One signal path, two gates
Thin pipes move data, the smart middle judges it against vault rules, then every write clears two gates in order — a deterministic validation check (is it well-formed?) and the ApprovalMax human-approval gate (is it authorised under the Delegation of Authority?) — before it lands in a store and drives a surface. Agents never write to Xero directly.
Domains
Every capability captured so far, with build status and the phase it sits in. Filter by status or phase, search, or open one for its purpose, how it connects, the systems it touches, its linked domains, a hub-and-spoke view and a deep-link into the vault.
Deployment sequence
What gets built before what. Phase 0 — connections and the vault — carries everything, so it ships first; Phase 1, the safe transaction layer, is the first load-bearing build. Later phases run partly in parallel once their dependencies are live.
Connections
Where each system stands and what's next, grouped by status. A live connection doesn't mean an agent is built on it yet — connections and agents are separate steps. Resolved items at the bottom are reached another way rather than built directly.
Systems map
The canonical spine every domain runs on, and the full connector inventory — 17 external systems across 51 domains, with the three stores (Airtable, Supabase, Vault) carrying the load. Status and the number of domains each system serves.
Command Centre
The running decisions-and-ideas log. Open decisions need your call; the workstreams are the live parallel projects; the hardening list is the security debt to clear before mail-reading agents go live; and the plan is what to do next. Every card opens the full write-up in the vault.
Work streams
Live status of every delivery stream, maintained by the Build Control chat from the reports in reports/. Streams with a report link have a written record behind them.
Open questions
Every "Decide now" item from each domain's Questions.md, grouped by domain. These are the choices that gate each build — settle them and the slice can be specced. Each group deep-links to the domain in the vault.
Bedded down
Domains whose Agent Instructions.md is written as a substantive operating ruleset — role, hard gates, retrieval limits, escalation routing — not a stub. These are ready to build against once their open questions are settled. D48–D51 are GOALS-only and have no folder yet.
Daily Git commands
OneDrive no longer syncs this project — Git does. The two laptops stay in step through GitHub, so the habit is simple: pull before you start, push before you walk away.
cd ~/buildgit pullgit add .git commit -m "short note on what changed"git pushgit statusgit log --oneline -10git pull
git push