STANDING-RULES-PROMOTION-01 — Close Report¶
Brief: STANDING-RULES-PROMOTION-01 — Codify four governance disciplines earned through use.
Filed by: Claude (architect) 2026-05-27 morning; relayed by Tim with Gate 1 review.
Authority: Tier 1 #3-5 bundle from RECON-FOUNDATION-LENS-01 §5 + fourth rule (CANONICAL-PROJECT-FILES-CURRENCY) earned through 2026-05-26 recon-v1 stale-project-files failure + 2026-05-27 macOS cp creation-date observation.
Executed: 2026-05-27 — single working session, ~30 minutes substantive plus gate overhead.
Commit: 26777755 (1 file changed, 48 insertions, 1 deletion).
Status: Closed cleanly. 1 commit unpushed, held per discipline.
1. What was articulated¶
Four rules codified (Core operating rules section)¶
| Rule | Provenance | Why earned |
|---|---|---|
| METADATA-RECONCILIATION-AT-COMMIT | 3 observable applications (SPINE-AND-ADR-05b, CANON-VS-ADR-018-RECONCILIATION-01, CANARC-01) | Promotion threshold reached per CANON-VS-ADR-018-RECONCILIATION-01 close §8 |
| RECON-PASS-ON-FOUNDATION-SHIFT | RECON-FOUNDATION-LENS-01 §C8 | First articulated application was the recon itself; discipline operating implicitly since |
| CANONICAL-PROJECT-FILES-CURRENCY | Recon-v1 stale-files failure 2026-05-26 + macOS cp creation-date observation 2026-05-27 |
Two distinct failure modes surfaced two-component sharpening of pre-existing Doc sync discipline |
| RECON-DOCS-AT-POSITION-4B (hierarchy expansion, not new rule body) | RECON-FOUNDATION-LENS-01 §C10 | Recon docs are an artefact class without governance position; 4b inserts the position |
All three rule bodies sit in Core operating rules section, between SPINE-AND-ADR-AS-GOVERNANCE and Machine safety rules. The 4b hierarchy expansion lives in the Governance hierarchy section.
What landed concretely¶
- Header pin updated to reflect four additions.
- Governance hierarchy position 4b inserted (recon documents at
ops/recon/). - Three new rule headers under Core operating rules.
- Composition sentence in CANONICAL-PROJECT-FILES-CURRENCY cross-referencing Doc sync discipline as the framing this rule operationalises.
2. Gate-by-gate¶
| Gate | Activity | Output |
|---|---|---|
| 1 | Substrate-bytes pressure-test | 8 findings: 3 substantive sharpenings (F1 section-label correction, F2 composition placement question, F3 path-name singular/plural), 5 confirmations (Q1/Q2/Q3 clean, F6/F7/F7-sub/F8 confirmed-as-drafted) |
| 2 | Drafts staged | Header pin + governance hierarchy 4b + three rule bodies inserted with F1/F2/F3 sharpenings applied |
| 3 | Tim review of bytes | Approved as pasted; two unsolicited improvements (provenance block on METADATA-RECONCILIATION-AT-COMMIT, "How to apply" paragraph) confirmed as upgrades |
| 4 | Commit | 26777755 — single-file coherent commit; first authoritative application of METADATA-RECONCILIATION-AT-COMMIT post-codification (this commit's own header pin reconciled in same commit) |
| 5 | Close report | This document |
3. Sharpenings landed (Gate 1 outcomes)¶
F1 — Section label correction (substantive)¶
The brief proposed inserting rules in "Operating principles" section, citing CANONICAL-DECISION DISCIPLINE / SPINE-AND-ADR-AS-GOVERNANCE as siblings. Substrate check found those existing rules live in Core operating rules section (lines 286 and 312), not Operating principles. The brief's sibling-relationship reasoning was correct; section label was wrong.
Corrected at Gate 2: all three rules land in Core operating rules, after SPINE-AND-ADR-AS-GOVERNANCE, before Machine safety rules. This is exactly the kind of catch Gate 1 substrate-bytes pressure-test is designed to surface — author's reasoning right, substrate state different from assumption.
F2 — Composition sentence placement (Tim decision)¶
Pre-existing "Doc sync discipline" section at bottom of standing-rules.md covers Project Files as mirrors of canonical docs. CANONICAL-PROJECT-FILES-CURRENCY's three sub-disciplines are sharper versions of the same concern.
Two options: separate rule (Option A) or fold into Doc sync discipline (Option B). Tim chose Option A with composition sentence cross-referencing Doc sync discipline. Applied at Gate 2 as bolded sentence in CANONICAL-PROJECT-FILES-CURRENCY body: "This rule operationalises the cadence-and-currency framing in Doc sync discipline (below) — Doc sync discipline frames repo-as-source-of-truth and refresh cadence; this rule specifies concrete triggers, filesystem discipline, and session-open verification."
F3 — Path name correction (tiny but real)¶
Brief drafted docs/docs/ops/recons/ (plural). Substrate has docs/docs/ops/recon/ (singular) — confirmed against actual file location of RECON-FOUNDATION-LENS-01. Singular form applied wherever the path appears (governance hierarchy 4b entry, RECON-PASS-ON-FOUNDATION-SHIFT rule body).
Confirmations (F4-F8)¶
- F4 (Q3 ripple): Single "position X" reference in canonical docs at
architecture-decisions.mdline 4 ("Position 4"); 4b insertion doesn't affect it. No cross-reference invalidation. - F5 (Q1 + Q2): All four rule names unique against header scan. All compositions additive, not redundant.
- F6 (rule ordering): Drafted order confirmed.
- F7 (4b label): Confirmed; renumbering would force ADR doc cross-reference update for cosmetic gain.
- F7-sub (4b entry form): Separate-entry form confirmed (not compressed-with-sub-bullets).
- F8 (header pin format): Current pattern with longer descriptor; ADR-doc-style evolution paragraph is over-investment for standing-rules.md.
Unsolicited improvements (Gate 3 approved)¶
Two additions Alex made during Gate 2 staging that weren't in the brief draft:
- Provenance block on METADATA-RECONCILIATION-AT-COMMIT — three observable applications listed with commit SHAs, matches the established pattern (PROD-VERIFICATION-FALLBACK RULE has a similar "Earned through three distinct applications" list).
- "How to apply" paragraph on METADATA-RECONCILIATION-AT-COMMIT — concrete operator guidance ("audit adjacent metadata before commit"), aligns with how to-apply structure in other rules.
Both confirmed at Gate 3 as upgrades over the original draft.
4. Forward observations¶
4.1 First authoritative application of METADATA-RECONCILIATION-AT-COMMIT¶
This commit codifies the rule and exercises it in the same commit — header pin reconciles with the four rule additions inside the same single-file commit. The rule's first authoritative application post-codification is the act of codifying it. Self-referential but operationally clean.
4.2 Composition pattern: rule + existing-section bridge¶
CANONICAL-PROJECT-FILES-CURRENCY's relationship to Doc sync discipline (rule operationalises framing) is a pattern worth pinning. Future rules may sharpen pre-existing high-level sections; the explicit composition-sentence pattern (bolded, "This rule operationalises..." form) makes the relationship discoverable to the reader. Not yet earned through repeated application — first explicit instance — but worth being aware of.
4.3 Reciprocal-composition discipline candidate-rule (carried forward from CANARC-01)¶
Phase 3 reciprocal-composition pattern still operating implicitly. STANDING-RULES-PROMOTION-01 didn't exercise it (no ADRs touched; only standing-rules additions). The rule shape awaits a second clean application before earning independent memory or codification.
4.4 Operating principles vs Core operating rules section semantics¶
The F1 catch surfaced that the two sections have meaningfully different shapes:
- Operating principles — frame/calibration/heuristic rules. Decision lenses. Operators reach for them when calibrating choices. Examples: NAMING-PAUSE, OPERATING-CALIBRATION, CLOUDFLARE-FIRST, NO-WEAPONISED-LOCK-IN.
- Core operating rules — concrete trigger→action must-dos. Examples: OPS SURFACE RULE, DEPLOY-ON-SURFACE-TOUCH RULE, EXT-API RULE, CANONICAL-DECISION DISCIPLINE, the three rules added today.
Worth carrying as orientation for future rule-placement decisions. Briefs that propose new rules should specify which of the two sections from the start, with this distinction in mind.
5. Recommended next brief drip¶
Per recon §5 Tier 2 sequencing (carried forward from CANARC-01 close report §5).
Primary recommendation: IDENTITY-MODEL-RATIONALISATION-01 (Tier 2 #6).
Reasoning unchanged from CANARC-01 close: 1. ADR-020 provides target shape (T4 admin role + T4A user identity). 2. Substantively unblocks OPS-DB split, ADMIN-AUTH-MODEL-RECONCILIATION-01, EXTRACT-CUSTOMER-DATA-TO-CUSTOMER-DB-01. 3. First by recon §5 Tier 2 sequencing.
Tier 1 foundation work is now closed: - Tier 1 #1 CANON-VS-ADR-018-RECONCILIATION-01 — closed 2026-05-26. - Tier 1 #2 SPINE-SECTION-9-NAMING-CONVENTION-ALIGN-01 — closed via fold-in to #1. - Tier 1 #3-5 (METADATA + RECON-PASS + recon-position-4b) — closed at this brief.
Next session opens against fully codified Tier 1 foundation. Tim's call on whether to drip IDENTITY-MODEL-RATIONALISATION-01 today or save for tomorrow.
6. Canonical doc state at close¶
| Doc | Lines added | Lines removed | Net | Notes |
|---|---|---|---|---|
standing-rules.md |
48 | 1 | +47 | 3 rules added in Core operating rules; governance hierarchy 4b inserted; header pin reconciled |
| Total | 48 | 1 | +47 | Single-file change |
Other canonical docs unchanged at this commit. ADR doc, spine doc, recon doc all untouched (their content compositions with the new rules are already in place via prior commits).
Commit 26777755. 1 unpushed commit, held per discipline.
Canonical-current snapshot at ~/Downloads/canonical-current/ to be refreshed with clear-before-write per the new rule.
7. Process notes¶
Gate 1 sharpening density: 3 substantive findings across 8 total. Higher ratio of substantive sharpenings than CANARC-01 Gate 1 (which produced 5 sharpenings across many smaller items). The F1 section-label catch was the most consequential — would have produced canonically-shaped output in the wrong section, requiring a follow-up commit to relocate.
Brief drip discipline held. STANDING-RULES-PROMOTION-01 in flight from Gate 1 morning until Gate 5 now. Next brief drips on Tim instruction.
Five-gate canonical-work pattern third clean application. After CANON-VS-ADR-018-RECONCILIATION-01 and CANARC-01, this brief continues to fit the pattern. Pattern is becoming routine for canonical-articulation work.
Cache state: prompt cache warm. Session context aligned to current canonical state.
End of close report. Brief drip moves to next brief on Tim instruction.