Rule
Give every claim one authority. Git is ground truth for content and its history. The tracker owns work and status. The runtime owns execution. Sessions, terminals, task lists, dashboards, and projections point at those owners and never decide anything themselves.
Sessions are disposable. A terminal closes, a context window compacts, a host reboots, and whatever lived only there is gone. So each fact goes where its owner keeps it, and everything else links across. Put work status in two stores and they will disagree by Friday, with nobody able to say which one is right.
Proof is its own case. Verdicts, receipts, and drafts can carry more than you want in a public history, so new proof defaults to protected storage outside Git and is linked by digest. Reviewed knowledge can enter the repo later as a project .context/ page, and only after a fresh review of what it claims and what it discloses.
Put It to Work
- Keep source and its history in Git. Push finished work so the remote is the shared copy.
- Keep work, status, and handoffs in the tracker you already run. Build no second work index beside it.
- Read execution state from the runtime that owns it instead of mirroring it somewhere else.
- Store requested proof in protected storage outside Git and reference it from the change or the issue.
- Admit reviewed knowledge into the repo only after a fresh support-and-disclosure review.
- Treat sessions, task lists, dashboards, and projections as views you can rebuild from their owners.
Failure Signal
- A decision exists only in chat history.
- The tracker says open, a dashboard says done, and nobody knows which to believe.
- A verdict full of private evidence lands in a public commit because "everything goes in git."
- A handoff says "check my notes" instead of pointing at a commit, an issue, or a stored receipt.
Done Looks Like
Every claim names its owner. The clone holds the code and its history, the tracker holds the work, protected storage holds the proof, and every live view can be rebuilt from those owners.
In AgentOps 3.8: the federated source authority table gives each claim one owner: Beads or your tracker for work, Git for content and its history, and your coding agent or a selected factory for execution. ADR-0016 sends new drafts and proof to protected storage outside Git.