Approve 0054-0056, apply them, and fix the two smaller findings

0003 is now superseded by 0056. Nothing is left proposed.

Applied:
- 06 corrected from ten contexts to seven plus the api, each row now stating
  why it passes the more-than-one-node test. work, knowledge and stream are
  named as mesh-hosted rather than dropped; `ai` folds into config; `record`
  is deferred explicitly rather than listed. Its frontmatter now cites 0055.
- how-we-build §4 amended per 0054, and the derived page republished by
  playbook 05.

The sync found the drift the playbook exists to catch: the published §4 and
the source did not say the same thing. The source said "four accidents, not
four boundaries"; the published page said "one intent expressed four times",
and only the published page carried the scope caveat. Same rule, two texts,
already diverging. Verified the republish by reading back -- the new rule is
present and the old section's body returns nothing -- rather than trusting the
success message.

The two smaller findings:
- 0051 separated the transport identity from the declaring authority. It said
  the token carries "an address" and "the identity to expect" without saying
  what the node dials. It dials the broker, so pinning only that would make the
  control plane's authority transitive and let a compromised broker forge
  declarations -- which, since the host applies whatever the link delivers, is
  the whole machine. The token now carries four things, and declarations are
  signed and verified per declaration. Cost recorded: rotating the signing
  identity is fleet-wide.
- 0026 no longer restates 0022's rule about generated views. 0022's own words
  are "prose does not restate status; one place, and two is one too many",
  which is what 0026 was doing to it.

02-DECISIONS/0054-things-that-change-together-share-an-authority.md

@@ -1,5 +1,5 @@
 ---
-status: proposed
+status: accepted
 date: 2026-08-27
 deciders: jochen
 reconstructed: false
@@ -91,10 +91,16 @@ replacement keeps the observation and changes the instruction:
 
 - **The instruction now matches the design.** An agent reading the constitution and an agent
   reading 0044 reach the same answer, which they currently do not.
-- **The republication is the point, not a formality.** Until the derived page is regenerated the
-  mesh is still governed by the old rule, and this record has changed nothing where it matters.
-  Verified by reading the rule back out of the published page
-  ([ADR 0035](0035-a-picture-is-read-from-what-runs.md)), not by the publish reporting success.
+- **Synced 2026-08-27**, playbook [05](../00-META/process/05-constitution-sync.md). The derived
+  page carries the new rule and §4 keeps its number. **Verified by reading back**, not by the
+  publish reporting success: the replacement text is present, and the old section's body — *scope
+  under measurement: grouping is evidenced for reachability* — returns nothing.
+- **The sync found a drift the playbook exists to catch.** The published §4 and the source did not
+  say the same thing: the source spoke of *four accidents, not four boundaries*, the published
+  page of *one intent expressed four times*, and only the published page carried the scope
+  caveat. Same rule, two texts, already diverging — which is the exact failure
+  [ADR 0025](0025-hq-is-the-source-of-the-constitution.md) predicted and the reason the playbook
+  re-publishes the whole page rather than patching a section.
 - **`context` becomes a word the constitution uses**, which raises the obvious next question —
   *which contexts are there* — and that is
   [ADR 0055](0055-the-control-plane-is-the-node-coordinating-contexts.md), not this record.