SCRs (Schema Change Requests) surfaced in scoping records use dimension-prefixed numbering rather than a single continuous sequence across the entire scoping programme.
Prefix scheme
| Dimension | Prefix | Example |
|---|---|---|
| Succession | SUCC-SCR- | SUCC-SCR-01, SUCC-SCR-02, … |
| Tax | TAX-SCR- | TAX-SCR-01, TAX-SCR-02, … |
| Trust | TRUST-SCR- | TRUST-SCR-01, … |
| Power of Attorney | POA-SCR- | POA-SCR-01, … |
| Faith (primary dimension) | FAITH-SCR- | FAITH-SCR-01, … |
Cross-cutting records
Cross-cutting records (e.g. Islamic × E&W succession) use the primary dimension’s prefix — here SUCC-SCR- — with the record title clarifying the overlay context. Do NOT mint a separate ISLAM-SUCC-SCR prefix scheme; it over-specifies.
Numbering within a prefix
Numbering starts at -01 within each (prefix × scoping record) pair. Subsequent records of the same dimension pick up where the last record left off globally — i.e. if the E&W succession pilot used SUCC-SCR-01–SUCC-SCR-08, then the next succession record (e.g. Scotland × succession) would start at SUCC-SCR-09. This produces a single continuous sequence within each dimension but no cross-dimension sequence.
Global architectural change log
When scoping records are merged, their SCRs become entries in the global architectural change log. The log is grouped by dimension prefix rather than interleaved.
Why
- Per-record self-containment. A scoping record’s §8 reads cleanly without requiring knowledge of how many SCRs exist elsewhere.
- Cross-dimension traceability.
TAX-SCR-05is obviously a tax SCR;SUCC-SCR-05is obviously succession. No need to cross-check which dimension a bareSCR-05belongs to. - Scoping programme scale. With ~230 records across 50+ jurisdictions, a global continuous sequence would become unwieldy (
SCR-1,847).
Retro-application
On Friday 17 April 2026, the E&W succession pilot’s original SCR-01–SCR-08 were retro-labelled to SUCC-SCR-01–SUCC-SCR-08 for consistency. Documents affected:
docs/superpowers/scoping/2026-04-17-ew-succession.mdv1.1 → v1.2docs/superpowers/specs/2026-04-16-ew-schema-audit.mdv1.3 → v1.4docs/superpowers/specs/2026-04-16-inheritkit-design.mdv1.11 → v1.12docs/superpowers/specs/2026-04-17-inheritkit-scoping-framework.mdv1.2 → v1.3 (§8 convention codified)docs/superpowers/scoping/ew-tax-handoff-prompt.mdv1.1 → v1.2
Codified in
Framework v1.3 §8 SCR template includes the prefix convention. All subsequent scoping records should apply it without further discussion.