STANDING-RULES-PROMOTION-02 — Close Report¶
Brief: STANDING-RULES-PROMOTION-02 — Codify three governance disciplines earned through use across today's work.
Filed by: Claude (architect) 2026-05-27 PM.
Executed: 2026-05-27 — single session.
Commit: e0165c51 (1 file, 83 insertions, 1 deletion).
Status: Closed cleanly. Canonical-work cluster grows from 3 to 6 rules.
1. What was articulated¶
Three rules codified in Core operating rules section¶
| Rule | Provenance | Applications |
|---|---|---|
| BRIEF-DRAFT-SUBSTRATE-VERIFICATION | Surfaced 2026-05-27 at SRP-01 Gate 1 (Alex's section-label catch); promotion threshold reached at IMR-01 Phase 1 | 7 observable |
| SUBSTRATE-BRIEF-GATE-DISCIPLINE | Tim-filed at IMR-01 Gate 1 sign-off (2026-05-27); structural refinement of the five-gate pattern for substrate work | 2 observable (structurally-specified threshold) |
| MIGRATION-COMPLETION-DISCIPLINE | Tim-filed at IMPD-01 pre-Phase-2 alignment (2026-05-27); first application in ADR-025 Consequences §6 | 1 observable + 1 pending (IDENTITY-MODEL-MIGRATION-01) |
Canonical-work cluster grows 3 → 6 rules¶
After this commit, the cluster covers all known canonical-work integrity surfaces:
| Cluster rule | Protection point |
|---|---|
| METADATA-RECONCILIATION-AT-COMMIT | Commit-time metadata currency |
| RECON-PASS-ON-FOUNDATION-SHIFT | Foundation-shift implications for open work |
| CANONICAL-PROJECT-FILES-CURRENCY | Project-files mirror currency |
| BRIEF-DRAFT-SUBSTRATE-VERIFICATION (this commit) | Draft-time substrate-reference accuracy |
| SUBSTRATE-BRIEF-GATE-DISCIPLINE (this commit) | Gate-pattern shape for substrate work |
| MIGRATION-COMPLETION-DISCIPLINE (this commit) | Substrate lifecycle completion |
Deliberately held back¶
SUBSTRATE-NAME-MATCHES-SHAPE remains in memory as candidate (2 applications: ADR-024 + ADR-025; 1 short of promotion threshold). Carries forward to next promotion brief. Codifying it now would be making up for missing earned applications.
2. Gate-by-gate¶
| Gate | Activity | Output |
|---|---|---|
| 1 | Substrate-bytes pressure-test (eighth application of the rule being codified) | 5 findings: F1 application count undercount (5 → 7); F2 line numbers verified; F3 provenance precision nit; F4 composition cluster framing verified; F5 self-referential observation; §8 Q1-Q4 confirmed at defaults |
| 2 | Drafts staged | Three rule bodies inserted after CANONICAL-PROJECT-FILES-CURRENCY (line 379), before Machine safety rules (now line 463); header pin reconciles with cluster-count tracking |
| 3 | Tim review of bytes | Approved as pasted; noted unsolicited improvement on SUBSTRATE-BRIEF-GATE-DISCIPLINE companion-footer; F1 broader framing applied correctly; F3 wording correction applied correctly; F5 appropriately scoped to close report |
| 4 | Single coherent commit | e0165c51 — METADATA-RECONCILIATION-AT-COMMIT sixth post-codification application |
| 5 | Close report | This document + memory updates + snapshot refresh + mkdocs nav |
3. Sharpenings landed¶
Gate 1 outcomes¶
- F1 application count undercount — brief listed 5 applications; substrate-verification against memory + canonical artefacts yielded 7 distinct applications. Tim approved Option B (broader framing). Rule body §3.1 in standing-rules.md now reflects the seven-application accounting, with the most recent application (push-relay provenance catch) listed last.
- F3 provenance precision — MIGRATION-COMPLETION-DISCIPLINE provenance wording updated from "during IMPD-01 Phase 2 decision discussion" to "during IMPD-01 pre-Phase-2 alignment (in response to observations about UCCA-migration residue surfaced during IDENTITY-SURFACE-AUDIT-01)." Trivial precision; doesn't affect rule content.
- F5 self-referential observation — captured in §9 below, not in rule body. Rule body stays evergreen.
Gate 3 acknowledgement¶
Unsolicited improvement on SUBSTRATE-BRIEF-GATE-DISCIPLINE companion-footer ("one is what to verify; this is when in the gate sequence") confirmed as upgrade over the original draft and already present in the staged bytes.
4. Forward observations¶
4.1 Self-referential exercise property (per Tim's pin)¶
The canonical-work cluster rules tend to exercise themselves during their codification. The pattern is structural:
- The cluster rules operate on canonical work
- The brief codifying a cluster rule is canonical work
- The rule applies to its own codification
Observed instances:
- METADATA-RECONCILIATION-AT-COMMIT was exercised by the commit codifying it (STANDING-RULES-PROMOTION-01 26777755 — header pin reconciled with the rule additions in the same commit; rule's first authoritative application post-codification).
- BRIEF-DRAFT-SUBSTRATE-VERIFICATION was exercised by Gate 1 of the brief codifying it (this brief's Gate 1 — substrate-verification of the brief's application list caught the undercount; rule's eighth application).
Worth carrying as durable observation about how cluster-rules earn promotion. The three-application threshold and observation-before-codification cadence work because the rules operate on the canonical work that codifies them; the codification itself supplies an application.
4.2 Bookending shape working as designed (candidate methodology observation)¶
STANDING-RULES-PROMOTION-01 opened the day (foundation hygiene, commit 26777755); this brief closes it (governance codification, commit e0165c51). Substantive substrate work in between: CANARC-01 (canonical articulation arc), IDENTITY-MODEL-RATIONALISATION-01 (Phase 1 audit + Phase 2 design + ADR-024), IDENTITY-MODEL-PLACEMENT-DECISION-01 (decision analysis + ADR-025).
The substantive briefs executed against informal candidate rules; tomorrow's IDENTITY-MODEL-MIGRATION-01 will open against fully codified governance.
Candidate methodology observation: governance-codify-before-substantial-substrate-work is the right ordering. The pattern protects substrate work from drift during the substrate work itself, by codifying the disciplines that will be applied under load.
One observable application so far (today). Carry forward — earns its place if a third application of the pattern emerges. Memory entry not yet warranted; observation lives in close-report archaeology.
4.3 METADATA-RECONCILIATION-AT-COMMIT sixth post-codification application¶
The discipline continues to exercise itself on each canonical-work commit. This commit's header pin reconciles with the three rule additions in the same commit; cluster-count tracking (3 → 6) added to "Last updated" line.
Application count post-codification:
- 3rd (CANARC-01 commit 8522c6e3)
- 4th (canon-reconciliation work prior — already counted before codification)
- 5th (IMPD-01 ADR-025 commit 4dabb86b)
- 6th (this commit e0165c51)
The discipline is settling as routine. Worth observing whether routine application stops warranting explicit mention — at some point post-codification it becomes plain operating discipline rather than an observable application worth counting.
4.4 Candidate-discipline-accumulation surface cleaner after this brief¶
Pre-brief: - BRIEF-DRAFT-SUBSTRATE-VERIFICATION (promotion-ready, 4+ applications) - SUBSTRATE-BRIEF-GATE-DISCIPLINE (Tim-filed, 2 applications) - MIGRATION-COMPLETION-DISCIPLINE (Tim-filed, 1 application + 1 pending) - SUBSTRATE-NAME-MATCHES-SHAPE (2 applications, 1 short of threshold)
Post-brief: - SUBSTRATE-NAME-MATCHES-SHAPE (2 applications, 1 short of threshold) — only remaining candidate - Possibly emergent: bookending shape methodology (1 observable application) - Possibly emergent: self-referential exercise property (2 observable applications across the cluster rules so far)
Three promoted, one carried, two new candidates surfacing in close report.
5. Recommended next brief drip¶
Primary: IDENTITY-MODEL-MIGRATION-01¶
Phase 3 of IDENTITY-MODEL-RATIONALISATION-01. Now opens against fully codified governance disciplines:
- BRIEF-DRAFT-SUBSTRATE-VERIFICATION applies at brief draft time
- SUBSTRATE-BRIEF-GATE-DISCIPLINE governs the brief's gate structure
- MIGRATION-COMPLETION-DISCIPLINE governs Phase 4 retirement scope
- METADATA-RECONCILIATION-AT-COMMIT applies at each commit
- CANONICAL-PROJECT-FILES-CURRENCY applies after commits touching canonical docs
Migration brief structure (per ADR-025 Consequences §6):
1. Phase 1: Schema creation + binding wiring — provision rto-identity-db + -staging twin; apply ADR-024 schema; add IDENTITY_DB binding to internal-api
2. Phase 2: Per-row migration with id_migration_map — consolidate users + tier_grants assembly + credentials migration
3. Phase 3: Code-path update — ~18 caller-side conversions; ~6-10 new internal-api endpoints; session-shape update
4. Phase 4: Explicit retirement of superseded substrate per MIGRATION-COMPLETION-DISCIPLINE
5. Phase 5: Verification — confirm zero remaining references
Tim's call on timing — likely tomorrow morning.
Parallel candidates¶
- OPS-DB-IDENTITY-ORPHAN-CLEANUP-01 — 5 orphan-table drops; can fold into IDENTITY-MODEL-MIGRATION-01 Phase 4 or stay standalone
- CROSS-DB-DUPLICATE-PRODUCTS-01 — out of identity scope; tiny standalone
- CROSS-DB-DUPLICATE-MAGIC-TOKENS-01 — drop both copies (dead schema); tiny standalone
6. Canonical doc state at close¶
| Doc | Lines added | Lines removed | Net | Notes |
|---|---|---|---|---|
standing-rules.md |
83 | 1 | +82 | 3 rules added; header pin updated; canonical-work cluster grows 3 → 6 |
| Total | 83 | 1 | +82 | Single-file change, single coherent commit e0165c51 |
Snapshot refresh follows per CANONICAL-PROJECT-FILES-CURRENCY (fourth authoritative application).
7. Memory updates filed¶
project_brief_draft_substrate_verification.md— applications updated 4 → 7 with broader framing; promotion status updated to "FORMALLY CODIFIED at SRP-02"project_substrate_brief_gate_discipline.md— new entry filed; status FORMALLY CODIFIED at SRP-02project_migration_completion_discipline.md— status updated to FORMALLY CODIFIED at SRP-02project_substrate_name_matches_shape.md— unchanged (still 2 applications, carry-forward candidate)project_standing_rules_promotion_02.md— new close-state entryMEMORY.mdindex — updated entries reflect codification
8. Process notes¶
8.1 Same five-gate pattern as STANDING-RULES-PROMOTION-01¶
Both promotion briefs (morning + afternoon) used identical five-gate structure. Pattern is now twice-applied for governance-codification work specifically; well-shaped for this work class.
8.2 Eight applications of BRIEF-DRAFT-SUBSTRATE-VERIFICATION across the day¶
Including this Gate 1's verification of the brief's own application count, the discipline earned eight observable applications within the 36-hour window. It is the most-exercised candidate-rule-becoming-formal-rule of the day. Memory entry promoted to formal-codified status.
8.3 Brief drip discipline held¶
SRP-02 in flight from drip until Gate 5 close. Brief drip rule held cleanly across the day's seven-brief arc (CANARC-01 + canon work earlier; SRP-01; IMR-01; IMPD-01; SRP-02; plus the time-machine handoff briefs that aren't counted as substantive).
9. Methodology observations (per Tim's pin)¶
9.1 Bookending shape working as designed¶
Morning: STANDING-RULES-PROMOTION-01 (codifies METADATA-RECONCILIATION-AT-COMMIT + RECON-PASS-ON-FOUNDATION-SHIFT + CANONICAL-PROJECT-FILES-CURRENCY; foundation hygiene).
Middle: Substantive substrate work (CANARC-01 canonical articulation arc; IMR-01 Phase 1 audit + Phase 2 design + ADR-024; IMPD-01 decision analysis + ADR-025).
Afternoon: STANDING-RULES-PROMOTION-02 (codifies BRIEF-DRAFT-SUBSTRATE-VERIFICATION + SUBSTRATE-BRIEF-GATE-DISCIPLINE + MIGRATION-COMPLETION-DISCIPLINE; governance protecting tomorrow's substrate work).
Candidate methodology observation: governance-codify-before-substantial-substrate-work is the right ordering. The substantive briefs surface candidate rules through observable use; the closing-bookend codifies them; the next day's substantive work executes against fully codified governance rather than informal candidate rules.
One observable application so far (today's bookend). Two more applications across distinct sessions would earn formal codification of this methodology observation.
9.2 Self-referential exercise property of canonical-work cluster rules¶
The canonical-work cluster rules tend to exercise themselves during their codification. The pattern is structural, not coincidental: the cluster rules operate on canonical work; the brief codifying a cluster rule is itself canonical work; the rule applies to its own codification.
Observed instances:
- METADATA-RECONCILIATION-AT-COMMIT exercised by the commit codifying it (STANDING-RULES-PROMOTION-01 commit 26777755 — header pin reconciled with the rule additions in the same commit; rule's first authoritative application post-codification).
- BRIEF-DRAFT-SUBSTRATE-VERIFICATION exercised by Gate 1 of the brief codifying it (this brief's Gate 1 — substrate-verification of the brief's application list caught the undercount; rule's eighth application).
Why this matters operationally: the three-application threshold and observation-before-codification cadence work because the rules operate on the canonical work that codifies them. The codification itself supplies an application; rules that have earned three applications elsewhere will get a fourth at codification by virtue of how the gate discipline works.
Two observations of this pattern across two distinct codifications. Carry forward as durable observation about how the cluster earns promotion; codify formally if a third instance emerges (likely a third cluster rule codification surfaces it).
End of close report. Brief drip moves to next brief on Tim instruction. Recommended: IDENTITY-MODEL-MIGRATION-01 tomorrow morning against rto-identity-db target per ADR-025.