Daniel
Sets intent, resolves ambiguity, and approves consequential work.
DECIDESAGENT MEMORY & RELIABLE ACTION Architecture overview · August 2026
Memory that can evolve.
Work that remains accountable.
A visual guide to why we are pairing active agent memory with deterministic business controls—and how a year of operating experience moved us here.
01
The architecture
See the whole system before reading the argument.
The upper half shows where flexibility belongs. The lower half shows how operating experience produced the design.
02
How it operates
Structured state replaces loose project memory.
The agent can reason flexibly, but work, authority, and results move through registered components. Operational state lives in structured records—not a pile of .md files that can drift apart.
REQUEST + DECISIONBOUNDED EXECUTIONSTRUCTURED STATE
Daniel’s Desk
Manages attention: what changed, what needs a decision, and what is blocked.
PRESENTSControl Center
Owns project registry, scope, routing, ownership, lifecycle, and approval state.
AUTHORIZESAgent
Interprets the task and performs only the work allowed by the registered route.
PROPOSES + ACTSMCP
Exposes typed reads and narrow approved writes. It is a boundary, not a second brain.
CONSTRAINSSupabase
Stores structured projects, tasks, work logs, source observations, and lifecycle state.
RECORDSREAD BACK + VERIFY←
Supabase result
←MCP response
←Control Center lifecycle
←Desk status
←Daniel sees the outcome
The agent’s understanding does not grant permission. Control Center scope and approval govern what may happen.
A write or external action is not complete until the result is read back and reflected in lifecycle state.
.md FILESUseful for plans, explanations, and exports—but not the operational database, routing registry, or current status.
03
The progression
Each decision solved a failure the earlier design exposed.
This is the short version. The detailed page preserves the reasoning, limits, and supporting evidence.
- 01ATTEMPT 5.5Workflows need durable state.
- 02CONTROL CENTERShared context needs authority boundaries.
- 03GLOBALSome rules belong above projects.
- 04MCPAccess should be typed and bounded.
- 05DANIEL'S DESKThe interface should manage attention.
- 06EMAIL + CLOUDFLAREAn event is not permission to act.
- 07NAPMEMActive navigation belongs in knowledge.
04
Section guide
The basics first. The complete record one level deeper.
Each card gives the point in plain language and leads to the exact section containing the full reasoning.
01OUR POSITION
Memory and authority are different problems.
Use flexible navigation to decide what evidence matters. Use deterministic controls to decide what actions are allowed.
Read the position → 02THE SYSTEMFour planes, four responsibilities.
Knowledge, governance, execution, and presentation cooperate without silently inheriting one another's authority.
See the system → 03HOW WE GOT HEREThe architecture grew from operating failures.
Attempt 5.5, Control Center, GLOBAL, MCP, the Desk, and email intake each revealed the next missing boundary.
Follow the chain → 04THE CUSP CLAIMTimely applied work—not a claim of invention.
The components are established or emerging. Their disciplined use across live business operations is still early.
Test the claim → 05THE EVIDENCEResearch direction plus production constraints.
MemGPT, MemOS, and NapMem inform the memory path. Current agent guidance informs governance and oversight.
Review the sources → 06THE CRITIQUEWe want the strongest objections.
Prior art, counterexamples, simpler architectures, and failure modes are more useful than agreement.
Send feedback ↗FULL RECORD Argument · decision chain · evidence
The overview is the map.
The detail page is the record.
Read what we adopted, what we deliberately rejected, what remains unresolved, and what evidence would cause us to change direction.