The Verala framework library
The Operator Stack.
The AI operating system an active multi-unit operator runs day-to-day. Named, drillable patterns — not theory, not vendor pitches. Each framework survived 18 months in the field before it made the library.
Built by an operator who runs it on themselves first.
Tier 01 · The Foundations
The architecture.
Five frameworks that name the underlying structure of an AI ops setup. Read these in order.
- 01The 4-Surface AI StackCapture · Reason · Act · Remember — the architecture every other framework plugs into.
- 02The MCP Mental ModelModel Context Protocol explained for operators, not engineers. The USB-C port for AI.
- 03The Connector StackAn opinionated map of which MCP connectors to install + when. The 80% stack named.
- 04The Persona CascadeDesign AI personas as priority-ordered contracts, not wish lists. Six layers, top overrides bottom.
- 05The Memory ArchitectureThe four-file-type system that gives Claude long-term memory across every conversation.
Tier 02 · The Workflows
What the architecture does.
Five frameworks for the actual day-to-day operator workflows that the foundations enable.
- 06The Operator VaultThe Obsidian setup an active operator actually uses. Six folders, two plugins, one Sunday ritual.
- 07The Orchestrator + Sub-Agent PatternScale yourself with AI without becoming an AI middle-manager. One Coach. One daily debrief.
- 08The Voice Memo → AI LoopTurn the operator's most under-leveraged capture surface into a structured workflow.
- 09The Autonomy LadderFive named levels of AI autonomy. The contract that determines which work belongs at which level.
- 10The Hand-off Brief PatternHow to write specs Claude Code can execute autonomously overnight. Not a prompt — a contract.
The Stack is the architecture. Verala is the practice.
These frameworks are the operating system. Verala is what runs on top of them when applied to your own communication delivery — your voice, your pitch, your presence.