00-META/how-we-build.md

@@ -172,9 +172,6 @@ behaviour asserts a guess. The obligation is that every decision has a defender.
 
 ### A report is read from the system, never from what asked for it
 
-*Proposed — [ADR 0035](../02-DECISIONS/0035-a-picture-is-read-from-what-runs.md), pending
-review.*
-
 The same rule as the two above, pointed at reporting rather than at verification. **Anything
 that describes the state of the mesh — a status view, an inventory, a diagram, a health
 check — is assembled from the running system.** Assembling it from the intended state produces

02-DECISIONS/0035-a-picture-is-read-from-what-runs.md

@@ -1,5 +1,5 @@
 ---
-status: proposed
+status: accepted
 date: 2026-08-24
 deciders: jochen
 reconstructed: false
@@ -84,12 +84,10 @@ difference read off directly.
 - The declared picture stays, and stays useful: it is review before raising, and it is one half
   of the comparison. It carries no runtime status, because it cannot know any.
 
-- **The constitution sync is not done and must not be.** `how-we-build.md` §5 carries this rule
-  marked *proposed*, and playbook
-  [05](../00-META/process/05-constitution-sync.md) publishes the derived page only for rules the
-  mesh should enforce now. A rule the mesh enforces before a second person has agreed to it is
-  the failure mode §6 exists to prevent. The sync happens when this record is accepted, and this
-  line is what makes the gap visible rather than silent.
+- **The constitution sync is now owed.** Accepted 2026-08-25, so §5 carries the rule
+  unqualified and playbook [05](../00-META/process/05-constitution-sync.md) is due. Until it
+  runs, the mesh does not enforce this — an unsynced rule is a rule the mesh does not enforce,
+  whatever this document says.
 
 ## References