Home

Orrin Wiki

Orrin is an experimental symbolic-first cognitive runtime: a long-running Python agent with persistent goals, memory, control signals, host telemetry, metacognition, and an optional LLM tool layer.

It is designed to make agent behavior inspectable over time: what it attends to, what goals it pursues, how memory changes, how control signals bias action selection, and how the runtime responds to the machine it runs on.

Orrin is a research prototype, not production software and not a claim of sentience. Cognitive terms in this wiki refer to engineering mechanisms: memory, goals, attention, control signals, runtime state, and action selection.

Start Here

• Getting Started — install, run, and read the UI in your first hour
• What is Orrin?
• The Cognitive Loop
• Quick Navigation Guide
• Glossary
• FAQ

Core Architecture

• Symbolic-First Design
• Workspace and Ignition
• Binding and Workspace Writeback
• Thinking and Action Selection
• Action Selection and Bandit
• Learning and Adaptation
• Loop Phases: Detailed

Subsystems

• Memory System / Memory Subsystem Deep Dive
• Control Signals / Deep Dive / Module
• Symbolic Reasoning / Subsystem Deep Dive
• Goals: Executive vs. Daemon / Goals Daemon Subsystem
• Peers / Peers Subsystem
• Host Coupling / Supervisor
• LLM Integration

Production and Expression

• Production and the Effect Ledger
• Quality Standard
• Expression Membrane
• Self-Code and Extension
• Native Language Model
• Existence and Lifecycle

The UI

• Face & Brain UI
• Backend & Telemetry

Running and Operating Orrin

• Configuration Reference
• Running with Docker
• Remote Access & Tunneling
• Desktop Packaging
• Security Model
• Benchmarks and Verification
• Troubleshooting
• Debugging Memory Issues

Development

• Contributing
• Cognition Module
• Writing a Custom Cognitive Function
• Extending Symbolic Operations
• Adding a Custom Peer
• Tuning Control Signals

Project

• Roadmap & Status
• Scientific Foundations

Source and maintenance: this wiki's source of truth is docs/wiki/ in the main repository (originally based on the WIKI_STRUCTURE.md blueprint, now in docs/archive/). Update pages when code or design changes; keep code pointers in each page.