Skip to the diagram
04 / 08Micro / durable context, coordinated work and operations

The operating spine underneath the estate.

People and agents need to know what is authoritative, what work is ready, what has been learned and what is safe to release. Separate systems hold those responsibilities; shared interfaces make them usable together.

INTENT SOLUTIONS / THE OPERATING SPINE

DURABLE AUTHORITIES / EACH HAS A DISTINCT JOB
INTERFACES AND BOUNDED ACTION
RELEASE, OPERATE AND LEARN
The operating spine underneath the estate. — relationshipsThree durable authorities hold source and decisions, Beads work state and governed knowledge. Skills, MCP tools and agent sessions use those authorities to perform bounded work. Review and release gates connect work to deployment, operation and new evidence. Arrows show responsibility and information flow, not a claim that every integration is fully automated. procedures claim work cited recall shared method tools evidence authorized release run observations propose lessonprocedures claim work cited recall shared method tools evidence authorized release run observations propose lesson

INTENT OS + REPOSITORIES

Source & decisions

Source code, company policies, interface contracts, operating docs and recorded decisions.

  • Git history · explicit authority

BEADS + DOLT

Durable work

Issues, dependencies, claims, acceptance evidence and task history across sessions.

  • Dolt database authority · Git code history

BOB’S BIG BRAIN

Governed knowledge

Capture proposals, apply governance, retrieve cited knowledge and verify audit receipts.

  • Compile → govern → retrieve

REPEATABLE PROCEDURES

Skills

Specify the method, required context and completion conditions for a class of work.

ACCESS TO CAPABILITIES

MCP & tool interfaces

Expose bounded tools and retrieval. Access still follows the tool’s permissions.

EXECUTION AND JUDGMENT

People & agent sessions

Recover context, claim work, act within scope and leave evidence for the next session.

DECIDE WHETHER TO SHIP

Review & release gates

Check acceptance, tests, changes and required human decisions before release.

A CONTROLLED CHANGE

Deployment

Versioned release, verification and an available rollback path.

AN ACCOUNTABLE OWNER

Operation

Observe health, respond to failures and maintain recovery procedures.

CLOSE THE CONTEXT LOOP

Evidence & proposals

Record what changed. Propose useful lessons for governed recall.

The model can change without losing the company’s source, work history or governed knowledge. Durable state belongs to systems with explicit owners and rules.
Work / artifact flowFeedbackControl / shared supportProposed boundarySelect a node to trace its connections.

Each authority answers a different question

Source records what exists and what was decided. Work tracking records what remains and why it is blocked. Governed memory records what may be recalled as an accepted lesson.

  • An index is a rebuildable search aid, not a replacement authority.
  • A dashboard is a projection with a scope and freshness boundary.
  • A proposed memory is not accepted knowledge merely because an agent wrote it.

Bob’s Big Brain, closer in

The Compiler can derive knowledge from a source corpus. The Registrar applies governance and maintains receipts; qmd supplies cited retrieval. The plugin exposes that loop through tools and skills.

  • Local mode operates in process after provisioning.
  • Team mode proxies to a shared governed-brain service.
  • The Compiler itself is a local tool; a team interface does not prove every ingestion path is deployed.

Coordination without pretending everything is automatic

The estate combines source, tools and operating procedures at different stages of adoption. People remain responsible for scope, promotion, release, response and recovery.

  • Beads history and code history travel in different Git reference lanes.
  • Hooks restore context and apply local guardrails; review and CI enforce their release checks.
  • Capabilities and rollout status must be checked in their owning repository.
  • Operational proof includes failure and recovery behavior, not just a passing build.

The business and operations support layer

The spine also connects relationship management, project coordination, communication and operational awareness. Each tool retains a defined job; a shared view does not make every system one synchronized authority.

  • Twenty supports relationship tracking; Plane provides a project-coordination surface alongside Beads work records.
  • Mission Control projects scoped status from the owning systems, preserving source, freshness and unknown states.
  • MXroute handles company email; Buzz supports team conversations and notification surfaces.
  • Monitoring, alert routing, backups and restore procedures support the person accountable for operations.
  • The public Mission Control view is a bounded reporting projection, not the private operations console.
Read the relationships as text

Three durable authorities hold source and decisions, Beads work state and governed knowledge. Skills, MCP tools and agent sessions use those authorities to perform bounded work. Review and release gates connect work to deployment, operation and new evidence. Arrows show responsibility and information flow, not a claim that every integration is fully automated.

  • Source & decisions → Skills: procedures (governance)
  • Durable work → People & agent sessions: claim work (governance)
  • Governed knowledge → MCP & tool interfaces: cited recall (governance)
  • Skills → People & agent sessions: shared method (flow)
  • MCP & tool interfaces → People & agent sessions: tools (flow)
  • People & agent sessions → Review & release gates: evidence (flow)
  • Review & release gates → Deployment: authorized release (governance)
  • Deployment → Operation: run (flow)
  • Operation → Evidence & proposals: observations (flow)
  • Evidence & proposals → Governed knowledge: propose lesson (feedback)

Basis and scope

Reviewed 2026-10-11. Public links support the named properties and capabilities. The relationships explain the operating method and owner-directed vision; they do not imply that every initiative is deployed or commercially proven.

Mermaid sourceComplete source graphWorkshop PDFPrint view