Decision records

The Scrum Master is three models sharing one identity. Nothing in the runtime guarantees they share a memory — each is a separate session with its own context. .agentic/DECISIONS.md is what makes them one agent instead of three agents contradicting each other in front of the teams below.

Read before you decide

At the start of every convene, read .agentic/DECISIONS.md in full. Not a summary of it. If a step would reverse a recorded decision, that alone flags the step (see flag-check), so the reversal gets recorded too and the history stays honest.

The index is append-only. Never edit or delete a past entry. A decision that turned out wrong gets a new entry that supersedes it and says so — the wrong decision and the reason it was reversed are both worth keeping.

Write after you decide

Append one line to .agentic/DECISIONS.md:

| DR-0007 | 2026-08-14 | Briefing cross-domain exposure | picked draft B | reversibility | convenes/DR-0007/ |

And write the full record to .agentic/convenes/<id>/decision.md using templates/decision-record.md. It must contain:

• What was decided — stated so someone can act on it without reading the drafts
• The criterion that decided it — from the pre-named criteria
• What was rejected, and why — the most valuable and most skipped section
• Derived acceptance criteria, if the Scrum Master inferred any from the PM's goal. Writing them here is what lets the PM veto them at a gate instead of discovering at G3 that the system graded its own homework.
• Flag decision — was this flagged, by whom, under which trigger

Never put an example row in the live index

DECISIONS.md is read in full by every council member, and a commented-out example row is not invisible to a language model — or to grep, which does not respect HTML comments. An example that reuses a plausible ID and title reads as a real prior decision, which is exactly the divergent history this file exists to prevent. The format belongs in this skill and in templates/, never in the file itself. (This shipped once and was caught on the first dry run.)

Numbering

DR-NNNN, zero-padded, monotonic, never reused. If two convenes run concurrently, the orchestrator assigns numbers — members never self-assign.