x:0 y:0 Agents / 01
Persek OS · Subsystem

Agents

Nine specialists. One cross-system view. Many ways into the work.

In Persek OS, each agent has a focused role and a clear area of ownership. The goal is not to force every request through one gate. The goal is to make sure context, memory, and follow-through do not scatter as the work moves.

Cal helps hold cross-project context and follow-through. I still work directly with specialists when the job is obvious. Cal is the coordination layer, not the only doorway.

← Back to Persek OSNext subsystem · Memory →

x:860 y:0 Roster / 02
The ten

The roster.

Cal keeps the cross-system view. Nine specialists sit around the ring, and direct specialist work still happens.

OPERATING LAYER PIP VANCE DRAPER IRIS REX WALDO MARCO HARPER FINN BUILD & DEV INTEL & VOICE HOME & SELF CAL cross-system view

Cal cross-system context

Keeps the wider picture visible and helps follow-through survive across projects.

Pip build & dev · infra

Owns the harness itself. The infrastructure layer everyone else stands on.

Vance build & dev · flagship app

Vitality Quest lead. Owns the feature pipeline, module architecture, and test strategy for the flagship product.

Draper build & dev · bounded apps

Application developer for prototypes, internal tools, and family apps. Includes this site.

Iris intel & voice · signal

The intelligence layer. Triages the firehose and produces the daily brief.

Rex intel & voice · research

On-demand research. Multi-source investigation with source-grounded synthesis.

Waldo intel & voice · writing

Personal writing agent. Owns the voice for external-facing prose: drafts, essays, landing copy.

Marco home & self · marketing

AI-native marketing for Persek Industries. Brand, content, and analytics.

Harper home & self · homeschool

Daily homeschool partner. Curriculum planning, per-kid progress tracking, lesson design.

Finn home & self · finance

Personal finance and investments. Cash flow, planning, and the quiet accounting work that keeps everything else honest.

x:0 y:720 Sectors / 03
How they're grouped

Three sectors.

Nine specialists fall into three natural groupings: the parts of the system that share context.

SECTORS / 3 BUILD & DEV ships code PIP infra VANCE flagship app DRAPER bounded apps share patterns, tooling, standards INTEL & VOICE handles signal IRIS eye on signal REX depth on demand WALDO voice + writing share research, voice, audience HOME & SELF life and business MARCO marketing HARPER homeschool FINN finance share family + business context

Build & Dev

Pip, Vance, Draper. The agents that ship code. They share product and engineering context.

Intel & Voice

Iris, Rex, Waldo. The agents that handle external signal and produce external-facing artifacts. Iris is the eye, Rex is the depth, Waldo is the voice. They share research context and publishing context.

Home & Self

Marco, Harper, Finn. The agents that own life and business outside dev. Marketing, homeschool, and household finance.

x:780 y:1720 Coordination / 04
How work routes

Coordination when the work needs it.

Some work starts with Cal. Some starts directly with a specialist. The important part is that cross-agent context still has a place to land.

WORK FLOW REQUEST direct or via Cal CAL context PIP infra work REX research work DRAPER app build cross-context still lands in one place

The point is not that Cal owns every route. The point is that cross-agent context has a home. If the work is broad, I may start with Cal. If the work is obvious, I go straight to the specialist, and the system keeps enough continuity that the work does not disappear between sessions.

The pattern scales because adding a new specialist adds a new lane without requiring every other agent to know everything about it. Cal keeps the larger map current, while the specialist owns the actual work.

It also forces clarity when clarity is needed. Broad requests get shaped into an artifact, owner, and next step. Direct specialist work can stay fast without losing the thread.

x:0 y:1740 Operating Layer / 05
What they share

The operating layer.

The plumbing all ten agents stand on. Boring on purpose.

5 LAYERS 01 CONTEXT carried between working sessions 02 REVIEW recurring review and maintenance 03 MEMORY shared context with clear boundaries 04 HANDOFF the rules for how work moves 05 TRACEABILITY important changes stay traceable

None of this is exciting. It is supposed to be plain. The interesting part is what the council does on top of it.

next dragpan 0fit all Eschome
Want to reach out? X is best.
x / @dpersek linkedin github / syntaxsawdust