From 88d759232187943d97d63ea713df3a55b42e95cc Mon Sep 17 00:00:00 2001 From: null Date: Tue, 18 Aug 2026 00:15:08 -0500 Subject: [PATCH] docs(readme): the review trigger still described the old Governs Two commits ago README's `Governs:` changed from `Projects/Template/**` -- true while this was a folder inside Projects/, matching nothing once it became a repository root -- to the three root documents it actually makes claims about. Its `Review trigger:` was left describing the previous scope. That is the drift this tree keeps finding, committed by me, in the header field pair whose entire job is to stay coherent: a Governs updated on one line and a trigger left describing what the document used to cover. Nothing checks the two against each other, which is why it survived a commit and a peer review. The trigger now names the events that should actually send somebody back here: a change to how adoption works, a script added or removed from the day-one table, and the QA run-state and reconcile grammar it already covered. Co-Authored-By: Claude Opus 5 (1M context) --- README.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 15d6c85..645572b 100644 --- a/README.md +++ b/README.md @@ -10,11 +10,12 @@ Status: Current Owner: _null Last reviewed: 2026-08-12 Governs: README.md, START-HERE-New-Project.md, START-HERE-Existing-Project.md -Review trigger: Any change to the tracker conventions or the QA run-state - grammar in the Privacy LLC Command Center's src/lib/; any - change to which project fields the agent API can write, or to - what reconcile reads; any script added to or removed from - docs/architecture/scripts/ +Review trigger: Any change to how a project adopts this template — scaffold.sh's + file list, the tracker conventions or the label names, or what + the Command Center needs at adoption; any script added to or + removed from docs/architecture/scripts/, which the day-one table + here names; any change to the QA run-state grammar or to what + reconcile reads ``` ## Why this exists