Operating manual
Coordination Operating System
A unified framework for governing change on complex projects.
Thesis
An unanchored change enters an interconnected system faster than governance can track it.
This is not a reading list. It is an operating manual.
In use · JN-05
b1m.solutions
The system, held in one place: a coordination memory that keeps the thread around every issue.
The Coordinator's Brain Should Not Be the Project's Database Read the journal entry- 01 The Framework Trap
Built for one coordinator first, so it works before anyone else has to adopt it.
- 02 Reactive Coordination
Every change is recorded with who made it and when, and nothing in the record is overwritten.
- 03 AI Agents and the Governance Gap
An assistant reads through a connector I authorise, and can only add an observation for me to triage.
- 04 Silent Divergence
The current state lives in a record, not in one person's memory: what was claimed, confirmed and decided.
- Module 01 Adoption
The Framework Trap
- Project phase
- Day one — before informal habits form
- Entry signal
- An informal instruction (WhatsApp, verbal, phone call) is acted upon and modeled without an issue tracker ID attached.
- Output
- The framework is the only surface across which work can legally cross. Informal channel attempts fail automatically. The path of least resistance has shifted to inside the system.
- Module 02 Debt
Reactive Coordination
- Project phase
- Post-60% DD through construction documentation
- Entry signal
- The ratio of Unlogged Changes to Identified Clashes begins to diverge — e.g., 500 new clashes per week against only 10 authorized logged changes.
- Output
- No unlogged change enters the federated model. Coordination Debt ledger is zeroed before each major milestone. The team is resolving issues, not investigating origins.
- Module 03 Governance
AI Agents and the Governance Gap
- Project phase
- Forward-looking — IFC stage
- Entry signal
- Coordination decisions are being made inside tools or automated workflows — model checkers, clash engines, procurement integrations — without a defined approval chain. No one can clearly state which tool committed a change, or when, or who authorized it.
- Output
- Every machine-proposed change passes through the ACIP lifecycle. Decision rationale is as permanent as project structure. Human authority is preserved even as agent autonomy expands.
- Module 04 State
Silent Divergence
- Project phase
- 60% DD through IFC issuance
- Entry signal
- A coordination meeting's first 20 minutes are spent reconstructing 'what changed since last time' from memory and chat logs — not a shared document.
- Output
- Every team member enters the federated model with the same understanding of current objective, locked zones, and next actions. Re-coordination from silent divergence is eliminated.
This system is a work in progress. New modules are added as new failure modes are identified.