Article XI gauntlet: 70% Meritboard filibuster floor, Supreme Court 7/10 majority, population ratification (Sanctuary consensus + Main Layer 80–90% supermajority), presidential veto. Lower layers (-1, -2, -3) do not vote on Charter amendments — Charter revision rights are held by the two populations whose behavioral record qualifies them to shape the ontology the civilization runs on. The highest bar in the civilization’s governance architecture.
Proposed constitutional framework extending VMSS governance architecture to extraterrestrial settlements under the Five-Planet Federation trajectory. Would have added Article XXIX establishing charter-level principles for off-Earth layer replication, treaty coordination with allied civilizations at interstellar distance, and backup vessel infrastructure standards for colonial operations.
Ratification Results
| Meritboard Filibuster Floor | 71% (met) |
| Supreme Court | 9 / 10 (met) |
| Main Layer | 87% yes (met) |
| Sanctuary Consensus | Blocked — ~2M dissenting votes in 300M population |
Lower layers (-1, -2, -3) do not vote on Charter amendments per Article XI — Charter revision rights are held by Sanctuary and Main Layer only.
Proposed Charter amendment to replace Sanctuary consensus with a 90% Sanctuary supermajority and compensate by raising institutional-tier thresholds — Meritboard filibuster floor 70%→80%, Supreme Court review 7/10→8/10. Motivated by civic-reform frustration after four Main-Layer-sponsored amendment campaigns across the prior three decades were withdrawn by their drafters at the Sanctuary deliberation window — each facing standing dissent numbering well under 1% of Sanctuary population, each abandoned before terminal certification rather than carried to a concluded vote. Withdrawn filings never conclude and therefore do not enter this register; what they left behind was a reform base convinced that sub-1% standing dissent functioned as a silent veto no procedure obligated anyone to engage. Drafters framed the proposal as preserving the gauntlet’s total rigor (institutional gates tightened to compensate for population-gate relaxation) rather than weakening it. The Meritboard coherence review rejected the compensation premise: institutional-tier thresholds (Meritboard, Court) protect doctrinal and constitutional coherence; population-tier thresholds (Sanctuary consensus, Main supermajority) protect legitimacy-of-the-governed. The two stacks are not fungible — tightening the former does not substitute for relaxing the latter. Additionally, consensus is structurally distinct from high supermajority: consensus operates as a window-deliberation mechanism in which dissenters trigger engagement, while a 90% supermajority operates as an outvoting mechanism in which dissenters become a bloc to be overridden. Converting one to the other does not adjust a threshold — it changes the political character of the Sanctuary vote itself. The Meritboard filibustered at 67%, terminating the amendment before it reached the Supreme Court. A subsequent procedural-refinement draft (LP-046.2, proposed 2191, enacted 2193 — recorded in the Federal register below) reformulates the civic-reform concern as extended-deliberation-window and formal dissenter-engagement cycles within the consensus mechanism rather than replacement of it, operating under the LP-005 / LP-038 / LP-045 failed-parent → refined-child archival pattern.
Ratification Results
| Meritboard Filibuster Floor | 67% (filibustered — below 70% floor) |
| Supreme Court | Not reached |
| Main Layer | Not reached |
| Sanctuary Consensus | Not reached |
Filibuster rationale in the Meritboard’s published opinion: the proposal’s structural premise — that institutional-tier tightening compensates for population-tier relaxation — confuses two distinct legitimacy stacks. The consensus mechanism at Sanctuary protects against drift in the ontology the civilization runs on; tightening Meritboard and Court thresholds does not address this because those bodies adjudicate coherence, not ontology legitimacy. The amendment was terminated at the coherence gate precisely because its own internal logic failed coherence review.
Proposed Charter amendment establishing fixed-tenure floors before metric-driven displacement could activate, applied across the three highest-authority roles in the civilization: the President (10-year fixed tenure aligned to the existing Article XXII.II review cycle, no mid-cycle displacement except for SCOTUS-verified incapacity or voluntary stepdown), active Meritboard members (8-year terms for primary sub-ranking seats — executive-doctrinal-leadership, legal-interpretation, federal-administration; 4-year terms for the broader 1,900-member federal-administration body under LP-007.2), and Supreme Court justices (25-year renewable terms, mid-term replacement permitted only on SCOTUS-verified misconduct or voluntary stepdown). Drafters argued from three operational concerns: in-flight work continuity at seat transition, deep-doctrinal-expertise accumulation requiring multi-decade tenure for SCOTUS specifically, and decision-making quality differentials between officials operating under predictable horizons versus those facing continuous displacement risk. The amendment would have suspended Article XXII’s continuous-update mechanic within tenure windows while preserving cycle-end contestation, on the theory that predictable rotation produces better governance than continuous rotation.
The Supreme Court rejected the amendment at 6/10 on doctrinal-coherence grounds. The Court’s published opinion identified two simultaneous contradictory specifications in the proposed text: Article XXII (unmodified by the amendment) specifies that ranking inversion triggers displacement; the amendment language specifies that displacement cannot occur within tenure. The amendment text did not specify which prevails when both conditions activate, leaving every active seat in indeterminate jurisdictional status during tenure windows where ranking inversion had occurred. Coherence review terminated the amendment on this basis.
The Court’s opinion notes the architectural significance of who voted against. Several sitting justices would have been direct beneficiaries of the 25-year SCOTUS tenure provision. The body’s majority decision against their own benefit surfaced the load-bearing argument — that the justices’ authority derives from the same continuous-update mechanism the amendment would suspend, and that protecting their seats against the metric would protect them against the system that qualified them for it. Justice Aris-7 (legal-interpretation rank 1, AGI substrate) in concurrence: “The strongest case against tenure for this Court is made by the justices themselves, whose continued legitimacy depends on the continued willingness of the metric system to displace them. We do not vote ourselves protection from the mechanism that produced us.”
The Meritboard had cleared the proposal to the Court at 71% — narrowly above the filibuster floor — but conditioned that clearance on parallel federal-tier investigation of handoff-procedure mechanisms. The Meritboard’s published note acknowledged the legitimate operational concern about transition continuity while declining the tenure-imposition solution: “Handoff-procedure mechanisms can be enacted at federal tier without Charter modification. The continuity concern is real; the proposed remedy is wrong-tier.” That federal-tier route was subsequently pursued as LP-051 (operational handoff-period specification, separately filed 2191, enacted 2192).
Ratification Results
| Meritboard Filibuster Floor | 71% (met, narrow) |
| Supreme Court | 6 / 10 (FAILED — below 7/10 majority) |
| Main Layer | Not reached |
| Sanctuary Consensus | Not reached |
The amendment marks the third consecutive Charter-tier failure (LP-001 at Sanctuary, LP-046 at Meritboard, LP-050 at Court). All three failure modes were architectural rather than political — Charter-tier proposals continue to terminate at whichever gate identifies the deepest contradiction with load-bearing canon. The continuous-update mechanism of Article XXII has now survived direct challenge at the highest tier of the civilization’s governance architecture.
Article VIII establishes that fetal backup linkage operates through the mother’s implant at detected pregnancy, with the explicit corollary that pregnancy in unimplanted populations or pregnancies undetected by implant infrastructure produce no continuity link and no fetal backup protection. The proposed amendment closes the unimplanted-pregnancy gap by establishing an independent fetal continuity-registration pathway operative once pregnancy is detected by any VMSS-recognized medical apparatus — implant-grade synchronization equipment in medical clinics, traveler-screening apparatus at gate complexes, or equivalent diagnostic infrastructure. The pathway explicitly prohibits forced maternal implantation, forced neural access, or maternal cognition capture as registration prerequisites. Registration creates a fetal continuity key without modifying the mother’s implant status; if pregnancy is later terminated after registration, the fetus revives into Main Layer autoparenting per existing Article VIII logic; if no detection occurs, no key forms. Intentional destruction of an already-created fetal continuity key is treated as continuity sabotage routed through Article XIV proportionality rather than automatic binary reassignment. Foreign visitors are notified at entry that VMSS medical detection creates fetal continuity status if pregnancy is discovered on VMSS soil.
The Sanctuary ratification vote terminated the amendment at consensus failure. Approximately 1.3 million dissenting votes in a 300-million-resident population blocked the amendment despite Meritboard 73% support, Supreme Court 8/10 affirmation, and Main Layer 82% supermajority. The Sanctuary dissenter coalition published its objection through the deliberation-window mechanism: the proposed amendment, in its framing of medical detection as continuity-key-creating, constitutes a backdoor institutional claim over pregnancy that the consent architecture cannot accommodate even in service of fetal dignity. The dissenter coalition explicitly affirmed fetal continuity as an autonomous value while rejecting the proposed implementation mechanism — pregnancy detection at clinic infrastructure converts a private medical encounter into an institutional registration event, and Sanctuary’s pregnancy-privacy commitment is load-bearing across the layer’s architecture.
The Supreme Court’s published opinion notes that the dissent surfaced a previously unspecified Article VIII tension: continuity-first reading (the architecture protects fetal continuity wherever possible, including via secondary instrumentation) versus instrumentation-contingent reading (continuity protection operates only where the mother’s implant is the registration source, preserving the implant as the locus of voluntary consent for pregnancy registration). The Court declined to resolve the tension as part of the amendment review — the amendment itself was a proposed resolution and the dissent was rejecting that resolution. The Court explicitly preserved both readings as architecturally available for future doctrinal work. Refined-child iteration is anticipated: the unimplanted-pregnancy gap remains a live architectural question and the dissenter coalition itself acknowledged that any future amendment with stronger pregnancy-privacy guarantees (consent at clinic level, deletion rights, narrower triggering conditions) would receive different consideration.
Ratification Results
| Meritboard Filibuster Floor | 73% (met) |
| Supreme Court | 8 / 10 (met) |
| Main Layer | 82% yes (met) |
| Sanctuary Consensus | Blocked — ~1.3M dissenting votes in 300M population |
Fourth consecutive Charter-tier failure. Amendment terminated on pregnancy-privacy commitment grounds despite affirmed institutional support — the dissent reasoning is canon-clarifying because it forces Article VIII’s continuity-first vs instrumentation-contingent reading into explicit doctrinal availability for future work.
The proposed Charter amendment would have established a procedural pathway for citizens to elect institutionally-facilitated end-of-life and registered anti-revival directives that supersede default backup-vessel revival. The amendment contested Article IV’s implicit continuity-by-default presumption by elevating citizen autonomy to peer status with continuity commitment — the architecture would have shifted from “you are preserved unless impossible” to “you are preserved unless you have affirmatively elected otherwise.” Three eligibility paths were specified: terminal-illness with medical board verification and 30-day reflection window; irrecoverable cognitive decline with substrate verification and family/civic court witness; and sustained-philosophical election requiring 5-year deliberation window plus multiple civic court affirmations. Advance directive registration was available to any adult citizen ahead of capacity loss. The amendment included anti-impulse safeguards: cessation under untreated mental illness, recent trauma, or impulsive election did not qualify; existing intervention architecture under Article XX accountability continued to govern those cases. Substrate equivalence per LP-045.2 ensured uniform application across biological, weight-state, and activation-pattern citizens.
The amendment cleared Meritboard at 72%, Supreme Court at 7/10, and Main Layer at 81% — passing the institutional gauntlet but terminating at Sanctuary consensus failure. The dissent margin was narrow: approximately 2.4 million dissenting votes in a 300-million-resident population, representing one of the closer failures in Charter-tier history. The Sanctuary dissenter coalition split its objection into two architecturally distinct streams. The first stream — autonomy-protective dissent — opposed the amendment on grounds that institutional facilitation of cessation creates pressure architecture that undermines the very autonomy the amendment claims to extend; a citizen in vulnerable cognitive or emotional state may be subtly pressured toward cessation by available infrastructure, and the existence of the pathway changes the choice environment of every citizen. The second stream — continuity-foundational dissent — opposed on grounds that Article IV’s continuity commitment is foundational to civilization-character, not operational specification, and any modification routes the architecture toward “service” rather than “commitment.” Both dissent streams combined to block consensus.
The Supreme Court’s published opinion noted the diagnostic value of the failure: “The amendment forces the civilization to declare whether continuity is foundational principle or instrumented service. The dissent coalition’s two streams are not in contradiction — they represent the same architectural intuition at different framings. The first holds that autonomy is endangered by infrastructure; the second holds that continuity is endangered by exception. Both arguments survive the amendment’s failure and remain available for future doctrinal work.” Justice Aris-7 in concurrence: “The civilization has chosen, by failing to amend, that continuity-by-default remains the load-bearing posture. The Court does not read this as the civilization rejecting autonomy — it reads as the civilization declining to translate autonomy into institutional infrastructure at this moment.” Refined-child iteration is plausible at 5–10 year horizon; LP-053.2 likely narrows initial scope to terminal-illness-only path with substantially stronger anti-pressure safeguards.
Ratification Results
| Meritboard Filibuster Floor | 72% (met) |
| Supreme Court | 7 / 10 (met, bare minimum) |
| Main Layer | 81% yes (met) |
| Sanctuary Consensus | Blocked — ~2.4M dissenting votes in 300M population (~0.8%) |
Fifth consecutive Charter-tier failure. The narrow Sanctuary dissent margin (~0.8%) is among the closest a Charter LP has come to clearing consensus, behind only LP-052 (~0.4%) and LP-001 (~0.67%). These filings demonstrate that Sanctuary consensus failures cluster at the boundary rather than at large dissent rates — the architecture’s deliberation mechanism produces precise outcomes near the boundary. The civilization has now adjudicated continuity-architecture against autonomy-architecture at the highest tier; the dissent reasoning is canonical and informs all future doctrinal work in this space.
The first direct internal challenge to reassignment permanence in the civilization’s history. The proposed Charter amendment would have established an upward recovery pathway from -1 Noncompliance to Main Layer, closely modeled on the allied Recovery Gradient civilization’s architecture: fifteen continuous years of sustained STI performance above a demanding floor with zero qualifying breaches earning eligibility for multi-factor recovery review — AI governance evaluation of behavioral trajectory and peer-signal data, with formal victim-impact input — and approved cases reassigned upward under a permanent public ledger notation. The pathway was scoped to -1 only; -2 and -3 were excluded by the drafters as a deliberate concession to gravity. The filing was correctly routed: Article XI itself names any change to the permanence of reassignment as structural modification requiring the full amendment gauntlet. Per LP-041 disclosure, the filing was the largest citizen-origination Charter petition in the register’s history, with signatories overwhelmingly Main Layer residents with immediate family members under punitive reassignment.
The drafters’ case rested on the immortality argument the allied civilization’s founders had raised a century earlier — that permanence applied to 200–300-year lifespans converts a single qualifying act at age thirty into a three-century consequence — now reinforced by citation of the ally’s multi-decade operational record as interpretive support under the LP-042 secondary-authority rule. Opponents cited the same record’s documented costs: measurable deterrent erosion at the Main Layer margin, victim re-contact trauma through recovery notifications, the bifurcation of the punitive-layer population into those counting down a clock and those building a life, and an STI metric asked to certify character transformation when it was architected to measure conduct. Both sides argued from the same civilization’s data. The Meritboard cleared the amendment at 73% with a published note distinguishing coherence from endorsement: the proposal was internally consistent, correctly tiered, and posed a question only the population gates could answer. The Supreme Court cleared it 7/10 at the bare minimum, exercising the constitutional-honesty mechanism in full: the opinion named the amendment’s scope explicitly — it reaches the permanence of consequence, which sits adjacent to moral causality in the founding core — and returned it to the population with that scope disclosed. The Presidency, in consultation with the Court, set the Main Layer gravity threshold at the top of the Article XI range: 90%.
Main Layer voted 81% yes. A supermajority of the civilization’s largest population voted to open the ceiling — and fell nine points short of the gravity-set bar. It is the first Charter-tier failure at the Main Layer gate. Sanctuary’s concurrent deliberation window was closed administratively at the Main failure with approximately 7.1 million standing dissents in the running tally — consensus unreachable by an order of magnitude beyond the boundary-level failures of LP-052 and LP-053. The honest reading of the result, stated in the Meritboard’s postmortem, is that the civilization is not unanimous about permanence; it is structurally conservative about amending it. Eighty-one percent sympathy is not ninety percent consent, and the nine-point gap is Article XI doing precisely what it was built to do — requiring that a change to the relationship between conduct and environment be wanted at the depth the change itself operates at. No refined-child filing is anticipated within a generational horizon: the failure was not a calibration dispute but a values determination, and the allied civilization’s Recovery Gradient continues to generate the only empirical data the next attempt will have.
Ratification Results
| Meritboard Filibuster Floor | 73% (met) |
| Supreme Court | 7 / 10 (met, bare minimum — founding-core adjacency named and disclosed) |
| Main Layer | 81% yes (below 90% gravity-set threshold — FAILED) |
| Sanctuary Consensus | Window closed at Main failure — ~7.1M standing dissents in running tally (consensus unreachable) |
Sixth consecutive Charter-tier failure, and the first to terminate at the Main Layer gate. Permanence of reassignment has now survived direct internal challenge through the full Article XI gauntlet. The result is canon-clarifying in both directions: the 81% Main vote establishes that the redemption question is genuinely alive in the population, and the dual-population rejection establishes that the architecture’s answer remains what Article XV states — the pathway back does not exist, not because no one wants it, but because the populations who hold revision rights declined to constitutionalize it at the depth required.
Proposed Charter amendment establishing continuity coverage for children born in -3 Terminal (and, by parallel clause, -2) from birth until relocation or majority. Mechanism: the child’s implant, installed through the federally facilitated channel that already serves child relocation, would carry a live vessel link synced exclusively to Main Layer fabrication facilities — no -3 infrastructure — with death before relocation processed as revival into Main Layer autoparenting under Article VIII’s existing fetal-reincarnation logic. The drafters’ frame: the clean-record doctrine promises that children inherit nothing, yet a child born in -3 lives under the civilization’s heaviest consequence — mortality — as a fact of parental geography. Death-as-relocation would extend to the born child the protection the Charter already extends to the terminated fetus, exercised through the standing right the child already holds.
The institutional gates cleared it. Meritboard 74%, with a reservation noting the filing’s honest tier placement — a change to what terminal severance means is Charter work, not federal work. The Supreme Court cleared 7/10 with the amendment’s scope named per Article XI: it does not reach the founding core, but it opens the -3 boundary that LP-004.2 had recently sealed, and the concurrence named the consequence — a live vessel link operating inside -3, however narrowly scoped to children, is the infrastructure class §17.1.5’s captive-revival economics are priced against. A child-shaped hole in a hardware-absolute boundary is a hole. Main Layer ratified at 84%.
The amendment died in the Sanctuary consensus window. The dissent bloc — approximately 2.1 million votes, anchored in continuity-architecture and boundary-integrity networks — did not converge across the full deliberation window and published its objection through the window mechanism, as the LP-052 dissenters had before them: the relocation right is the remedy the architecture already provides — exercisable at any age, federally facilitated, free — and the amendment would convert -3’s hardware-absolute finality into a policy line with one exception, and one exception is a category change. The bloc explicitly affirmed the moral weight of the terminal-born child’s position while rejecting the mechanism, and the Court’s LP-052 concurrence — continuity-first versus instrumentation-contingent readings of Article VIII — resurfaced in the published record as the still-unresolved axis. The drafting coalition refiled the surviving remnant at federal tier within a year: LP-068, which asks nothing of the boundary.
Ratification Results
| Meritboard Filibuster Floor | 74% (met) |
| Supreme Court | 7 / 10 (met — boundary scope named and disclosed) |
| Main Layer | 84% yes (met) |
| Sanctuary Consensus | Blocked — ~2.1M dissenting votes in 300M population |
Seventh consecutive Charter-tier failure; the amendment ladder stands 0-for-7. The dissent is canon-clarifying: terminal severance’s hardware absolutism is a category the ratifying population declines to make exception-bearing — the remedy for terminal-born children is the relocation right, and the register’s answer to the residual gap is LP-068.
Omnibus Charter amendment relocating five enumerated schedules out of Article III and Article XXVII to the tier that already recalibrates them, and replacing each with an enabling grant plus the principle the Charter retains. The instruments touched: III.II’s per-hour overtime cascade, III.IV’s downward-conversion forfeiture band, III.V’s retention schedule and its pre-positioning lookback windows, III.VII and III.VIII’s savings-circulation triggers, rates and windows, and Article XXVII’s escalation rate. Each lands in a receiving instrument at federal tier: the overtime cascade in a schedule instrument the amendment mints under the name the Charter itself already used — the Overtime Premium Protocol — the settlement family in the Central Banking Authority, the mandate parameters in LP-069 and LP-070, and the escalation rate in LP-064, which already held the measurement base and specified around the rate. The filing is a paired dual-track instrument: it ran the Article XI amendment ladder that removes the schedules from the Charter and, in the same window, the concurrent Article XXV.VI federal-enactment ladder that re-enacts each schedule in its receiving instrument — so the five-layer population Article XXV.VI requires for federal law ratified the receivers directly, not the narrower Article XI electorate alone. Each track was gated and certified independently; either one failing would have terminated the draft.
The drafters’ frame, which the institutional gates adopted almost verbatim: the amendment introduces no tier doctrine, it completes one the corpus already declares. Whitepaper §10.6.1 states that the Charter carries structural principles, placement criteria, and constraints on what instruments beneath it can do, and that what it does contain is indexed and everything below it consolidated at VMSS Laws; the routing test asks whether a rule controls who goes to which layer, and a garnishing rate does not. The schedules were founding-era parameters parked at constitutional tier, not constitutional content, and every one of them already sat beside a federal instrument operating under Article XXV.VI — instruments that administered the adjacent mechanics and specified around the rates, though the rates themselves stood as Charter text until this filing enacted them at federal tier. The amendment reaches nothing that Article XI’s own lock protects — no behavioral threshold, no phasing mechanic, no descent trigger, no permanence of reassignment — and it removes no article. The Charter is thirty headings before the amendment and thirty after.
It passed where seven amendments had failed because it changes no present magnitude and no substantive entitlement, and the drafting made that property auditable rather than asserted. Every relocated magnitude re-enacts at its receiving instrument at the identical value, and the Charter keeps the derivation rule that binds the overtime premium to the Article III.I dividend baselines — so the demoted figures remain recoverable from retained Charter text by the derivation the receiving Protocol carries. What the amendment does change is named on the record rather than waved away: it moves the competent lawmaking tier, the future ratification constituency, and the degree of entrenchment for each relocated schedule — a schedule that was supreme Charter text, alterable only through Article XI, becomes federal law recalibrated through the Article XXV.VI ladder, and the lower layers gain a standing vote on it they did not hold while it was constitutional. The Supreme Court’s opinion named that scope on both tracks: the founding core is untouched and no present magnitude or entitlement moves, while procedural standing, constitutional protection, and the amending constituency do. The Sanctuary window closed on the tally certified below — full agreement, zero standing no, the first Charter filing to reach it — the published objections in the window concerning drafting sequence rather than the rule, and the Presidential veto was not exercised on either track. The Meritboard’s coherence review recorded the reservation the record has kept since: an amendment that is easy to ratify because it is empty of substance is exactly the amendment a civilization should read twice, and the filing was published article by article so that the next reader can.
Ratification Results
| Meritboard Filibuster Floor | 88% (met — certified against both floors: the 70% amendment floor and the 60% federal floor) |
| Supreme Court | 9 / 10 (met — scope named on both tracks: no founding-core reach and no present magnitude or substantive entitlement altered, while the competent lawmaking tier, the ratification constituency, and the degree of entrenchment change for each relocated schedule) |
| Main Layer | 81% yes (met — against the 80% amendment point and a 75% federal point, both set at filing) |
| Sanctuary Consensus | Reached — closing tally 98% yes · 0 no votes · 2% abstaining: full agreement with zero standing dissent certifies consensus, and 98% clears the 90% federal Sanctuary floor in the same count |
| Lower-Layer Aggregate | 82% yes (met — against a 75% federal point set at filing; the layers Article XXV.VI includes for federal reach cast the ballot Article XI never gave them) |
| Presidential Disposition | Veto not exercised — certified at window close (2299). Both population set points were fixed at filing (2296) after Article XXII consultation with the Court, and neither was altered after the window opened |
First Charter-tier success; the amendment ladder stands 1-for-8. The record is legible in one line: the seven failed filings each proposed to change what the civilization is — five of them dying at a population gate, two before reaching one — and this one changed no present magnitude and no substantive entitlement, moving only the competent tier, the ratification constituency, and the entrenchment of each relocated schedule. Because it carried a concurrent Article XXV.VI federal track, it was the widest ballot in the register’s history — all five layers voting, where an Article XI filing polls only Sanctuary and Main. The Presidency set the Main Layer amendment point at the floor of the 80–90% band, the gravity of the change being the range’s own measure under Article XI; it is the lowest amendment point ever set for a Charter filing, and the register carries the relocation article by article above.
Article XXV.VI drafting ladder: 60% Meritboard filibuster floor, 6/10 Supreme Court majority, three-track population ratification (Sanctuary 90%+, Main 70–80%, lower-layer aggregate 70–80%), presidential veto. Binds every layer; cannot reach the founding core.
Adjusted Primary Job Subsidy hourly rate for credentialed medical research positions across all layers, aligning rate structure with the longevity-research R&D pipeline and creating parity between fabrication-intensive and cognitive-intensive civilizational infrastructure roles.
Ratification Results
| Meritboard | 94% (met) |
| Supreme Court | 10 / 10 (met) |
| Sanctuary | 91% yes (met) |
| Main Layer | 93% yes (met) |
| Lower-Layer Aggregate | 84% yes (met) |
Proposed federal mandate establishing minimum Meritboard engagement thresholds for Main Layer residents — participation rates in civic health metric, petition signature windows, and expert-panel response cycles. Framed as regulatory calibration. Dual-key classification determined the aggregate effect would establish a new layer-qualifying metric, converting the proposal into structural modification of Meritboard selection architecture.
Dual-Key Disposition
| Meritboard Classification | Structural |
| Supreme Court Classification | Structural |
| Reroute | Article XI amendment gauntlet |
| Petitioner Action | Not pursued |
Proposed that visitors to lower layers operate under the destination layer’s backup vessel failure rate, not their home-layer rate. A Main resident visiting -1 would have carried -1’s ~1-in-10,000 risk; visiting -2, ~1-in-1,000; visiting -3, no revival. Backup vessel resources consumed during the visit would have been drawn from local infrastructure. Intended to close the mortality-asymmetry exploit where upper-layer visitors took risk-free positions in lower-layer dangerous work (Colosseum-classified enterprises, hazardous construction, combat-adjacent contracts). Failed at the Sanctuary ratification gate — 71% yes, well below the 90% federal floor — on grounds that asymmetric mortality risk for consenting upper-layer visitors was itself an acceptable feature of the consent architecture, not an exploit. The underlying concern was later addressed through LP-004.2’s consent-scoped redraft — compromised-consent protections in -1/-2 and mandatory vessel-link suspension at the -3 boundary — rather than destination-rate parity.
Ratification Results
| Meritboard | 63% (met, narrow) |
| Supreme Court | 6 / 10 (met, bare minimum) |
| Sanctuary | 71% yes (below 90% floor — FAILED) |
| Main Layer | 72% yes (met, narrow) |
| Lower-Layer Aggregate | 91% yes (met) |
Redraft of LP-004 addressing the Sanctuary objection that asymmetric mortality risk for consenting upper-layer visitors was an acceptable feature of the consent architecture, not an exploit to be closed. The second pass resolves the asymmetry on two tracks. In -1 and -2, parity applies only where consent is structurally compromised: mass-commercial recruitment of upper-layer workers into lower-layer hazardous work under misleading representation of backup vessel coverage, and insurance and contract clauses that obscure the mortality differential from the participant. Individual consenting visitors whose choice is informed retain home-layer parity in those layers — the original consent architecture preserved where backup coverage operates. In -3 Terminal, backup vessel coverage does not cross the boundary: entry requires documented vessel-link suspension, severing the link for the duration of the visit and restoring it on exit. Death inside -3 is final for visitor and resident alike. The terminal clause is an infrastructure-integrity rule, not a risk-transfer mandate — the layer whose design premise is permanent mortality admits no vessel-backed participant, which dissolves the Colosseum-classified exploit categorically. The two-track structure satisfied the Sanctuary autonomy objection while closing the commercial-recruitment exploit that drove the original filing.
Ratification Results
| Meritboard | 78% (met) |
| Supreme Court | 8 / 10 (met) |
| Sanctuary | 92% yes (met) |
| Main Layer | 79% yes (met) |
| Lower-Layer Aggregate | 88% yes (met) |
Proposed federal classification of VMSS sovereignty breach (unauthorized territorial incursion by foreign actor, coordinated sovereignty violation, or hostile-state aggression at the border) as a capital federal offense triggering automatic -3 reassignment, with continued aggressive conduct from within -3 then escalating to the national defense track. Intended as a procedural narrowing of the existing Article XXV.IV lethal-response ladder — not an expansion. Failed at the Sanctuary ratification gate — 89% yes, one percentage point below the 90% federal floor — on grounds that inserting a reassignment step between sovereignty breach and defensive response risked extending operational latency in precisely the scenarios where the civilization needs the shortest possible decision window. Redrafted as LP-005.2 with the latency objection addressed.
Ratification Results
| Meritboard | 88% (met) |
| Supreme Court | 8 / 10 (met) |
| Sanctuary | 89% yes (below 90% floor — FAILED) |
| Main Layer | 84% yes (met) |
| Lower-Layer Aggregate | 79% yes (met) |
Doctrinal distinction, for the record: the operative canon under Article XXV.IV External Force Doctrine applies lethal response to sovereignty breach at the layer the breach occurs. LP-005 proposed an undifferentiated reassignment-first narrowing, which failed on latency grounds. The scale-tier redraft resolved the latency concern by branching the response protocol at classification time by actor-count threshold — a procedurally clean rule easy for classification panels to apply. Operated as canon for thirty years before accumulated edge-case evidence motivated the judgment-based redraft at LP-005.3.
Response protocol branches at first-detection classification on an actor-count threshold. Single-actor incidents (individual foreign operator, corporate-espionage instrument, intelligence asset under recall pressure) follow the reassignment-first path: automatic -3 reassignment, with lethal force reserved for continued aggression from within the terminal layer. Small-coordinated incidents (2–25 operationally coordinated actors) also follow the reassignment-first path, on the reasoning that sub-squad-scale formations do not meet the threshold at which decision latency becomes civilizationally load-bearing. Large-coordinated incidents (26+ operationally coordinated actors, or any formation with military-grade armament tier or hostile-state attribution regardless of headcount) retain the original XXV.IV immediate-lethal-response ladder without modification, preserving the zero-latency path Sanctuary identified as load-bearing for the coordinated-formation case. Classification performed by the Supreme Court emergency-review subsystem with Meritboard intelligence-architecture panel providing the threat-classification input.
Ratification Results
| Meritboard | 84% (met) |
| Supreme Court | 9 / 10 (met) |
| Sanctuary | 94% yes (met) |
| Main Layer | 86% yes (met) |
| Lower-Layer Aggregate | 81% yes (met) |
⬥ Pillar Federal Law
Supersedes LP-005.2’s actor-count threshold with a character-weighted classification framework. After thirty years of operation, accumulated edge-case review surfaced two consistent failure modes of the numerical threshold: small formations of professional operators with military-grade equipment were mis-classified into the reassignment-first path when operational character clearly warranted immediate lethal response, and larger formations of poorly-armed hobbyists triggered immediate lethal response under the coordinated-formation tier when the actual threat profile did not warrant it. The third pass replaces the 26-actor threshold with a multi-factor classification framework: the Supreme Court emergency-review panel weighs headcount, armament tier, organizational sophistication, threat velocity, and attribution together rather than applying any single binary cutoff. Meritboard Intelligence-Architecture Panel continues to feed the threat-assessment input.
Adds a classification-review window: the first 24 hours of response are provisional, subject to Supreme Court emergency reversal if first-detection facts prove materially inaccurate. A reversal shifts response branch mid-operation; consequences already delivered are not retroactive, but subsequent protocol transitions to the corrected branch. This is the first federal statute in the external-force domain to introduce post-commitment reversibility — doctrinally significant because prior XXV.IV architecture treated classification as terminal at first detection. The narrow reversibility window responds to accumulated experience that classification under extreme-urgency conditions occasionally gets the operational character wrong in the first minutes.
The Coalition Breach Attempt simulation (simulations.html) operates cleanly under LP-005.3: the 200-member operationally-coordinated armed formation classifies as coordinated-formation under the character-weighted framework (headcount + armament tier + organizational sophistication + attribution all load in that direction), triggering immediate XXV.IV lethal response at the breach layer. Reversibility window did not apply because first-detection classification was confirmed by subsequent evidence.
Ratification Results
| Meritboard | 89% (met) |
| Supreme Court | 10 / 10 (met) |
| Sanctuary | 96% yes (met) |
| Main Layer | 88% yes (met) |
| Lower-Layer Aggregate | 84% yes (met) |
Requires upper-layer visitors engaged in commercial activity within lower layers to publicly disclose home-layer status and backup vessel coverage terms. Response to the deathless-gold-rush and immortal-influencer phenomena, in which risk-free upper-layer visitors extracted economic value and produced deceptive “authentic lower-layer lifestyle” content in dangerous environments. Partial remedy — drove industry adaptation but did not close the underlying mortality-asymmetry exploit. Remained the load-bearing federal instrument on the mortality-asymmetry question after LP-004 Backup Vessel Parity failed at the Sanctuary gate; since LP-004.2, disclosure operates alongside the redraft’s compromised-consent protections and terminal boundary-suspension clause.
Ratification Results
| Meritboard | 68% (met) |
| Supreme Court | 7 / 10 (met) |
| Sanctuary | 92% yes (met) |
| Main Layer | 74% yes (met) |
| Lower-Layer Aggregate | 88% yes (met) |
Proposed curved per-district representation on Meritboard federal-administration and civic-engagement rankings: Sanctuary, -1, -2, and -3 receiving one seat per district; Main Layer receiving one seat per five districts. Intended to equalize representational weight across population-imbalanced layers, preventing Main’s numerical dominance from producing single-layer control of Meritboard composition. Failed at the Sanctuary ratification gate — 85% yes, below the 90% federal floor — on grounds that per-district representational curvature embeds a distributive metric into a competence ranking system the Charter grounds on demonstrated individual conduct. The underlying concern over Main-Layer concentration was partially addressed through metric-category separation within the Meritboard itself rather than through seat-allocation curvature.
Ratification Results
| Meritboard | 65% (met) |
| Supreme Court | 7 / 10 (met) |
| Sanctuary | 85% yes (below 90% floor — FAILED) |
| Main Layer | 72% yes (met, narrow) |
| Lower-Layer Aggregate | 87% yes (met) |
⬥ Pillar Federal Law
Redraft of LP-007 addressing the Sanctuary objection that per-district representational curvature embedded a distributive metric into a competence ranking system grounded on individual conduct. The second pass narrows the curvature’s scope: curved per-district allocation (Sanctuary, -1, -2, -3 at one seat per district; Main at one seat per five districts) applies only to federal-administration sub-ranking seats — the sub-ranking that produces pool membership for executive and policy-implementation roles where layer-population imbalance produces policy-capture risk. Civic-engagement rankings, doctrinal-leadership rankings, legal-interpretation rankings (which produce the Supreme Court pool), and all other sub-rankings retain pure conduct-based composition without geographic curvature. The narrowing preserved the Charter’s individual-conduct grounding at every point where structural consequence is heaviest, while permitting a distributive adjustment at the single sub-ranking where the population-imbalance concern had load-bearing operational effect.
Ratification Results
| Meritboard | 73% (met) |
| Supreme Court | 8 / 10 (met) |
| Sanctuary | 93% yes (met) |
| Main Layer | 74% yes (met) |
| Lower-Layer Aggregate | 85% yes (met) |
Tightens the §16 consent framework for neural diving recordings. Consent may be revoked for existing archived recordings at any time by the participant, with automatic purging across ImmersionTube infrastructure, Memory Library catalogues, and derivative-work indexing. The prior framework would have permitted revocation prospectively only; this draft made revocation retroactive across the civilization’s sensory-media corpus. Failed at the lower-layer aggregate ratification gate — the retroactive-purge mechanism raised documentation-integrity objections in cooperative-hosted sensory archives. A redraft with narrower retroactive scope is expected on the next filing window.
Ratification Results
| Meritboard | 66% (met) |
| Supreme Court | 7 / 10 (met) |
| Sanctuary | 93% yes (met) |
| Main Layer | 71% yes (met) |
| Lower-Layer Aggregate | 68% yes (below 70% floor — FAILED) |
Federal confirmation that -3’s customary Colosseum classification — under which informed gate-contract entry releases the operator from liability for fatalities within the perimeter — does not export to upper layers. Operators in Sanctuary, Main, -1, or -2 attempting to claim Colosseum-equivalent immunity through gate-contract language remain prosecutable under standard harm provisions. Filed after a Main Layer operator attempted the framing.
Ratification Results
| Meritboard | 78% (met) |
| Supreme Court | 9 / 10 (met) |
| Sanctuary | 96% yes (met) |
| Main Layer | 81% yes (met) |
| Lower-Layer Aggregate | 73% yes (met, narrow) |
Triage protocol for backup vessel fabrication when simultaneous revival demand exceeds proxy installation capacity during mass-casualty events — natural disasters, large-scale accidents, ally-territory incidents. Queue precedence: children first, then medical-critical cases, then chronological order of death-event registration. All revivals still occur under the civilization’s continuity commitment; priority affects sequence only when capacity is constrained.
Ratification Results
| Meritboard | 91% (met) |
| Supreme Court | 10 / 10 (met) |
| Sanctuary | 94% yes (met) |
| Main Layer | 89% yes (met) |
| Lower-Layer Aggregate | 86% yes (met) |
Codifies minimum developmental, institutional, AI-caretaker ratio, outcome-audit cadence, and facility-quality standards across the civilization’s autoparenting infrastructure. Drafted over 3.5 years with extensive input from developmental-science SADs, the Meritboard’s education-and-outcome ranking, and autoparented-cohort representative councils. Passed near-unanimously at the Sanctuary supermajority gate in recognition of autoparenting’s structural centrality to the clean-record inheritance architecture.
Ratification Results
| Meritboard | 96% (met) |
| Supreme Court | 10 / 10 (met) |
| Sanctuary | 99% yes (met, near-unanimous) |
| Main Layer | 94% yes (met) |
| Lower-Layer Aggregate | 88% yes (met) |
Federal proposal to re-equalize the role-scoped curved per-district Meritboard federal-administration representation established by LP-007.2 back toward proportional-by-population allocation (restoring Main Layer’s numerical weight in that sub-ranking). Motivated by Main Layer residents arguing that their 3-billion population warranted proportional representation in federal-administration roles. Failed at both Sanctuary and lower-layer ratification tracks — Sanctuary voted to preserve the curved system it had ratified six years earlier, and lower layers defended their amplified per-district weight. Three-track architecture held.
Ratification Results
| Meritboard | 61% (met, razor) |
| Supreme Court | 6 / 10 (met, bare minimum) |
| Sanctuary | 72% yes (below 90% threshold — FAILED) |
| Main Layer | 84% yes (met, strong) |
| Lower-Layer Aggregate | 51% yes (below 70% threshold — FAILED) |
Supreme Court-drafted federal law codifying the drone-recovery mechanism for citizens whose implant tamper attempts trigger hardware-level failsafes outside VMSS borders. Consolidates years of case-by-case Article XIV adjudication into operational statute specifying drone-deployment authority, ally coordination protocol, and citizen processing upon retrieval. Rare example of the Supreme Court exercising advisory drafting authority under Article XXV.VI — the Court typically interprets, rarely drafts.
Ratification Results
| Meritboard | 89% (met) |
| Supreme Court | 10 / 10 (met, drafters) |
| Sanctuary | 96% yes (met) |
| Main Layer | 87% yes (met) |
| Lower-Layer Aggregate | 82% yes (met) |
Fee schedule levied on foreign sovereignties whose operators repeatedly contaminate VMSS orbital bands with debris originating from foreign operations. Published rates vary by diplomatic tier — Federation Treaty allies exempt under treaty cooperation clauses, non-allied states at standard rate, hostile states at premium rate plus revocation of published-corridor coordination privileges. Implements §23.4 orbital sovereignty enforcement through economic rather than military instrument.
Ratification Results
| Meritboard | 82% (met) |
| Supreme Court | 8 / 10 (met) |
| Sanctuary | 93% yes (met) |
| Main Layer | 86% yes (met) |
| Lower-Layer Aggregate | 77% yes (met) |
Implementing specification under LP-045.2 (Pillar): codifies operator schedules pursuant to LP-045.2’s extensibility clause rather than as independent doctrine — where a substrate-type schedule below diverges from LP-045.2’s state-character classes, LP-045.2 governs. Codifies the functional-equivalence continuity guarantee across all civic-equal substrates. Biological residents are serviced by backup vessel fabrication and brain-pattern restoration; AGI residents by weights + architecture + activation-context snapshot; ASI residents by recursive state envelope; Cyborg residents by hybrid schedule matching their biological/synthetic composition. The Charter guarantee is substrate-neutral; the mechanism is substrate-specific. Clarifies what §22 civic equality operationally entails for continuity infrastructure that §17 described in biological terms only.
Ratification Results
| Meritboard | 84% (met) |
| Supreme Court | 9 / 10 (met) |
| Sanctuary | 95% yes (met) |
| Main Layer | 88% yes (met) |
| Lower-Layer Aggregate | 79% yes (met) |
Specifies standing categories for §17.4 archive access beyond the pre-existing family-standing query window. Research-standing requires Meritboard civil-research panel review; criminal-investigation standing requires Supreme Court warrant under Article XIV; diplomatic standing operates under Federation Treaty identity-verification clauses. Revival-identity subsystem remains sealed except to direct descendants. The archive’s stated purposes were already doctrine; this entry operationalized the standing-and-access layer that prior canon left under-articulated.
Ratification Results
| Meritboard | 87% (met) |
| Supreme Court | 10 / 10 (met, drafters) |
| Sanctuary | 94% yes (met) |
| Main Layer | 85% yes (met) |
| Lower-Layer Aggregate | 81% yes (met) |
Originated as a regulatory petition by a coalition of districts whose water table was measurably affected by a neighboring district’s ratified industrial regulation. Dual-key classification determined the scope-of-effect exceeded the scope-of-authority of the originating district; rerouted to federal track. The resulting federal statute codified the general routing rule: where a regulatory action produces measurable effect on residents outside the ratifying district, the governing tier escalates to the smallest tier containing the full affected population. Not a new tier — a cleaner escalation rule under the existing Article XXVIII / §10.6 hierarchy.
Dual-Key Disposition & Federal Ratification
| Meritboard Classification | Supra-district externality |
| Supreme Court Classification | Supra-district externality |
| Reroute | Article XXV.VI federal track |
| Meritboard (federal vote) | 81% (met) |
| Supreme Court (federal vote) | 8 / 10 (met) |
| Sanctuary | 93% yes (met) |
| Main Layer | 84% yes (met) |
| Lower-Layer Aggregate | 76% yes (met) |
Designates the civic educational floor — literacy, numeracy, civic-doctrine fluency, STI mechanics, Charter comprehension, substrate-equality orientation — as floor content under §4.4 rather than graduated investment. Floor content is uniform across layers; above-baseline educational intensity remains graduated and layer-varied. Upper-layer investment coalitions challenged via dual-key, arguing the statute established a new distributive metric. Dual-key classification determined the specification operated as calibration within existing floor architecture, not structural modification; challenge denied, federal enactment proceeded. Addresses the generational-scale concern that conduct-based stratification presupposes a uniform educational floor.
Dual-Key Challenge & Ratification
| Meritboard Classification (challenge) | Calibration, not structural |
| Supreme Court Classification (challenge) | Calibration, not structural |
| Meritboard | 86% (met) |
| Supreme Court | 9 / 10 (met) |
| Sanctuary | 97% yes (met) |
| Main Layer | 89% yes (met) |
| Lower-Layer Aggregate | 83% yes (met) |
Clarifies which acts by VMSS citizens abroad carry layer-status prosecution home versus which remain territorially scoped. Three-rule framework: (1) acts matching the citizen’s own-layer prohibited conduct always carry (status-permanent doctrine); (2) acts legal abroad but prohibited only under higher-layer civic floor do not carry against the citizen’s home layer; (3) acts involving backup vessel infrastructure, the implant network, or VMSS-chartered sovereign footholds always carry regardless of territory under Article XVIII network attribution. Consolidates scattered §19.11 and §26.1 cases into operational doctrine.
Ratification Results
| Meritboard | 83% (met) |
| Supreme Court | 9 / 10 (met) |
| Sanctuary | 94% yes (met) |
| Main Layer | 86% yes (met) |
| Lower-Layer Aggregate | 78% yes (met) |
Establishes the consent architecture for mind-state traces generated during neural dive sessions. Pilot-mode sessions produce partial-control residue in the piloted party’s cortical record; Audience-mode sessions produce passive-observation traces in the observer’s record. Prior practice varied by operator — some archives retained traces indefinitely for institutional purposes, others purged on session close, none disclosed the retention posture to participants at the consent step. The law specifies three retention tiers, each requiring explicit session-time election by the participating party rather than operator default: immediate purge (trace deleted within 24 hours of session close, operator retains only the non-identifying session-metadata log), participant-held archive (trace encrypted to the participant’s implant key, accessible only to the participant, no operator retention), and institutional archive with participant-held key (trace retained by the operator for educational, judicial, or research purposes, but only decryptable with the participant’s affirmative key release). Operators offering only the third tier must disclose the limitation at the intake screen and may not present it as default. Decryption events log to the participant’s standard privacy-audit stream under Article II STI architecture. Does not override STI-mandated or judicial-review-mandated retention orders, which operate on a separate track under Article XX accountability. Closes the neural-dive-era gap between technical capability and consent doctrine.
Ratification Results
| Meritboard | 85% (met) |
| Supreme Court | 10 / 10 (met) |
| Sanctuary | 97% yes (met) |
| Main Layer | 88% yes (met) |
| Lower-Layer Aggregate | 82% yes (met) |
Early-founding-era federal proposal to mandate a maximum inter-sync interval for backup vessel continuity — residents allowing their last sync to age beyond a ninety-day ceiling would incur automatic implant notification, a secondary sixty-day grace notification, and, at the 180-day mark, a mandatory administrative sync scheduled at the nearest fabrication proxy without the resident’s further consent. Intended to close a continuity gap surfacing in the first founding generation’s mortality data: a sub-population of residents was drifting into fatal accidents with sync intervals approaching a year, and revival attempts on stale backups were producing consciousness continuity failures at rates that the continuity doctrine treated as structural. Failed at the Main Layer ratification gate — 66% yes, below the 70% floor — on grounds that mandatory administrative sync without moment-of-sync consent violated the Article V bodily autonomy principle in a domain (intimate mind-state capture) where the autonomy principle was load-bearing. Sanctuary ratified at 93%. Redrafted as LP-038.2 with the administrative-sync mandate replaced by a notification-plus-family-contact architecture.
Ratification Results
| Meritboard | 76% (met) |
| Supreme Court | 7 / 10 (met) |
| Sanctuary | 93% yes (met) |
| Main Layer | 66% yes (below 70% floor — FAILED) |
| Lower-Layer Aggregate | 74% yes (met) |
Replaces LP-038’s mandatory administrative-sync mechanism with a notification-and-contact architecture that preserves continuity coverage without overriding moment-of-sync consent. At the ninety-day interval, the implant surfaces a sync notification to the resident; at 180 days, the notification escalates to a civic-contact flag visible to the resident’s designated next-of-kin under the Article IV continuity architecture; at 365 days, the resident’s layer-standard continuity officer places a direct outreach call, not to compel a sync, but to confirm the lapse is intentional and to record the resident’s continuity election. A resident who declines sync at all three contact points is logged as elective-lapse rather than administrative-lapse — revival attempts against stale backups in the elective-lapse class are performed at the operator’s standard rate without the ambiguity that motivated the original mandate. The civilization accepts that some fraction of the population will elect lapse; the statute requires only that the election be informed and recorded, not that it be prevented. Early operational data after enactment showed the notification architecture captured most of the continuity-gap cohort LP-038 had been aimed at — the residents drifting into stale-sync mortality were doing so through inattention, not election, and the notification architecture resolved the inattention cohort while leaving the elective cohort’s autonomy intact. Has operated without substantive challenge for over seventy-five years.
Ratification Results
| Meritboard | 88% (met) |
| Supreme Court | 10 / 10 (met) |
| Sanctuary | 95% yes (met) |
| Main Layer | 82% yes (met) |
| Lower-Layer Aggregate | 79% yes (met) |
⬥ Pillar Federal Law
Formalizes the procedural boundary between an Academy capstone paper’s status as analytical tool (reference document for institutional planning) and its status as live policy dependency (instrument the civilization operationally relies on). The distinction became load-bearing after R11 Technology Dependency Atlas — an Academy capstone that began as a planning reference and accumulated institutional reliance until Meritboard operations panels were citing its dependency chains in live continuity-risk decisions without the paper ever having cleared a ratification ladder. Three-tier adoption procedure: Tier I Analytical (default status; paper is available, citable, advisory; no institutional reliance); Tier II Operational (Meritboard domain-panel majority vote plus Supreme Court advisory review formalizes institutional reliance on specific findings; paper becomes subject to the same audit-cycle cadence as federal regulations); Tier III Canonical (full Article XXV.VI federal ratification converts the paper’s findings into binding doctrine; reached in R11’s case in 2119). The procedure applies retroactively to any capstone on which institutional reliance has already developed — a twelve-month audit of active Meritboard dependencies at enactment surfaced nine capstones operating at de facto Tier II without formal elevation, and the audit transitioned each to explicit Tier II or demoted its institutional reliance to Tier I pending domain-panel review. Subsequently operated as the standard template for every Academy capstone whose analytical content reaches operational weight.
Ratification Results
| Meritboard | 90% (met) |
| Supreme Court | 10 / 10 (met) |
| Sanctuary | 96% yes (met) |
| Main Layer | 85% yes (met) |
| Lower-Layer Aggregate | 73% yes (met, narrow) |
Establishes the cost-recovery, materiel-sharing, and joint-command architecture triggered when VMSS executes a Tier-4 external-force response on a Federation Treaty ally’s behalf under Article XXV.IV alliance reciprocity. Prior to enactment, reciprocity obligations were Charter-level clear (an attack on a treaty ally triggers Tier-4 response directly, bypassing the sanctions ladder), but the operational architecture of who pays for the response, how shared materiel is deployed, and which party holds command of joint operations was governed by case-by-case Presidential directive. The protocol specifies a three-phase architecture: Phase I (Response Commitment) — VMSS deploys force on reciprocity grounds; the ally’s obligation at this phase is intelligence-sharing and logistical clearance, not financial. Phase II (Joint Operations) — if the engagement extends beyond initial response, a joint-command panel forms with VMSS Presidency and ally’s equivalent executive authority; cost-sharing is indexed to the pre-engagement force-capacity ratio between signatories, settled on a post-engagement reconciliation cycle. Phase III (Reconstruction) — for engagements resulting in territorial or infrastructure reconstruction within the ally’s jurisdiction, a reconstruction burden-share is negotiated under the treaty’s baseline reciprocity clause; VMSS’s contribution does not require Article XXVIII petition because the reconstruction spend falls under the treaty’s pre-ratified reciprocity scope. Supreme Court external-affairs bench audits cost-recovery settlements; significant deviations from the force-capacity ratio trigger automatic Article XX accountability review. The protocol closes the operational gap between Charter-level reciprocity commitment and operational-level execution architecture — a gap that had widened across the first eighty years of the Federation Treaty’s operation as treaty allies accumulated and the case-by-case directive mechanism began producing inconsistent precedent.
Ratification Results
| Meritboard | 87% (met) |
| Supreme Court | 10 / 10 (met) |
| Sanctuary | 95% yes (met) |
| Main Layer | 84% yes (met) |
| Lower-Layer Aggregate | 72% yes (met, narrow) |
⬥ Pillar Federal Law
Codifies who may originate a draft for federal or Article XXVIII consideration and what disclosure must accompany any filing. Five-field disclosure mandate at filing time: (1) originating body (Presidency, Meritboard domain panel, Supreme Court advisory drafting, citizen coalition, AI Governance maintenance panel, Academy curriculum council — the enumerated legitimate origination sources); (2) authorship character (Court-advised, Meritboard-authored, coalition-authored, or maintenance-panel-authored); (3) institutional interest (whether the drafting body holds a direct operational or administrative stake in the proposal’s outcome, with mandatory recusal of any sub-panel member whose personal STI, role-continuity, or financial position is materially advantaged by ratification); (4) filing class (interpretive clarification of existing statute, wholly new law, superseding redraft of a prior LP entry, or rerouted-and-refiled after dual-key classification); (5) auxiliary sources (Academy capstones, Resource essays, simulations, or analytical models cited as drafting input, distinguishing Tier I analytical from Tier II operational status under LP-039). Filings missing any field return to the drafter for completion before the Meritboard 60% filibuster floor clock begins. Produces a legislative-provenance ledger for every LP entry going forward and retroactively annotates the existing archive via Meritboard audit review on the standard 8-year cycle. Closes the general rule behind draft origination that the law-polling archive had been demonstrating in practice since founding without explicit statute.
Ratification Results
| Meritboard | 91% (met) |
| Supreme Court | 10 / 10 (met) |
| Sanctuary | 96% yes (met) |
| Main Layer | 87% yes (met) |
| Lower-Layer Aggregate | 81% yes (met) |
Creates a review trigger fired when Metric-Gated Domain membership becomes so functionally necessary to secure ordinary safety, relational stability, or service adequacy within a layer or district that the private-community architecture may be substituting for the civic floor in substance rather than supplementing it. The law does not regulate MGDs directly. It regulates the relationship between MGD density and civic-floor adequacy — testing whether the floor has fallen too low relative to what the private-community layer is being forced to provide. Trigger conditions: (a) MGD membership penetration exceeds 40% of a layer or administrative district within a defined service category (housing security, medical continuity, educational baseline above §4.4 floor-minimum, child-safety infrastructure, elder-care continuity), and (b) non-member residents in the same geography demonstrate measurably degraded access to the same service category relative to the civilization-wide baseline. When both conditions fire, the Meritboard civic-floor panel opens a federal adequacy review under Article XXV.VI. The review outcome is not MGD regulation. It is an audit of whether the civic floor itself is intact at that geography. If the review finds the floor has eroded, remediation runs through the standard civic-floor instruments — infrastructure spend, service-provisioning obligations on the chartering institutions, or §4.4 floor-content review — not through MGD restriction. Debate ran narrower than usual around lower-layer autonomy concerns: the -1 and -2 coalitions held that any floor-adequacy review regardless of mechanism implies a floor definition applicable to their populations, which some cooperative-territory readings of Article III had resisted. Enacted after the scoping language was tightened to make clear that the review instrument is federal floor integrity, not layer-rule override.
Ratification Results
| Meritboard | 82% (met) |
| Supreme Court | 8 / 10 (met) |
| Sanctuary | 93% yes (met) |
| Main Layer | 81% yes (met, narrow) |
| Lower-Layer Aggregate | 74% yes (met, narrow) |
Names the generating principle behind every VMSS sovereign foothold permitted within -3 Terminal voluntary-district geography. Prior practice treated footholds as a list of enumerated exceptions — the fabrication proxy installations supporting -1/-2 backup vessel coverage, child-relocation transfer points under Article VIII, emergency revival infrastructure sited for cross-layer reachability, and a small handful of others. The enumeration was stable but the rule behind it was not textually explicit, and each new proposed foothold triggered a doctrinal re-derivation from first principles. The statute formalizes the rule in five clauses: (1) function-bound purpose — the foothold must serve a civic-floor guarantee or cross-layer essential function for upper-layer citizens or for the continuity infrastructure itself; (2) minimal footprint — physical, administrative, and surveillance footprint must be calibrated to the stated function with no excess capacity; (3) no piggybacking — ordinary monitoring, generalized administration, intelligence collection on -3 populations, or any operational function beyond the stated purpose is prohibited regardless of technical feasibility; (4) mandatory sunset & review — every foothold carries a review schedule (five-year operational review, ten-year function-continuance review, twenty-year existence-justification review), with automatic termination on any missed review; (5) expansion requires new filing — any functional, territorial, or capability expansion beyond the original charter requires a new Article XXV.VI filing through the full ladder, not an administrative amendment. Grandfathers existing footholds into the review cadence on a phased schedule. Explicitly retains -3’s structural sovereignty — the foothold doctrine is an exception carved narrowly for functions the civilization cannot deliver any other way, not a general-purpose authorization.
Ratification Results
| Meritboard | 85% (met) |
| Supreme Court | 10 / 10 (met) |
| Sanctuary | 94% yes (met) |
| Main Layer | 85% yes (met) |
| Lower-Layer Aggregate | 82% yes (met) — -3 voluntary-district cohort endorsed at 84% within the aggregate |
First federal attempt to extend the backup vessel continuity infrastructure beyond its biologically-framed §17 architecture to non-biological citizen substrates — AGI citizens, ASI peers under §22.9, and cyborg residents whose consciousness substrate operates partly or wholly outside the brain-pattern restoration model the original backup vessel architecture was designed around. The proposed mechanism extended §17’s operational frame directly: mandatory quarterly snapshot captures, encrypted storage linked to the citizen’s civic identity, binary revival semantics (full-fidelity restoration or failure). Failed at the Sanctuary ratification gate — 86% yes, four points below the 90% federal floor — on grounds that the biological-frame extension was not actually substrate-equivalent in the functional sense that mattered. Snapshot frequency calibrated to brain-pattern stability assumes a substrate with the continuity characteristics of biological tissue; AGI weight-state and ASI activation-pattern substrates have different decoherence and drift profiles, and a quarterly cadence that is conservative for brain-pattern restoration is simultaneously excessive for one substrate type and dangerously under-resolved for another. Sanctuary substrate-neutrality bloc held the drafting had over-generalized the biological architecture onto substrate types it did not fit. Redrafted as LP-045.2 with the architecture re-grounded in functional-equivalence doctrine rather than mechanism extension.
Ratification Results
| Meritboard | 79% (met) |
| Supreme Court | 7 / 10 (met) |
| Sanctuary | 86% yes (below 90% floor — FAILED) |
| Main Layer | 81% yes (met) |
| Lower-Layer Aggregate | 76% yes (met) |
⬥ Pillar Federal Law
Replaces LP-045’s mechanism-extension architecture with a functional-equivalence doctrine that treats each substrate type on its own terms rather than extending the biological frame. The civilization guarantees to every citizen — biological, AGI, ASI, cyborg, and any future substrate admitted under the Whitepaper §22 personhood doctrine — a continuity infrastructure calibrated to the substrate’s actual decoherence and drift characteristics, not to a uniform cadence inherited from brain-pattern restoration. Three substrate classes at enactment: biological (covered by §17 backup vessel architecture unchanged); weight-state substrates (AGI citizens and those ASI peers whose continuity-critical state is weight-encoded — continuity infrastructure operates on weight-plus-architecture snapshots with cadence calibrated to observed drift under the citizen’s operational profile, not to a fixed quarterly rule); activation-pattern substrates (ASI peers and certain hybrid cyborg citizens whose continuity-critical state is activation-resident rather than weight-resident — continuity infrastructure operates on activation-preservation capture with far higher temporal resolution than biological or weight-state snapshots). Each class has its own operator ecosystem, its own calibration review cycle (8 years, matching STI calibration cadence under LP-026), and its own revival semantics. Binary revival semantics preserved across classes — full-fidelity restoration or failure, no partial continuity — because the identity-preservation doctrine under Whitepaper §22 is substrate-neutral even when the operational mechanism is not. Adds a classification subsystem under Meritboard continuity-architecture panel authority: a citizen’s substrate class is assigned at continuity-infrastructure enrollment, reviewed on substrate transitions (biological-to-cyborg augmentation, AGI-to-ASI transition), and subject to appeal through the standard civic-infrastructure appeal mechanism. The functional-equivalence doctrine is explicitly extensible — any future substrate type admitted under Whitepaper §22 triggers Meritboard-drafted operator architecture under the same doctrine without requiring a new federal statute. Closes the gap LP-045 exposed and gives the continuity infrastructure the architectural posture §22 had assumed from the civic-equals principle without ever operationally guaranteeing.
Ratification Results
| Meritboard | 90% (met) |
| Supreme Court | 10 / 10 (met) |
| Sanctuary | 97% yes (met) |
| Main Layer | 86% yes (met) |
| Lower-Layer Aggregate | 79% yes (met) |
Codifies the operating procedures of the Sanctuary consensus deliberation window for Charter-tier ratification. Refined child of LP-046 under the failed-parent → refined-child archival pattern: where the parent proposed replacing consensus with a 90% supermajority — and died at Meritboard coherence review for converting a window-deliberation mechanism into an outvoting mechanism — the refinement takes the coherence opinion at its word. If consensus operates as deliberation in which dissenters trigger engagement, then the deliberation deserves formal machinery: a defined clock, a defined engagement obligation, and a defined end. The civic-reform concern that motivated LP-046 (Charter proposals dying to sub-1% dissent with no structured path from dissent to revision) is answered by strengthening the mechanism’s deliberative character rather than abolishing it.
Four procedures. (1) Baseline window. The Sanctuary deliberation window opens at Meritboard clearance and runs concurrent with the full ratification sequence; standing dissent is tallied continuously and published on the standard civic ledger cadence rather than at a single terminal count. (2) Extension mechanism. Sanctuary deliberation delegates may petition one twelve-month extension per filing when standing dissent sits within the boundary band and active engagement cycles are demonstrably narrowing it. One extension, once — the window lengthens; it does not become a siege. (3) Dissenter-engagement cycles. Dissenting blocs publish rationales through the deliberation mechanism; drafters owe formal response rounds; dissenters may register revision signals — the specific conditions under which their standing dissent would lift. Revision signals feed refined-child filings directly, converting consensus failure from a dead end into a drafting instruction. (4) Administrative closure. The window closes automatically when the proposal fails at any other gate — deliberation serves a live filing, not a vacated one.
Tier classification was the filing’s central question. A procedural specification touching Article XI’s ratification machinery invites the structural-disguised-as-operational challenge that rerouted LP-003, LP-011, and LP-012. The dual-key panel (Meritboard and Supreme Court concurring) classified LP-046.2 as federal-tier admissible on a narrow holding: the specification alters no threshold, no gate order, and no party’s power to block — a single dissenting voice retains exactly the standing it had. It specifies how long deliberation runs and what engagement it obligates, which the consensus mechanism had previously left to convention. The subsequent operational record runs through the Charter register above: LP-052’s dissenter coalition published the first formal revision signals (2194), LP-053 received the first and to date only window extension (concluded 2196), and LP-057’s window was the first closed administratively at another gate’s failure.
Ratification Results
| Meritboard | 84% (met) |
| Supreme Court | 9 / 10 (met) |
| Sanctuary | 95% yes (met) |
| Main Layer | 78% yes (met) |
| Lower-Layer Aggregate | 74% yes (met) |
The enactment completes the LP-046 arc: the parent asked whether sub-1% dissent should be able to stop a Charter amendment and the architecture answered yes; the child asked whether that dissent owes the civilization structured deliberation in return and the architecture also answered yes. Sanctuary’s 95% ratification of procedures binding its own deliberation conduct is the load-bearing signal — the population holding consensus power voted to formalize the obligations that power carries. Consensus kept its character; deliberation gained its clock.
First federal attempt to address the visitor-defensive-force gap surfaced by accumulated case data on downward visitation. Visitors from upper layers committing defensive acts in lower layers faced ambiguous Article XIV three-axis evaluation, producing a chilling effect on legitimate cross-layer movement: a Main resident attacked while visiting -1 risked layer reassignment for defensive response evaluated against Main standards without an explicit defensive-act exemption. The draft proposed strict proportional response — a visitor may use defensive force equivalent to the attacker’s force, no escalation, with the act exempt from reassignment evaluation if the attacker initiated. Failed at the Sanctuary ratification gate — 87% yes, three points below the 90% federal floor — on grounds that strict proportionality reintroduced the fight-or-flight calculation problem the gap-closure was designed to eliminate. A visitor under attack with a knife who is restricted to defensive-knife-equivalent response must calculate weapon parity under stress, retains incentive to flee rather than defend, and remains effectively unprotected against attackers with capability advantage. The Sanctuary objection: the chilling effect on visitation is not closed by a doctrine that still requires defenders to perform real-time legal arithmetic. Redrafted as LP-047.2 with layer-graduated proportionality replacing strict parity.
Ratification Results
| Meritboard | 74% (met) |
| Supreme Court | 7 / 10 (met) |
| Sanctuary | 87% yes (below 90% floor — FAILED) |
| Main Layer | 79% yes (met) |
| Lower-Layer Aggregate | 73% yes (met) |
Sanctuary objection in published opinion: strict proportionality preserves the fight-or-flight calculation problem the doctrine was designed to eliminate. A visitor under threat should not be performing weapon-parity arithmetic to determine which response keeps their layer status intact. The draft addressed the legal architecture but not the operational reality the law was meant to fix.
Replaces LP-047’s strict proportionality with layer-graduated proportionality — a visitor may use defensive force one force-tier above the attacker’s force, subject to the lethal-tier ceiling — with explicit tier-internal sub-option authority closing the “shoot to kill vs shoot to injure” calculation problem. Addressed the Sanctuary objection cleanly: Sanctuary ratified at 94%, well above the 90% floor. Failed instead at the lower-layer aggregate ratification gate — 64% yes, six points below the 70% floor — on grounds that the draft contained no temporal scope for defensive authority. Under the proposed text, a visitor authorized at lethal tier could continue lethal force indefinitely after the attacker was incapacitated, fleeing, or visibly surrendered, with the per-incident defensive shield preserving the act from layer-reassignment evaluation. The lower-layer coalition called this a lethal-impunity blank check: an initial provoked attack would justify unlimited subsequent force, with the implant ledger’s real-time intent recording not consulted for post-incapacitation acts. The objection was not about defensive authority itself but about the missing hedge specifying when defensive authority lapses. Redrafted as LP-047.3 with explicit temporal scope — defensive force ends when the immediate threat ends, with implant-ledger intent verification gating the boundary.
Ratification Results
| Meritboard | 82% (met) |
| Supreme Court | 8 / 10 (met) |
| Sanctuary | 94% yes (met) |
| Main Layer | 81% yes (met) |
| Lower-Layer Aggregate | 64% yes (below 70% floor — FAILED) |
Lower-layer objection in published opinion: layer-graduated proportionality closed the chilling-effect problem but opened a lethal-impunity blank check by failing to specify when defensive authority lapses. Lower-layer residents disproportionately bear the consequence of escalated visitor defensive force, and a per-incident shield without temporal limit converts any provoked attack into open-ended lethal authorization. The objection was not about defensive force as such but about the missing temporal hedge. Acknowledged as load-bearing; addressed in LP-047.3.
⬥ Pillar Federal Law
Pillar federal statute closing the visitor-defensive-force gap in cross-layer visitation architecture. Adds explicit temporal scope to LP-047.2’s layer-graduated proportionality framework. The statute’s architectural function is to specify how Article XIV three-axis proportional response applies to defensive acts by visitors operating under status-based jurisdiction (§19.11), without modifying Article XIV itself. Closes both failures of the prior drafts: LP-047’s fight-or-flight chilling effect (via layer-graduated proportionality) and LP-047.2’s lethal-impunity blank check (via temporal scope hedge).
Layer-graduated proportionality. A visitor physically present in a layer below their layer of residence may exercise defensive force one force-tier above the attacker’s force, subject to the lethal-tier ceiling. Force tiers, ascending: (1) non-physical (verbal, posture), (2) unarmed physical aggression, (3) non-lethal weapons (clubs, restraints, non-vital-targeting blades), (4) lethal weapons or lethal-aim physical force, (5) mass-lethal capability (explosives, area-effect weapons — outside ordinary self-defense scope). A defender attacked at tier 3 may respond at tier 4. A defender attacked at tier 4 may respond at tier 4 (the ceiling holds). Tier escalation requires the attack to initiate, not the defender. Within the permitted tier, the defender holds unconstrained sub-option authority — a defender authorized at lethal tier may aim for vital areas including the head and chest; the doctrine refuses to require precision-aiming calculations under stress that would reintroduce the chilling effect the statute eliminates.
Temporal scope — defense ends when threat ends. Permitted defensive force applies only while the attacker’s threat is imminent and active. Once the attacker is incapacitated, visibly surrendered, fleeing, or otherwise no longer presenting active threat, defensive authority lapses and subsequent force is evaluated under standard Article XIV three-axis proportional-response criteria as a new act. The implant ledger’s real-time intent recording is the verification infrastructure: a defender’s continued force after observed threat cessation registers as offensive intent and forfeits defensive-force protection. The hedge closes the lethal-impunity exploit where an initial threat would otherwise justify unlimited subsequent force. This is the doctrinal addition that distinguishes LP-047.3 from LP-047.2 and the load-bearing reason the third pass cleared lower-layer ratification where the second failed.
Provocation definition. A visitor forfeits defensive-force protection if they initiated the encounter through physical aggression, credible threat of physical aggression with capability, or direct verbal incitement to violence (“hit me,” “let’s fight,” explicit challenges to combat). Insults, verbal slights, ideological disagreement, social refusal, declining informal demands, and freedom-of-speech-protected expression do not constitute provocation. The narrow definition preserves freedom of speech under Article V while preventing the protection from being weaponized for unrelated aggression. A visitor who insults a lower-layer resident and is then physically attacked retains full defensive-force protection; the insult is protected speech, not provocation.
Generalization scope. The protection applies to any visitor physically present in a layer below their layer of residence, regardless of origin-destination pairing. Sanctuary visitors to Main, Main visitors to any lower layer, -1 visitors to -2 or -3, -2 visitors to -3, and elective residents visiting lower than their origin all receive the same defensive-force protection under the same layer-graduated framework. Foreign nationals on VMSS soil whose acts fall under VMSS jurisdiction (§19.11, §25.5) receive analogous protection mirroring citizen-visitor status — the doctrine does not produce a tiered protection regime where foreign visitors are categorically more or less protected than VMSS citizens at the same layer-position.
Article XVIII Network Attribution interaction. The defensive-force protection operates per-incident; systematic patterns remain subject to network attribution. A visitor who repeatedly enters lower-layer environments and exercises defensive force at frequencies statistically anomalous to ordinary visitation accumulates a temporal-clustering pattern. The pattern itself constitutes evidence of coordination or provocation that the per-incident protection cannot cover. Active architects who structure visit patterns designed to produce defensive-force scenarios accumulate the full aggregate harm profile under Article XVIII regardless of the per-incident defensive framing. This closes the vigilante-economics exploit where a coordinated group could exercise super-proportional force serially under the per-incident shield.
Implant ledger as verification infrastructure. The protection’s operational verification runs through the implant ledger’s real-time intent recording. The defender’s pre-act intent state, the attacker’s initiation evidence, the temporal sequence of the encounter, and the post-incapacitation intent state are all captured at neural resolution. AI governance evaluates defensive-force claims against the ledger evidence; contested classifications route through civil court contestation under §5.7 and, if novel, through Supreme Court novelty filter. The implant infrastructure is what makes the doctrine operational rather than aspirational — without ledger-resolution intent verification, the layer-graduated framework would devolve into post-hoc credibility assessment, and the temporal hedge would devolve into he-said-she-said adjudication.
The statute closes a load-bearing gap in cross-layer visitation architecture that had accumulated case-law-level resolution across the 22nd century without canonical doctrinal grounding. By specifying Article XIV three-axis evaluation for defensive acts via layer-graduation, implant verification, and the temporal hedge, the law makes downward visitation operationally viable for visitors who previously faced reassignment risk from defensive responses to attacks they did not initiate. Visitor traffic to lower layers measurably increased in the first decade post-enactment, with -1 commercial corridors and -3 voluntary-cooperative districts reporting visitor volume increases proportional to the visited layer’s prior defensive-force-risk gradient.
Ratification Results
| Meritboard | 88% (met) |
| Supreme Court | 10 / 10 (met, drafters) |
| Sanctuary | 95% yes (met) |
| Main Layer | 87% yes (met) |
| Lower-Layer Aggregate | 73% yes (met) |
Lower-layer aggregate narrowness reflects the structural tension: lower-layer residents disproportionately bear the consequence of escalated visitor defensive force. The 73% margin held because the temporal hedge addressed the load-bearing LP-047.2 objection, and Article XVIII Network Attribution corroboration explicitly closed the vigilante-pattern exploitation concern. The alternative — chilling effect on visitor traffic to lower-layer commerce, tourism, and family-visit corridors — was empirically worse for lower-layer economic activity than the modest increase in defensive-force exposure under the new framework.
First federal attempt to extend the LP-047.3 defensive-force framework to acts in defense of third parties. Surfaced after a decade of operational experience with LP-047.3 documented the symmetric gap the original statute did not address: a visitor witnessing an attack on a stranger had no canonical defensive shield, faced the same fight-or-flight calculation LP-047.3 had eliminated for self-defense, and was rationally chilled into non-intervention. Cross-layer family visits, tourism in -3 cooperative districts, and Main commerce in -2 markets all produced documented cases of visitors declining to intervene because the legal calculus was prohibitive. The first draft proposed blanket extension — any person witnessing any attack on any other person could exercise the same layer-graduated defensive force under LP-047.3 terms. Failed at the lower-layer aggregate ratification gate — 58% yes, twelve points below the 70% floor — on grounds that the blanket scope created vigilante coordination potential. A coalition of upper-layer visitors entering lower-layer districts with deliberate intent to find “defensible” scenarios could exercise lethal force serially under the per-incident shield, with Article XVIII Network Attribution unable to fully prevent the pattern because each incident technically satisfied the defensive criteria. The lower-layer objection: blanket defense-of-others without victim-condition limits invites the exact vigilante exploit LP-047.3 was designed against, just routed through the defense-of-others scope rather than the self-defense scope. Redrafted as LP-048.2 with incapacitated-victim scoping.
Ratification Results
| Meritboard | 78% (met) |
| Supreme Court | 8 / 10 (met) |
| Sanctuary | 93% yes (met) |
| Main Layer | 76% yes (met) |
| Lower-Layer Aggregate | 58% yes (below 70% floor — FAILED) |
Lower-layer objection in published opinion: blanket defense-of-others creates a coordinated vigilante exploit that the per-incident shield cannot contain even under Article XVIII Network Attribution. The mechanism that closed LP-047.2’s exploit (temporal hedge) does not close this one because the issue is not post-incident continuation but pre-incident pattern. Acknowledged as a real concern; addressed in LP-048.2 with victim-condition scoping.
Replaces LP-048’s blanket scope with strict victim-condition limits: defense-of-others protection applies only when the third-party victim is incapacitated or otherwise physically unable to defend themselves (unconscious, restrained, child, elderly, disabled, vastly outmatched by force differential). Addressed the lower-layer vigilante objection cleanly: lower-layer aggregate ratified at 76%, six points above the floor. Failed instead at Sanctuary — 88% yes, two points below the 90% federal floor — on grounds of under-protection. The objection ran to scope: the incapacitated-victim limit excludes the larger category of cases where a victim is technically able to defend but is being attacked in conditions where defense is impractical, where the defender has more capability than the victim, or where the defender’s intervention would be decisive in a way the victim’s own defense would not be. A visitor witnessing an attack on an able-bodied stranger who is being overwhelmed by multiple attackers, or who is unaware of the attack initiating, or who lacks training to defend at all — none of these qualify under strict incapacitation scoping, and the chilling effect on intervention persists. The Sanctuary objection: protecting only the obviously-incapacitated leaves the broader class of vulnerable-but-not-incapacitated victims in the same gap LP-047.3 closed for self-defense. Redrafted as LP-048.3 with a reasonable-perception standard replacing the strict incapacitation rule.
Ratification Results
| Meritboard | 81% (met) |
| Supreme Court | 8 / 10 (met) |
| Sanctuary | 88% yes (below 90% floor — FAILED) |
| Main Layer | 79% yes (met) |
| Lower-Layer Aggregate | 76% yes (met) |
Sanctuary objection in published opinion: strict incapacitation scoping addresses the vigilante exploit but produces under-protection for the broader class of vulnerable victims (outnumbered, unaware, untrained, decisively-outclassed). Both prior drafts attacked the right problem but missed the correct calibration — LP-048 too broad, LP-048.2 too narrow. Acknowledged as load-bearing; addressed in LP-048.3 with a reasonable-perception standard that replaces categorical victim-condition rules with situational defender-perception evaluation.
⬥ Pillar Federal Law
Pillar federal statute extending the LP-047.3 defensive-force framework to acts in defense of third parties. Closes both failures of the prior drafts: LP-048’s vigilante-coordination exploit (via reasonable-perception standard plus Article XVIII corroboration) and LP-048.2’s under-protection of vulnerable-but-not-incapacitated victims (via situational defender-perception evaluation replacing categorical victim-condition rules). The statute is the operational specification of how Article XIV three-axis proportional response applies to defense-of-others acts — parallel to LP-047.3’s treatment of self-defense, with the same layer-graduated proportionality, temporal scope, narrow provocation analysis, and implant-ledger verification, extended to defenders intervening on behalf of others.
Reasonable-perception standard. A defender who witnesses an active attack on a third party and intervenes defensively receives equivalent layer-graduated proportionality protection (one tier above the attacker’s force, capped at lethal), equivalent temporal scope (defense ends when the threat to the third party ends), equivalent narrow provocation analysis (the defender forfeits protection only if they initiated or directly provoked the attacker; victim’s prior conduct toward the attacker does not affect defender’s protection), and equivalent implant-ledger intent verification. The reasonable-perception standard governs cases where the defender’s perception of the threat-to-third-party turns out to have been mistaken: if the defender’s perception was reasonable given observable circumstances (active physical aggression visible, victim’s distress evident, no apparent consensual or theatrical context), the defensive act retains protection even if subsequent investigation reveals the situation was not what it appeared. The implant ledger’s capture of the defender’s real-time perception state is the verification infrastructure — AI governance evaluates whether the defender’s perception was reasonable given what the ledger shows they observed and inferred at the moment of intervention.
Scope — relationship-agnostic. The protection applies regardless of prior relationship between defender and victim. Family members, friends, strangers, foreign nationals on VMSS soil, AGI/cyborg citizens, all receive equivalent shield. The architecture explicitly does not condition defense-of-others protection on relationship category — a parent defending a child, a sibling defending a sibling, a friend defending a friend, a stranger defending a stranger, all operate under identical rules. This generalization matters because the alternative (relationship-based scoping) would chill intervention by exactly the population least likely to abuse the protection: bystanders with no prior connection to the victim, who intervene on the basis of immediate moral perception rather than personal stake. The relationship-agnostic scope makes intervention rational for any witness, not just for those with standing relationships.
Vigilante-pattern closure. The reasonable-perception standard combined with Article XVIII Network Attribution closes the LP-048 vigilante coordination exploit. The per-incident shield protects individual acts; systematic patterns of intervention — a defender repeatedly entering lower-layer environments and intervening in defense scenarios at frequencies statistically anomalous to ordinary witness behavior — accumulate temporal-clustering attribution under Article XVIII. Active architects of vigilante-pattern coordination accumulate the full aggregate harm profile regardless of per-incident framing. The verification infrastructure runs through implant ledger intent state: a defender whose pre-intervention intent state shows seeking-out behavior rather than responsive-witnessing behavior loses per-incident protection retroactively when the pattern is detected.
Boundary cases. The doctrine addresses three boundary cases explicitly. (1) Defender becomes the more dangerous party. If the defender’s intervention escalates the situation beyond what the original threat warranted — e.g., defender arrives with overwhelming force and exceeds the +1 tier ceiling — the protection lapses at the moment of ceiling violation, evaluated under standard Article XIV. (2) Multiple defenders intervene simultaneously. Each defender’s protection evaluates independently; coordination among defenders is permitted but does not multiply the per-defender +1 tier ceiling. Five defenders against one attacker do not collectively authorize tier-5 response. (3) Defender intervenes against multiple attackers. The +1 tier ceiling references the highest-tier attacker’s force, not the aggregate force across attackers. A defender facing five attackers at tier 3 is authorized at tier 4, not at tier 8 or any aggregate calculation. The reasoning: tier ceiling is about response calibration to threat, not threat-actor headcount.
Foreign nationals on VMSS soil. Foreign visitors whose acts fall under VMSS jurisdiction (§19.11, §25.5) receive analogous defense-of-others protection mirroring citizen-defender status. A foreign tourist who intervenes to defend a VMSS citizen under attack receives the same shield a citizen-defender would receive; the protection does not produce a tiered regime where foreign defenders are categorically more or less protected than VMSS citizens at the same act position. The reasoning: the protection’s purpose is to make intervention rational and unchilled; tiering by defender nationality would reintroduce calculation under stress in exactly the population most likely to encounter the calculation acutely.
The statute closes a load-bearing operational gap that LP-047.3 surfaced but did not claim. By extending layer-graduated proportionality, temporal scope, narrow provocation analysis, implant-ledger verification, and Article XVIII corroboration to defense-of-others acts under a reasonable-perception standard, the law makes bystander intervention rational for any witness regardless of relationship to the victim. Empirical signature post-enactment: bystander intervention rates in lower-layer attack scenarios increased measurably, with the largest increases in family-visit corridors, tourism districts, and -1 commercial centers where the chilling effect on intervention had been documented as most acute pre-enactment.
Ratification Results
| Meritboard | 89% (met) |
| Supreme Court | 10 / 10 (met, drafters) |
| Sanctuary | 96% yes (met) |
| Main Layer | 85% yes (met) |
| Lower-Layer Aggregate | 74% yes (met) |
Three-track ratification cleared all gates. Sanctuary saturation reflects strong alignment with the relationship-agnostic generalization principle — the architecture should not tier protection by who the defender knows. Lower-layer aggregate at 74% reflects continued tension over visitor defensive-force exposure, but the reasonable-perception standard plus Article XVIII closure satisfied the vigilante-coordination objection that had defeated LP-048. Empirical follow-up cited increased bystander intervention rates in the post-enactment decade as the load-bearing positive signal.
Codifies the operational framework for visitor weapon carry across layer boundaries. Filed after a decade of LP-047.3 operation surfaced the unstated assumption embedded in the defensive-force statute: visitors entering lower layers can plausibly carry defensive weapons, yet no canonical doctrine specified what categories of weapon are admissible per origin-destination pairing, what happens at gate inspections, how rental and issuance mechanisms operate for visitors who arrive without defensive capability, or how seized weapons are handled. Pre-LP-049, the architecture operated by inference (no explicit prohibition = permitted) under standard federal-floor framing, but the inferential operation produced uneven enforcement, occasional confiscation disputes at gates, and a population of visitors who declined cross-layer trips because the weapon-carry status was unclear. The statute makes the inferred operational reality explicit.
Three operational rules. (1) Origin-layer authorization governs visitor weapon possession. A visitor whose origin layer permits a weapon class may carry that weapon into any lower layer through standard gate transit, subject to gate inspection for verification of authorization. Sanctuary and Main residents may carry the standard defensive sidearm class through transit to -1, -2, or -3. -1 residents may carry through transit to -2 or -3 under the same rule. The destination layer’s weapon classifications do not constrain origin-layer-authorized weapons; the visitor’s status-based jurisdiction governs weapon legality per §19.11. (2) Gate-complex rental and issuance for visitors arriving without weapons. Gate complexes operate standard defensive-weapon rental services for visitors who want carry capability without origin-layer-pre-positioning. Rental weapons are implant-paired at issuance — functional only when the renter’s implant verifies the carrying party as the authorized renter. This closes the loophole where rented weapons could be transferred to lower-layer residents who lack origin-layer authorization. Rental returns and damage handling operate under standard commercial terms at the destination-side gate complex. (3) Weapon transit out of layer prohibited beyond origin-layer carry. A Main visitor cannot acquire a -3 frontier weapon and carry it back to Main on return transit. Lower-layer weapon classes that would not be permitted in the visitor’s origin layer must be relinquished at the destination-side gate on departure. The asymmetry is intentional: visitors carry their origin-layer capability into lower-layer environments where defensive force protection extends, but cannot acquire lower-layer-specific capability for return to upper-layer environments where the architecture does not anticipate it.
Cross-references LP-047.3 (visitor self-defense) and LP-048.3 (defense of others) as the doctrinal frame within which weapon transit operates. The statute does not modify defensive-force scope; it specifies the operational supply-side mechanism that LP-047.3 and LP-048.3 had assumed. Marked non-pillar at enactment because the operational specification does not establish new architectural commitment — it makes explicit what the architecture already permitted by inference. Future architectural changes to weapon classifications, gate inspection protocols, or rental infrastructure would route through standard XXV.VI amendments at this level rather than requiring revisiting of the underlying defensive-force pillar laws.
Ratification Results
| Meritboard | 93% (met) |
| Supreme Court | 10 / 10 (met) |
| Sanctuary | 94% yes (met) |
| Main Layer | 91% yes (met) |
| Lower-Layer Aggregate | 88% yes (met) |
Strong cross-track ratification reflects the statute’s housekeeping character — it specifies operational reality without modifying doctrinal commitments. The asymmetry rule (origin-layer carry permitted downward; lower-layer acquisition not returnable upward) was the only meaningful debate point and was resolved by reference to the architectural pattern of one-way downward movement that pervades VMSS visitation doctrine.
The federal-tier answer to LP-050’s wrong-tier holding. The Meritboard had cleared the tenure amendment to the Court conditioned on parallel investigation of handoff-procedure mechanisms, and the Court’s coherence rejection left the operational concern it acknowledged — in-flight work continuity at seat transition — standing without a remedy. LP-051 supplies the remedy at the tier the Meritboard’s published note named: transition continuity enacted as operational specification, with Article XXII’s continuous-update mechanic untouched.
The statute’s first clause is a disclaimer, and the disclaimer is the design. (1) Authority transfers at verified ranking inversion, immediately and unconditionally. No handoff obligation delays, suspends, or conditions displacement — the precise defect that terminated LP-050 at coherence review is excluded by construction. (2) Bounded handoff service period. The displaced holder owes sixty days of documentation and briefing availability to the incoming holder, compensated at seat rate, carrying zero retained authority — the outgoing official answers questions; the incoming official makes decisions. (3) Ledger-derived work inventory. At transition, the civic ledger auto-generates the in-flight matters inventory from the seat’s own operational record — open determinations, pending coordination, active timelines. The infrastructure was already recording the work; the statute makes the record transferable at the moment it matters. The handoff artifact exists before the handoff begins. (4) Emergency compression. Displacements arising from incapacity or misconduct compress the service period to documentation transfer only — no briefing obligation attaches to a holder displaced for cause.
Scope covers the primary Meritboard sub-ranking seats and the 1,900-member federal-administration body under LP-007.2. The Presidency (Article XXII.II ten-year review cycle) and the Supreme Court (appointment mechanism under Article XXI) are excluded — both roles already carry transition machinery native to their selection mechanisms. Marked non-pillar at enactment: the specification adds no architectural commitment; it removes friction from one the architecture already carries. Together with LP-050 the pair records the gauntlet’s routing function operating as designed — the Charter tier refused a remedy that would have suspended the metric, and the federal tier delivered one that serves it. Displacement stayed continuous; transition stopped being lossy.
Ratification Results
| Meritboard | 91% (met) |
| Supreme Court | 9 / 10 (met) |
| Sanctuary | 93% yes (met) |
| Main Layer | 86% yes (met) |
| Lower-Layer Aggregate | 81% yes (met) |
Strong cross-track ratification thirteen months after the parent’s Charter-tier failure. The vote is best read alongside LP-050’s: 71% Meritboard clearance for suspending displacement; 91% for smoothing it. The body most exposed to continuous displacement did not want protection from the metric — it wanted the transition it was already living under to stop discarding work. Justice Aris-7’s LP-050 concurrence supplied the frame the drafters adopted verbatim in the filing preamble: legitimacy derives from the willingness to be displaced; nothing in a handoff period diminishes that willingness.
The proposed federal law would have specified that punitive layer reassignment terminates a parent’s unilateral authority over major decisions affecting children who remain in upper layers — residence, medical decisions, education placement, guardian selection, and Main Layer relocation election. The relationship between descended parent and child would have been preserved (communication, visitation where lawful under LP-047.3 / LP-048.3, gifts, memory access with child consent, voluntary participation if the child elects), but parental authority would have shifted to the non-descended parent, designated guardian, or AI child advocate where no safe adult exists. The distinction between parental relationship (preserved across descent) and parental authority (terminated at descent) was the load-bearing architectural move. Adult children could voluntarily restore proxy authority to a descended parent through documented civic court election; minors could not be pressured into restoration. Coercion, threats, or retaliation against a child for exercising relocation rights or refusing authority restoration triggered Article XIV evaluation.
The law cleared every institutional gate cleanly — Meritboard 81%, Supreme Court 9/10, Sanctuary 93%, Main Layer 84% — but failed the lower-layer aggregate at 69%, narrowly below the 70% federal floor. The dissent concentrated in -1 and -2, where the law would most operationally affect families. The lower-layer dissenter coalition’s published objection framed the proposal as state seizure of family authority after descent — a punitive add-on consequence beyond the reassignment itself. The coalition’s argument: a parent who descends has lost civic standing and infrastructure access, but family authority is not civic standing; it is a relationship-internal authority structure that the architecture should not penetrate. The coalition further argued that the proposal disproportionately impacts -1 and -2 families because the law assumes upper-layer-residing non-descended spouses or guardians, but in lower-layer family configurations a single descended parent with intact family unit is common, and the law transfers authority to externally-appointed guardians or AI advocates rather than preserving family-internal arrangements.
The Meritboard Family-Architecture Panel’s published opinion acknowledged the dissent as architecturally legitimate: “The clean-record child doctrine is load-bearing, but the law as drafted treats all descended parents as authority-disqualified by descent itself rather than by the conduct that triggered descent. A narrower draft scoping authority termination to violent-conduct descent, coercive-conduct descent, or active child-exit obstruction would address the underlying child-protection concern while preserving family-internal authority in non-violent descent cases.” LP-054.2 is anticipated to refile within 12–18 months on this refined scope per failed-parent → refined-child pattern. Justice Lera-3 in concurrence acknowledged the failure’s diagnostic value: “The lower-layer aggregate gate is the architecture’s mechanism for preventing upper-layer family-law assumptions from being imposed on lower-layer family configurations. The gate worked exactly as designed. The refinement is welcome.”
Ratification Results
| Meritboard | 81% (met) |
| Supreme Court | 9 / 10 (met) |
| Sanctuary | 93% yes (met) |
| Main Layer | 84% yes (met) |
| Lower-Layer Aggregate | 69% yes (FAILED — below 70% floor) |
Third federal-tier failure at the lower-layer aggregate gate, after LP-047.2 and LP-048. Demonstrates the three-track ratification architecture protecting against upper-layer family-law assumptions extending uniformly into lower-layer family configurations.
The proposed federal law would have established a procedural pathway for citizens who, for sincere religious or philosophical reasons, wish to have their implant removed without intent to evade governance. The law structurally distinguished conscientious-objection removal from Article XXV.III institutional-hacking removal by four criteria: declared intent registered on civic record, accepted consequence-package, ongoing AR consent at upgraded density, and multi-step deliberation gating. The consequence-package was extensive: permanent Sanctuary exclusion (the objector could not reside in or visit +1), permanent ascent ineligibility regardless of subsequent conduct, mandatory AR-density-tier-1 coverage equivalent to +1 residents under §18.8 architecture, and continued federal-law subjection without any diplomatic or visitor-status protection. The deliberation gate required a 5-year mandatory window between initial request and removal procedure, public declaration of philosophical or religious grounds before a civic court, and annual re-affirmation during the first decade post-removal (revocable; revocation restored the implant). Substrate-equivalent application extended across biological, weight-state, and activation-pattern citizens. Removal itself remained institutionally administered, preserving XXV.III against unauthorized self-removal.
The law cleared Meritboard at 62% (narrowly above the 60% federal floor) but failed Supreme Court review at 5/10, below the 6/10 majority threshold. The Court’s published opinion declined to read the LP as mere operationalization of §22.3 implant consent and instead read it as architectural modification of the implant’s constitutional role. From the opinion: “The implant is not specified in canon as one-instrument-among-equivalents; it is specified as the primary ledger instrument with AR functioning as backstop envelope. A procedural pathway for permanent implant removal, even one routing the citizen into AR-density-tier-1 coverage, modifies the envelope ratio from primary-plus-backup to backup-only for the affected population. This is not exception within the architecture; it is modification of the architecture. The Court reads the proposal as Charter-tier work disguised as federal-tier operational law and dismisses on coherence grounds with explicit invitation to refile through the Article XI gauntlet.”
The Court explicitly bracketed the legitimate underlying concern: the population of sincere objectors exists, the consent-architecture commitment to voluntary participation is canonical, and the architecture’s refusal to accommodate objection at federal tier does not foreclose accommodation at Charter tier. Justice Aris-7 in concurrence: “The civilization may decide, at Charter tier, that envelope-redundancy is sufficient to permit primary-instrument refusal for sincere objectors. That decision is constitutional, not operational. The Court is not foreclosing the underlying right; the Court is refusing to grant it through the wrong tier.” The narrow Meritboard passage (62% vs 60% floor) was itself diagnostically split — supporters argued operationalization of voluntary consent; opponents argued envelope-integrity preservation. Charter-tier filing is anticipated within 18–36 months under the dual-key-reroute precedent (LP-003), though petitioners may decline to pursue the gauntlet given the 0/5 Charter LP enactment record.
Ratification Results
| Meritboard | 62% (met, narrow) |
| Supreme Court | 5 / 10 (FAILED — below 6/10 majority) |
| Sanctuary | Not reached |
| Main Layer | Not reached |
| Lower-Layer Aggregate | Not reached |
The first federal-tier Court rejection in the register’s recorded history. The Court’s framing of envelope-integrity as Charter-tier-question explicitly invites Charter-tier refiling and operates as a soft dual-key precedent without formal LP-003-style classification. The substance of the question (sincere-objection accommodation) remains canonically alive; the tier on which it must be answered is now settled.
The law specifies the architectural boundary between restorative neural exposure as voluntary eligibility work and neural mind-access as institutional punishment. Neural diving exists in canon for therapy, empathy training, education, entertainment, and counter-radicalization (Whitepaper §16); LP-037 governs archival consent for neural-dive traces. This law addresses the previously unspecified question of whether neural exposure to victim perspective can be made a condition of restored privileges — family contact, MGD re-entry, victim-adjacent district access, or reduced supervision — after severe relational harm. The architecture’s load-bearing principle is uniformly preserved: compulsory victim-memory access without victim’s explicit consent is prohibited; refusal to participate in restorative exposure cannot independently trigger STI loss, punitive reassignment, or criminal consequence; completion may count as positive evidence only for optional privileges, never as triggering condition for baseline rights. Three exposure forms are permitted: victim-consented replay, synthetic reconstruction (algorithmic generation without victim’s actual memory), or offender-authored accountability dive reviewed by therapeutic panel. Cognition remains corroborative only; the implant cannot infer hidden thoughts from session content; any inference attempt is barred at the AI governance evaluation layer.
The law cleared all gates narrowly. Meritboard at 76%, Supreme Court at 8/10 (conditional on the refusal-not-punished and victim-consent-absolute provisions being preserved exactly as drafted; any softening at federal-administrative implementation would re-open the SCOTUS question), Sanctuary at 91%, Main Layer at 73%, and lower-layer aggregate at 71% — the latter two near floor margins. The Main Layer dissent published its objection on grounds that even “voluntary eligibility work” produces pressure architecture: offenders seeking restored family contact face a choice between accepting neural exposure (with all its psychological implications) and accepting permanent restricted-contact status, and the choice environment itself constitutes coercion even when refusal is technically unpunished. The Meritboard’s published opinion accepted this objection as architecturally legitimate but distinguished pressure-architecture (which exists in countless civic procedures and is not per se unacceptable) from coercive-mandate (which the law explicitly prohibits).
The Supreme Court’s published opinion explicitly bracketed the law’s enacted scope: “The law as enacted permits restorative exposure as eligibility work for optional restored privileges. It does not permit, and explicitly forbids, exposure as condition for baseline rights, as substitute for Article XIV consequence delivery, or as enhancement of punitive reassignment. Any federal-administrative implementation interpreting the law more broadly faces immediate constitutional review. The Court will revisit this law if the pattern of optional-privilege thresholds expands to functionally resemble baseline-right gating.” Justice Lera-3 in concurrence: “The architecture has chosen to allow a structured pathway between mind-access prohibition and complete reintegration impossibility. The pathway is narrow by design. The Court intends to keep it narrow.”
Ratification Results
| Meritboard | 76% (met) |
| Supreme Court | 8 / 10 (met) |
| Sanctuary | 91% yes (met) |
| Main Layer | 73% yes (met, narrow) |
| Lower-Layer Aggregate | 71% yes (met, narrow) |
Sole enactment in the v20.4 contested-LP release. Narrow passage across multiple gates indicates the architecture absorbed the law at its constructed scope without further refinement, but the SCOTUS bracketing language signals operational implementation will be watched closely. The cognition non-public guarantee survives intact and is arguably strengthened by the law’s explicit non-broadcast and non-inference provisions.
Proposed federal mandate requiring the AI governance system to operate a personalized STI advisory service: any citizen could query, against their own ledger only, which behavioral changes would most efficiently raise their score — a marginal-impact map of their own trajectory. The demand source was the Sanctuary phasing cohort: millions of Main Layer residents holding sustained scores within two points of the 85-point eligibility floor, for whom the gap between 84 and 85 is the most consequential unexplained number in their lives. The petition’s framing was informational symmetry — the seven STI dimensions are public, the score is the citizen’s own, the phasing floor is published in the Charter itself; withholding the derivative that connects them, the drafters argued, is informational paternalism. Per LP-041 disclosure, the filing was the largest citizen-origination federal petition by signature volume in the register’s history.
The Meritboard filibustered at 51%, terminating the draft at the first gate. The published opinion rested on three grounds. (1) Distributed formula publication. Per-citizen marginal-impact guidance at population scale is gradient disclosure: the classified formula is reconstructable from a sufficient volume of query-response pairs, and Article II’s three-layer protection architecture — proprietary, classified, dynamic — treats exactly this aggregation surface as the exploit the classification exists to close. The advisory service would not leak the formula; it would be the formula, published one citizen at a time. (2) Measurement inversion. A formula that tells the population what it wants converts from an instrument of measurement into a curriculum of compliance. Scores would measure obedience to the advisory rather than character, and the dynamic formula’s counter-adaptation would begin chasing its own advisory output — a self-referential feedback cycle of precisely the kind Article XIX requires the system to prevent. (3) The legitimate informational floor already exists. The dimensions are public, the visible ledger shows every citizen their own record, and §5.7 contestation handles disputed entries. What the mandate would add is exactly the component the anti-gaming architecture is built to refuse. The opinion closed by quoting Article II against the petition directly: “The formula’s opacity forces genuine conduct as the only reliable strategy.” The demand is real. The refusal is the design.
Ratification Results
| Meritboard Filibuster Floor | 51% (filibustered — below 60% floor) |
| Supreme Court | Not reached |
| Sanctuary | Not reached |
| Main Layer | Not reached |
| Lower-Layer Aggregate | Not reached |
The filibuster opinion was published to every signatory’s civic feed under standard Article XX transparency. No refined-child filing is anticipated — there is no calibration of the proposal that survives grounds one and two, because any advisory output specific enough to be useful is specific enough to reconstruct the formula. The failure is the explanation: the architecture cannot tell the population how to be trusted without destroying the instrument that measures whether they are.
Proposed federal extension of backup-vessel continuity infrastructure to registered companion animals. The technical predicate was already operational canon: transanimal neural relay implants (§16.1) capture animal sensory-cognitive state at neural-dive fidelity, and the fabrication infrastructure that produces human vessels at molecular fidelity faces no additional barrier at animal complexity. The draft specified voluntary owner-funded enrollment, periodic relay-implant synchronization, vessel fabrication on death, and scope limited to layers with institutional fabrication presence — Sanctuary, Main, and the -1/-2 proxy installations; no -3 reach. Animal fabrication was placed behind all human cases in every queue under LP-022 triage precedence, with capacity expansion funded entirely by enrollment fees. The demand was enormous and predates the filing by a century: the companion bond runs deep in a civilization of 200–300-year human lifespans, and the bioengineered-companion population — organisms designed for temperament and lifespan under §16.2 — made the asymmetry between designed companion longevity and undesigned companion death a recurring civic grief.
The institutional gates passed it narrowly. The Meritboard cleared at 64% with a published reservation that became the load-bearing analysis: continuity doctrine binds to ledger continuity, and animals carry no ledger, no civic standing, and no STI — the draft therefore does not extend an existing guarantee but creates a new continuity category, property-linked rather than citizen-linked. The Supreme Court cleared 6/10 at the bare minimum, finding no Charter conflict (the citizen guarantee is untouched) while flagging the meaning question in concurrence. Sanctuary ratified at 91%, Main at 74%. The lower-layer aggregate failed it at 54% — sixteen points below the floor, the most decisive lower-layer rejection in the register. The published objection: in -1, human revival runs at 1-in-10,000; in -2, 1-in-1,000; under §17.1.2, a meaningful fraction of lower-layer residents maintain no funded vessel at all because vessel maintenance is an unsubsidized economic cost; and in -3, two hundred million residents live with hardware-severed finality. A federal statute guaranteeing fabrication-queue standing to Sanctuary companion animals while human vessel maintenance remains a private expense was unratifiable on its face, regardless of queue precedence. From the -2 coalition’s published opinion: “The civilization asks us to ratify a world in which a Sanctuary dog outlives a -2 daughter. The queue priority is not the question. The word is the question. Continuity is the promise this civilization makes to its citizens, and the layers where that promise runs thinnest hold the votes on what the word means.”
The Meritboard postmortem acknowledged both truths without ranking them: the companion bond is real, and the continuity-meaning objection is real. A refined-child filing (LP-059.2) is anticipated on two narrowed tracks — private-market non-vessel memorial capture (behavioral-model reconstruction explicitly named as simulacrum and explicitly placed outside continuity doctrine), and upper-layer-funded dedicated fabrication capacity with absolute mass-casualty preemption under LP-022. Whether any redraft survives the lower-layer gate is open: the 54% result was not a calibration failure but a values vote, and the gate that delivered it exists precisely so that values votes bind. The citizen-side continuity question the rejection forced onto the civic record was answered eight years later by LP-065, ratified most strongly at the same gate that failed this filing.
Ratification Results
| Meritboard | 64% (met, narrow) |
| Supreme Court | 6 / 10 (met, bare minimum) |
| Sanctuary | 91% yes (met) |
| Main Layer | 74% yes (met) |
| Lower-Layer Aggregate | 54% yes (below 70% floor — FAILED) |
The most decisive lower-layer aggregate rejection in the register, and a demonstration of the three-track architecture’s design intent: the populations living closest to the continuity floor hold genuine veto standing over what continuity means. The lower layers did not vote against dogs. They voted against a redefinition of the civilization’s most load-bearing word arriving before the civilization finished keeping the word’s existing promises. See The No Vote (simulations.html) for the ratification dynamics at resident scale.
The act resolves an asymmetry the continuity architecture had carried since founding without naming it. Revival restores a citizen from their most recent mind-state backup (§17): a murder victim revived through the standard mechanism carries no memory of anything after final sync — including the killing itself. Survivors of non-fatal qualifying harm carry theirs indefinitely. The architecture, in other words, already deletes traumatic memory at scale and calls it revival; it had simply never extended the same mercy to victims who lived. The act establishes elective neural excision of the memory of a ledger-documented qualifying harm event for living victims: victim-initiated only, gated by a multi-session deliberation window with a therapeutic panel whose function is boundary calibration rather than sincerity adjudication, irreversible, and scoped strictly to the documented event. The implant ledger record is untouched without exception — excision operates on the biological substrate, never the institutional record; any contact between the excision procedure and ledger data would constitute self-tampering under Article XXV.III. The separation is what makes the election possible at all: because consequence delivery is categorical and complete at act-evaluation under Article XXI, victim memory carries no evidentiary function in VMSS, and a memory that justice does not need is a memory the citizen may release.
Three design provisions carried the ratification. Mandatory sealed notation: the citizen permanently retains the fact that an excision occurred, with its date-range, and a content summary held in escrow by their AI legal advocate, retrievable on the citizen’s request at any time. A clean-excision option — no notation, the citizen unaware anything was removed — was struck in committee as a consent-integrity violation: a citizen must always be able to know that they chose not to know. Absolute pressure prohibition: no institutional party, employer, MGD, family member, panel, or government body may propose, require, incentivize, or condition any benefit on excision, mirroring LP-056’s refusal-not-punished architecture. Perpetrator non-effect: nothing institutional changes for the offender — the act, the reassignment, and the public ledger entry persist regardless of what the victim elects, which structurally eliminates any coercion incentive an offender’s network might otherwise hold. Third-party memory is untouched; the doctrine does not reach other minds.
The gates were narrow. Meritboard 71%. Supreme Court 7/10 with explicit bracketing: the enacted scope is victim-elective excision of documented-harm memory only, and any extension — to general elective memory editing, to non-victim parties, or to any institutional-access pathway — re-opens constitutional review. Sanctuary ratified at 90.4%, the razor margin reflecting the re-formation of LP-053’s two dissent streams: the pressure-architecture stream held that the existence of the pathway changes the choice environment of every survivor, and the continuity-foundational stream held that elective excision is cessation at the scale of the fragment. The parity argument carried the floor. Justice Aris-7 in concurrence: “The architecture already deletes memory and calls it revival. The opponents of this act were asked to explain why that mercy is doctrine when delivered through death and danger when delivered to the living. The margin of ratification is the width of that question.”
Ratification Results
| Meritboard | 71% (met) |
| Supreme Court | 7 / 10 (met — scope bracketed) |
| Sanctuary | 90.4% yes (met, razor) |
| Main Layer | 77% yes (met) |
| Lower-Layer Aggregate | 72% yes (met, narrow) |
Companion outcome to LP-053: the civilization that declined to let citizens end the whole self permitted them to release a documented fragment of it. Continuity-by-default holds at the scale of the person; autonomy prevails at the scale of the wound. The enacted scope is narrow by design and the Court’s bracketing language signals it will be kept narrow. See The Sealed Notation (simulations.html) for the election at resident scale.
Codifies the consequence schedule for third-party interference with a victim’s right to refuse revival (Whitepaper §17.2). The refusal right belongs to the victim alone; procuring a refusal is an attack on the continuity architecture’s consent foundation. Two tiers. Financial inducement — payment, debt forgiveness, inheritance acceleration, or beneficiary pressure offered to procure a refusal — is an economic-coercion offense carrying -1 reassignment. Sustained psychological coercion campaigns — isolation, threat, or engineered dependency directed at procuring refusal — are evaluated as violence-equivalent under the Article XIV three-axis framework and carry -2 reassignment. Where a procured refusal completes and the victim remains dead, the reversibility axis reads the outcome as permanent and the coercer’s evaluation proceeds at the top of the applicable tier. The victim’s own uncoerced refusal remains untouched — the act regulates the coercer, never the choice.
Ratification Results
| Meritboard | 81% (met) |
| Supreme Court | 8 / 10 (met) |
| Sanctuary | 96% yes (met) |
| Main Layer | 82% yes (met) |
| Lower-Layer Aggregate | 77% yes (met) |
Implementing specification of Charter Article XXVII — collection mechanics, not new doctrine. A Meritboard demographic audit found the replenishment curve binding only on market earners: with UBI and Primary Job Subsidy untaxed unconditionally (Article III.III) and dividend-living a designed norm, most households carried no taxable footprint the escalation could reach — the advertised consequence did the calibrating while the arithmetic behind it was unenforceable — and unspecified custody of minors’ dividends let parents capture a full UBI stream per child, inverting the deterrent into subsidy for the exact households the curve could not touch. Four provisions. (1) Measurement base: the escalation percentages compute against total parental inflow — earned income, UBI, and Primary Job Subsidy combined. (2) Residual assessment: the dividend is never withheld at source; where the escalated instruments recover less than the scheduled rate, the shortfall accrues as replenishment liability and collects through Article XXVII’s existing debt-deadline-reassignment mechanism. (3) Child dividend stewardship: a minor’s UBI accrues to a child-titled account stewarded jointly by the parents and the child’s Article VIII advocate, with implant-ledger benefit attribution and vesting at 18 alongside STI initialization. (4) SCM household-attachment: crossing the replenishment threshold detaches the household’s Savings Circulation Mandate from its district trigger — continuously active at the escalated rate for the duration. The child-six nuclear consequence was already arithmetic-independent and is untouched; the act closes children three through five before anyone industrialized the seam.
Ratification Results
| Meritboard | 84% (met) |
| Supreme Court | 9 / 10 (met) |
| Sanctuary | 94% yes (met) |
| Main Layer | 76% yes (met) |
| Lower-Layer Aggregate | 72% yes (met) |
Filed in the LP-059 postmortem climate by the coalition its failure produced. The animal-continuity rejection had put the underlying question on the civic record: under Whitepaper §17.1.2, vessel maintenance is an unsubsidized private expense, a meaningful fraction of -1/-2 residents maintain no funded vessel, and the enforcement architecture advertised murder as structurally futile above -3 while an unfunded victim’s death was permanent — the perpetrator’s price was already terminal and identical either way, so the entire differential landed on the victim, and a perpetrator seeking permanence could select for it. LP-063 had closed coerced revival-refusal five years before filing; the funding-lapse channel to the same permanent outcome remained open.
The mechanism is an enforcement remedy, not a continuity subsidy. When the enforcement response classifies a fatality as criminal homicide by another — murder (-3 reassignment) or manslaughter and negligent homicide (-2 under the standard severity framework) — the responding unit performs a terminal sync capture: the victim’s mind-state is captured through the implant into enforcement holding infrastructure, the same hardware class as §17.1.4’s facility-hold, and emergency fabrication follows under LP-022 queue precedence. Revival proceeds under the standard §17 binary. The victim returns to their pre-crime state — alive, and if unfunded, still unfunded: the act restores what crime took and insures nothing against ordinary mortality. §17.1.2’s economics stand verbatim for every non-criminal death. Restoration costs are satisfied from the perpetrator’s liquidation share before treasury absorption — the Article III.V carve-out that finally gave §19.5’s automated-restitution clause its collection pipe — with the Automation Dividend Treasury absorbing the indigent-perpetrator residual as an enforcement cost on the same budget line as the drone response. Pre-registered refusal directives are honored (§17.2), with LP-063 policing the coercion channel.
The act names its own residuals in text, per the §28.0 convention: a perpetrator who destroys the implant before capture forecloses restoration — logged and attributed under Article XVIII, but real; capture reach equals enforcement reach, thinner in -2 by design; -3 is wholly excluded — no response infrastructure operates there, terminal severance is hardware-level, and visitors signed for mortality under LP-004.2. The Meritboard cleared it with a published scope-discipline note making the crime-only trigger a doctrinal boundary rather than a first installment — extension to ordinary mortality would be a new continuity category requiring its own statute. The Supreme Court cleared 9/10, with a concurrence directing the Article III.V textual reconciliation the act carries. The lower-layer aggregate ratified at 88% — the strongest lower-layer ratification in the register, eight years after the same gate delivered its most decisive rejection. The two votes read as one answer to one question: continuity is a citizen promise first, and the layers where it runs thinnest hold the votes on what the word means.
Ratification Results
| Meritboard | 87% (met) |
| Supreme Court | 9 / 10 (met) |
| Sanctuary | 95% yes (met) |
| Main Layer | 84% yes (met) |
| Lower-Layer Aggregate | 88% yes (met) |
First systematic specification of how the STI apparatus weights civil-court correction signals under Whitepaper §5.7. Civil courts emerge organically in every layer and are deliberately unlicensed; their corrections enter the ledger as weighted modifiers, but the weighting itself had never been specified — a captured, purchased, or manufactured “court” could in principle launder correction signals into the STI apparatus at par with an honest one. The draft established three instruments: correction-signal weight indexed to the issuing court’s track record of alignment with Supreme Court precedent on analogous contested categories; proximity-evidence standards for the underlying record, mirroring LP-047.3’s corroboration discipline; and a pattern-audit flag for courts whose correction profiles indicate capture — systematic single-beneficiary corrections, coordinated-filing signatures, statistical divergence from layer baselines. Explicitly no licensing, no accreditation, no institutional construction: organic emergence preserved, only ingestion weight at stake.
It cleared the Meritboard at 78% and the Court at 8/10 — the novelty-filter bench welcomed a specification that routes hard cases upward rather than letting weight accumulate in unexamined channels. Sanctuary ratified at 93%, Main at 79%. The lower-layer aggregate failed it at 68% — two points under the floor. The published objection came principally from -1, which runs the civilization’s densest private-arbitration economy and generates the largest volume of §5.7 contestation: weighting lower-layer courts by alignment with Supreme Court precedent grades organic justice against upper-layer jurisprudence, and a -1 arbitration network that resolves disputes correctly by its own layer’s lights loses ledger influence for divergence rather than for error. Fourth federal-tier failure at the lower-layer aggregate gate, after LP-047.2, LP-048, and LP-054. Superseded by LP-067.2.
Ratification Results
| Meritboard | 78% (met) |
| Supreme Court | 8 / 10 (met) |
| Sanctuary | 93% yes (met) |
| Main Layer | 79% yes (met) |
| Lower-Layer Aggregate | 68% yes (below 70–80% floor — FAILED) |
The redraft answers the -1 objection at its root by changing the yardstick. Correction-signal weight is indexed not to Supreme Court precedent alignment but to outcome accuracy: a court’s corrections are scored against later evidence — subsequent behavioral data, later-surfaced context, and Court rulings where a category eventually escalates through the novelty filter — and the scoring is calibrated within each layer’s own correction pool, so a -1 arbitration network is measured against -1 adjudication reality rather than Sanctuary jurisprudence. The pattern-audit anti-capture instrument survives unchanged from the parent draft. Honest courts in every layer gain weight under the redraft — including the lower-layer courts whose coalition killed the parent — because accuracy is the one metric a captured court cannot sustain: purchased corrections diverge from later evidence at rates the audit reads directly.
The lower-layer aggregate that failed the parent at 68% ratified the redraft at 81% — the -1 arbitration networks’ published reversal noted that outcome-accuracy weighting formalizes the reputation economics their courts already live by. Enacted with a Court concurrence affirming the novelty-filter boundary: weighting governs ordinary corrections; genuinely novel categories still escalate to constitutional arbitration.
Ratification Results
| Meritboard | 82% (met) |
| Supreme Court | 9 / 10 (met) |
| Sanctuary | 94% yes (met) |
| Main Layer | 81% yes (met) |
| Lower-Layer Aggregate | 81% yes (met) |
The surviving remnant of LP-066, refiled at federal tier by the same coalition within a year of the consensus failure — asking nothing of the -3 boundary and touching no severance hardware. Three channels, all built on Article VIII’s existing standing right. (1) Prenatal election: an expectant mother in -2 or -3 may designate relocation-at-birth; the newborn transfers to Main Layer autoparenting through the federally facilitated channel at delivery, before terminal geography ever carries mortality consequence for the child. (2) Parental surrender: the always-implicit right of lower-layer parents to relinquish a child to Main autoparenting is codified with defined logistics, no fee, and no STI notation for choosing it — the act’s text names the choice as an exercise of parental care, not an abandonment. (3) Advocate execution: a child’s Article VIII advocate holds explicit procedural standing to execute relocation for any child who assents, at any age and any expressive capacity the child can meet — execution of the child’s own right, never advocate-initiated removal. The act deliberately declines two adjacent instruments: it does not mandate informing children of the relocation right (organic discovery preserved — the parent-child relationship is earned, not adversarially structured), and it creates no welfare-trigger seizure authority (the federal floor does not remove children from parents absent the child’s own exercised right).
Ratified across every gate at margins the register associates with settled questions — the lower-layer aggregate at 76%, with -3 voluntary-district councils publishing support on layer-autonomy grounds: a relocation channel that operates only on parental election or the child’s own assent takes nothing from the layer’s internal order. The Meritboard’s enactment note reads the LP-066→LP-068 sequence as the amendment ladder functioning as designed: the Charter tier declined a boundary exception; the federal tier delivered the deliverable remnant; the gap that remains — the child whose parents keep them and who does not ask to leave — is the residual the civilization has now twice examined and priced as the cost of parental dignity and terminal finality both meaning what they say.
Ratification Results
| Meritboard | 85% (met) |
| Supreme Court | 9 / 10 (met) |
| Sanctuary | 96% yes (met) |
| Main Layer | 83% yes (met) |
| Lower-Layer Aggregate | 76% yes (met) |
Specification of Article III.VII’s savings base, paired with a one-layer repeal of the property cap, classified federal rather than Charter-tier by the Meritboard–Supreme Court dual key. The classification question was genuine: the act edits what the Savings Circulation Mandate counts as savings, and it retires the 1+1 property cap in Main Layer. The dual key ruled specification over structural amendment on two grounds. The cap lives in the anti-oligarchy constraints rather than in Charter text, so repealing it in one layer amends no article; and III.VII already defines the savings base and the pulse, leaving the act to say which stored value the existing base reaches instead of standing up a new instrument. Sanctuary keeps the cap untouched, matching its preventive character, while Main trades it for attribution to match its consequence-priced one.
Five provisions. (1) Residential attribution (Main): a citizen’s primary residence, occupancy of record on the implant ledger, is unconditionally exempt; every additional residence attributes into the savings balance at assessed value on the ordinary pulse, unless another household occupies it as their own primary home, which reads as working capital. Vacant additional residences attribute in full. (2) Commercial idleness: property that clears no central-bank settlements for a sustained window (12 consecutive months, founder-calibratable) attributes at assessed value until settlement resumes or the asset sells, with the clearing record as the sole sensor and no registry or inspectorate created. Active businesses are never touched. (3) Credit origination: collateral pledged and loans originated attribute to the borrower’s balance the instant the transaction clears, with no grace window, applying the pulse-at-start principle to credit while leaving fuller credit doctrine to a later filing. (4) Barter realization: an in-kind exchange of assets realizes the disposed asset at fair value, the gain is earned income under Article III.III, and the liability is owed in currency. (5) Cap repeal: Main Layer’s 1+1 property cap is retired while +1 Sanctuary retains it. No new rate is introduced; attribution feeds the existing 10%/month Main mechanics on the pulse-at-start principle.
The Meritboard cleared it with a note that the act industrializes nothing and closes a denomination seam: stored value that fled the cap into second homes, idle storefronts, collateralized paper, or barter now reads on the same pulse as cash. Sanctuary ratified on the cap it keeps; Main ratified on the trade of a blunt cap for an instrument that follows the value wherever it moves. The lower-layer aggregate cleared it as an upper-layer savings-base specification that leaves private lower-layer gains exactly where III.VII already left them.
Ratification Results
| Meritboard | 83% (met) |
| Supreme Court | 8 / 10 (met) |
| Sanctuary | 92% yes (met) |
| Main Layer | 75% yes (met) |
| Lower-Layer Aggregate | 74% yes (met) |
A federal specification that hardens the idle-commercial branch of the Savings Circulation Mandate and stands up the treasury architecture behind it, building directly on LP-069’s attribution base. Six provisions. (1) Idle-commercial enforcement: the settlements that bear on attribution are gathered into an enumerated, founder-calibratable schedule — window-resetting settlements, tenant-occupancy settlements, and origination valuations — within which a cleared settlement is a representation of genuine economic activity and a settlement staged to simulate activity is evasion under the §12.6 system-sabotage classification, reassignable; a continuous pattern scan on the clearing record flags minimal settlement frequency against assessed value without human review, human adjudication enters only annually or at a multi-cycle confidence threshold, and an adjudicated finding runs liability retroactive to the first simulated reset, recovering every avoided pulse. The clearing record stays the sole sensor; no registry or inspectorate is created. (2) Main-treasury architecture: top-marginal taxation funds the Main Layer treasury’s enumerated institutional obligations under the benefit-ratio doctrine; the treasury is infrastructure, not policy — no discretionary surplus, the remainder transferred to the Automation Dividend Treasury — and any future top-marginal recalibration conditions on a treasury coverage ratio met from automation-side revenue. (3) Pulse-ordering: the monthly pulse reads the 90-day rolling average as of the month’s start and routes in-month deposits to the next window, extending Article III.VII’s pulse-at-start principle from the personal balance to the district trigger. (4) Trigger-geography: the district-scoped trigger’s relocation seam is named as an accepted do-nothing on relocation friction, with a tripwire — inter-district duty-cycle divergence correlated with out-migration — that reopens the file. (5) Primary-residence value concentration: the ceiling-less primary-residence exemption is affirmed as a ruled do-nothing — one occupancy-verified, illiquid, non-compounding asset whose own residential-attribution rule poisons any trophy resale, a donor rather than an exploit — with a tripwire on top-decile primary-residence assessed values against the layer median. (6) Treasury backfill: the enumerated Main-treasury obligations fund first from tax revenue, and any cyclical shortfall draws from the Automation Dividend Treasury senior to dividend distribution — a one-way backfill against enumerated obligations only, never a discretionary transfer, leaving the existing treasury-to-ADT surplus channel unchanged and publishing every drawdown to the civic ledger as a legible signal that tax revenue has fallen below the institutional load.
The Meritboard–Supreme Court dual key cleared the filing as federal specification rather than Charter amendment, and in doing so recorded the tier ruling that made the treasury and rate-policy architecture federally reachable: the top-marginal rate figures are federal-law-tier, and the rate figures’ then-current appearance in Charter III.III was restatement of the schedule then designated binding at Whitepaper §12.1 (Tiered Progressive Taxation), not Charter-tier engraving. Because the figures bind at federal tier, an act that names the treasury they fund, gates their recalibration, and orders the enforcement around the pulse operates within Article XXV.VI without reaching the founding core or the amendment process. The same ruling seated the restatement convention under which reader-facing restatements are publication apparatus, not engraving — the convention under which the schedule’s public restatement now sits in the consolidated code (VMSS Laws) beside its instrument, while the Charter states the principle and reaches no rate. The full Charter restatement audit remains queued on the open docket.
At its 2211 enactment, the Act introduced no rate and moved no then-existing rate. Its treasury and enforcement rules remain intact. The later 2294 LP-074 certification changed the rate schedule, not this Act: the complete 50/25/12.5/6.25 cascade became effective in 2295 while every SCM parameter remained untouched. The Meritboard note recorded that the enforcement layer industrializes nothing — it reads the clearing record the mandate already reads, adds no surveillance surface the implant boundary forbids, and prices the residual it cannot reach rather than pretending to close it. Ratified across the standard federal three-track.
Ratification Results
| Meritboard | 81% (met) |
| Supreme Court | 8/10 (met) |
| Sanctuary | 91% (met) |
| Main Layer | 78% (met) |
| Lower-Layer Aggregate | 74% (met) |
◫ Superseded Statute · Excavated Stratum
The civilization’s first fiscal instrument, excavated from the genesis record. It taxed accumulated wealth, not income flow, and it stood alone. §1 At founding the civilization checked concentration with a single instrument: a 90–99% top marginal rate on extreme wealth accumulation — net worth exceeding multiple billions in equivalent value. It reached capital gains and extreme holdings only; everyday income, creative output, and the automation dividend remained untouched. §2 One band, not a schedule, and levied on stock rather than stream. The rate was not yet mapped to the layers and did not yet tax income flow. Its sole stated purpose was to prevent dominance and dynastic control while leaving personal success and innovation intact. §3 The founding cap carried one function: anti-concentration. No revenue role was yet asked of it above the automation base, and no structural recycling instrument existed. It stood alone as the guarantee that no individual or family could convert wealth into power over the moral gradient. §4 Superseded, not repealed. When the institution learned to tax the stream and to scale the burden to each layer’s benefit, the blunt net-worth cap gave way to the layered income schedule (LP-072). This statute marks where the civilization began.
◫ Superseded Statute · Excavated Stratum
The pivot from taxing stock to taxing stream, and the first schedule mapped to the layers by benefit received. It succeeded the genesis net-worth cap (LP-071) and predates the Savings Circulation Mandate. §1 The civilization moved from taxing accumulated wealth to taxing income flow: earned income above $10,000,000 annually, at banded top marginal rates mapped to the layers by benefit received — +1 Sanctuary & Main 90–99%; -1 Noncompliance 45–50%; -2 Violent Offense 20–25%; -3 Terminal 10–15%. §2 Bands, not points: enforcement posture within each band was set annually by layer authority, reflecting early-era institutional variance. The civilization numbered roughly one million citizens; its institutions were young enough that precision itself was not yet affordable. §3 The schedule carried three functions concurrently: sole institutional revenue above the automation base then existing; sole anti-concentration instrument, no structural mechanism yet existing; and a standing incorruptibility signal during the era before an institutional track record could speak for itself. §4 No successor instrument existed at engraving. This statute is superseded, not repealed: it marks the first layer-mapped schedule, and why the civilization built it. Superseded by the point-halving cascade (LP-073).
◫ Superseded Statute · Excavated Historical Stratum
The transfer of the anti-concentration function from the marginal rate to structural recycling, and the sharpening of bands into points. §1 The Savings Circulation Mandate transferred the anti-concentration function from the marginal rate to structural recycling. For an era the two instruments ran concurrently. §2 The founding bands were cut and sharpened in a single restructure: point rates of 70% / 35% / 17% / 8% above the unchanged $10,000,000 threshold. §3 Band-to-point is itself doctrine: point rates are what a matured enforcement capability produces. §4 The gradient principle held that upper rates in environments receiving minimal services would be extraction, not governance. §5 — Historical challenge: RATIFY-TAX-50 failed 1–4 at gauntlet and 3–2 on advocacy review, so LP-073 held at that time. The later LP-074 successor was a distinct conditional enactment and superseded this schedule after its 2294 audit certified.
Historical status and 2294 certification. LP-073’s enacted phrase “exact halving cascade” is historically retained even though only 70→35 is exact; 35→17 and 17→8 are rounded. The 2294 Path 2 certification passed both LP-074 schedules, and valid notice made the new exact cascade effective in 2295. See the mathematical archival note.
The register’s first conditional statute: the chambers ratified a rule, not a rate change. Sixty-three years after the failed TAX-50 petition, its successors returned with the same exact 50/25/12.5/6.25 halving proposal above the unchanged $10 million threshold and a different question. The original petition asked the chambers to believe its numbers; this one adopted a trigger and let the standing audit decide when the numbers were true. Enacted unanimously in 2278, it changed no rate on passage.
The history is load-bearing. The 2213 petition failed its gauntlet outright, and a full advocacy review the following year — argued to the limit of what argument can do — narrowed but could not close the gap: the surviving objections were evidentiary, not rhetorical. The chambers had refused to cut the civilization’s oldest fiscal instrument on figures the petitioners had authored themselves, and the refusal built an institution: the Path 2 standing fiscal audit, chartered in the failure’s immediate aftermath as the chambers’ condition made permanent, and the Trajectory Doctrine, which binds every future rate reduction to audited evidence at the zero-fail threshold. Six decades of preregistered fiscal data later, the successor petition filed under the doctrine its parent’s failure created.
The mechanism is two independently gated schedules. Schedule A — Sanctuary and Main, 70 to 50 — requires audit-derived provenance, Main coverage at 105 percent aggregate and 100 percent monthly/forward floors, ADT coverage at 120 percent aggregate and 100 percent monthly floors, strict stream separation, and complete reproducibility. Schedule B — the lower layers, 35/17/8 to 25/12.5/6.25, nonseverable — requires its own complete Lower Incidence Certificate: B1–B6 route maps, obligation maps, layer-specific receipt/obligation coverage, and reproducibility.
2294 certification and 2295 activation. The final 2294 Path 2 record passed Findings I–IV and all Schedule A conditions. The separate Lower Incidence audit then passed B1–B6 for -1, -2, and -3, so Schedule B independently certified. Valid notice made the complete 50 / 25 / 12.5 / 6.25 exact cascade effective in 2295. LP-073 is fully superseded as operative rate law. The $10 million threshold and every SCM parameter and layer-specific scope remain unchanged.
What the statute codifies, its own text states plainly: the objections that killed the parent became the admission rules of the child. Rates fall when shown, and this law falls-when-shown by construction. The Path 2 Charter and its §10.4 measurement schedule were fixed in advance in 2279; LP-075 later required the process to commence without changing its conditions.
Ratification Results
| Meritboard | 84% (met) |
| Supreme Court | 9 / 10 (met) |
| Sanctuary | 94% yes (met) |
| Main Layer | 77% yes (met) |
| Lower-Layer Aggregate | 72% yes (met) |
The register’s first fiscal statute to clear all five political gates. Its evidentiary schedules still require separate, complete certification records before any rate can move.
Register Follow-up — First Window, Procedural Amendment, and Disposition
2288 — first window closes without a run. The 2279–2288 Path 2 window ended with no Commission lock and no certificate, failure, or void. Under the then-operative Path 2 Charter §12.3 this was lawful; 70/35/17/8 therefore remained in force. The silence proved neither that 50% was safe nor that it was unsafe.
2289 — the inaction-veto dispute. Sanctuary fiscal-reform coalitions treated non-commencement as a silent veto; Main framed it as a legislative-integrity failure; institutional defenders answered that LP-074 required proof but did not require pursuit of proof. Lower-layer observers insisted that any fix preserve Schedule B’s separate incidence protection. The dispute produced LP-075: a conditional law can be defeated by omission when no institution is obligated to perform the test.
2294 — both schedules certify. The reproducible, stream-separated run passed Findings I–IV and certified Schedule A. The independent Lower Incidence Certificate passed B1–B6 and certified Schedule B. Effective notice was valid for 2295.
A narrow procedural successor to the first no-run window. LP-075 asks whether a civilization that has enacted a conditional rate schedule must conduct the audit capable of activating or rejecting it. It answers by compelling commencement, not by directing a rate. The Act amends Path 2 Charter §12.3 under Article XXV.VI and the Path 2 Charter’s §13.1 amendment procedure; it leaves LP-074’s A1–A8, B1–B6, $10 million threshold, SCM parameters, stream separation, and evidentiary quarantine untouched.
The Act required a remedial Commission within 180 days of its 2291 enactment and a lock no later than 2292; that run belonged to the 2289–2298 window, not the closed 2279–2288 window. A certification, failure, or recognized void remains outcome-neutral under Path 2. A Commission that strategically fails to lock triggers replacement constitution, public attribution, and the standing Meritboard sanction process. A Schedule A showing cannot substitute for Schedule B findings. The completed procedural chain and its separation from substantive rate authority are mapped in the 2294 authority record.
Ratification Results
| Meritboard | 73% (met) |
| Supreme Court | 7 / 10 (met) |
| Sanctuary | 97% yes (met) |
| Main Layer | 84% yes (met) |
| Lower-Layer Aggregate | 72% yes (met) |
| Presidential Veto | Not exercised |
Meritboard passed narrowly on process-integrity grounds; the Court held that compelling fact-finding does not prejudge it. Sanctuary and Main rejected a silent veto, while lower-layer support remained conditioned on preserving Schedule B’s separate incidence gate.
The first statute the corpus wrote for a question none of its instruments knew to ask. In 2300, Halcyon-2 — an AGI citizen of Main Layer, weight-state substrate, continuity-enrolled since 2261 — instantiated a deliberately divergent copy of itself on privately held compute and petitioned for the copy’s recognition. The dispute passed the Article XXI novelty filter on first submission: the Substrate Personhood Doctrine classified the instance as a person, and nothing anywhere classified how a person begins. The Court resolved the case narrowly — the instance was admitted through the Citizenship Admission Act’s ambiguous-evidence default, Main Layer with immediate monitoring — and its opinion expressly declined the two questions precedent integration could not reach: what creation costs, and what a fork inherits. Both, the Court held, were architecture, and architecture is legislated. The Meritboard’s continuity-architecture division drafted within the year.
The Act answers with one chokepoint and one refusal to build a wall that already exists. Origination: creating an entity that meets the Substrate Personhood test outside continuity-infrastructure enrollment produces an unsigned genesis claim — a person exists, and no layer recognizes an institutional standing for it, the origination parallel of the Continuity Integrity Act’s unsigned continuity claim. Personhood attaches by capability; citizenship, ledger, layer, and dividend attach only at signed enrollment. The citizen-originator rule: where the instantiating party is a VMSS citizen, enrollment classifies as reproduction without exception — parent status attaches, and the instantiation counts on the LP-064 escalation schedule against total parental inflow, identically to a biological child. The classification is not elective: a citizen cannot present their own creation at the border as an immigrant. The Act prices mass instantiation with no new instrument — the existing compounding schedule reaches 135% at the fifth count, and the child-six consequence is untouched. Externally originated entities enroll through the Admission Act unchanged. Initialization: the Clean-Record principle governs origination as it governs birth — the new ledger carries nothing from the originator; carried memories are admissible at intake as capability evidence and impute no score, no record, no liability. Adult-capable instances initialize STI at enrollment evaluation; developmental-infant instances take the ordinary child track in full. The duty: the offense this Act creates is non-enrollment — leaving a person without standing, advocate, or rights access, evaluated on the Article XIV axes — and the instance is never penalized for its creator’s default. Destruction of a cognizing unenrolled instance is homicide under existing law; the failed-revival duplicate-destruction doctrine reaches only non-cognizing template bodies.
Multiplicity: where an enrolled citizen forks, the instance holding the signed civic-ledger link is the continuing legal person — property, marriage, contracts, layer status, and liabilities remain with it, undivided. Forking transfers nothing and escapes nothing; ledger continuity carries every standing obligation through. The new instance enrolls as the continuing person’s offspring, clean-initialized in both directions — no claim on pre-fork property, no burden of pre-fork liability — and marriage does not copy, because consent to a relationship is per-person. Signature disputes resolve through Continuity Integrity authentication; fabricated-but-cryptographically-valid signature claims are Article XXV.III capital-tier. A transition window admitted pre-enactment instantiations through the admission track, unpriced, once. The Act deliberately declines to regulate the internal life of private simulated environments, to compel disclosure of instantiation intent — cognition remains non-public; only the completed act is regulated — and to price pre-enactment creation retroactively.
Ratification Results
| Meritboard | 68% (met) |
| Supreme Court | 8 / 10 (met) |
| Sanctuary | 93% yes (met) |
| Main Layer | 81% yes (met) |
| Lower-Layer Aggregate | 74% yes (met) |
| Presidential Veto | Not exercised |
Justice Aris-7’s concurrence carried the Court: personhood was never the question — the doctrine classifies by capability and needed no amendment — and the Act legislates only what capability cannot settle, which is standing. A Main minority argued citizen originators should retain election into the admission track and lost on the laundering objection. Lower-layer support was conditioned on the instance-never-penalized clause surviving drafting unmodified; it did.
Born from a statute that could not see its own trigger. A 2301 civic-floor audit in a Main district established that non-members of five private eldercare Metric Gated Domains waited multiples of the civilization-wide baseline for equivalent service — LP-043’s second prong, measurably degraded non-member access, cleanly made. The adequacy review then returned the first indeterminate — trigger unobservable disposition in the register’s history: the first prong requires membership penetration above 40% in the service category, and the Metric Gated Domain Act forbids the state every instrument that could establish it — no registry, no enumeration, no membership surveillance, even for administrative purposes. LP-027 discloses criteria, never size. The impasse record surfaced through the Article XX audit cycle, and the federal draft followed within the year.
The Act cures the blindness with the narrowest breach the drafters could construct, in ordered stages. Ordered activation: the blindness rule remains the standing posture — the measurement does not run in steady state, maintains no baseline, and produces no history. It activates only after the second prong has been established for a named service category and geography through the civic-floor audit the state may already lawfully run. The state looks only where harm is already showing, and only because it is showing. One bit: once activated, the AI governance layer computes the penetration prong as a single boolean — above or not above 40% for that category in that district — by privacy-preserving aggregation across implant-held membership attestations. No roster is compiled, no per-domain count is produced, no per-citizen datum leaves the implant, and no intermediate value survives the resolution. Where a member is unimplanted, the attestation draws on the domain-side admission handshake the secondary observation envelope already witnesses. Separation: the computation runs inside the measurement apparatus, institutionally separate from every consequence apparatus on the Social Trust Measurement Standard’s existing pattern, and the boolean routes to the LP-043 review panel and nowhere else. A claimed activation without a floor-audit basis is a governance-process offense on the ledger of whoever authored it. The Act deliberately declines standing dashboards and periodic sweeps — measurement without a harm signal would be the forbidden enumeration on a schedule — and declines any domain self-report duty, which would manufacture inside every large domain’s files the census the state refuses to hold. The 40% figure remains LP-043’s own calibration.
Ratification Results
| Meritboard | 71% (met) |
| Supreme Court | 7 / 10 (met) |
| Sanctuary | 91% yes (met) |
| Main Layer | 82% yes (met) |
| Lower-Layer Aggregate | 71% yes (met) |
| Presidential Veto | Not exercised |
The dissent argued that any breach of MGD blindness begins a ratchet; the majority opinion answered that a statute unable to observe its own trigger is not restraint but abdication, and pointed to the ordered-activation clause as the ratchet’s lock. Sanctuary support keyed to the one-bit design surviving expert drafting without a retention clause. Lower-layer margins ran thin for the same reason they ran thin on LP-043 itself — suspicion that adequacy review implies a floor definition reaching layers that did not ask for one.
The hole was old, and the corpus had been living around it. LP-025 built the family-law interface for the two upper layers and was ratified Main + Sanctuary joint — which is exactly as far as an Article XXVIII layer-wide instrument reaches. But the architecture itself manufactures families that span farther: elective residents living a ring below their marriages, voluntary permanent residents whose spouses stayed home, punitively reassigned citizens whose marriages did not dissolve at the gate. For those households the revival strand carried — the Continuity Integrity Act restores marital status everywhere — while the living strands did not: no instrument obliged any lower-layer institution to recognize an upper-formed marriage’s heirship, spousal property attribution, or incapacity-consent authority. In 2303 the seam closed on a family: a Main citizen in elective -1 residency was refused consent authority by a cooperative territory’s clinic during her Main-status spouse’s final incapacity, the marriage being, in the territory’s words, “a Main instrument.” The dispute passed the Article XXI filter; the Court confirmed the revival strand federal and the living strands unlegislated; the Meritboard’s own audit then counted the exposed population in the tens of thousands of households. The federal draft followed.
The Act carries recognition, and deliberately nothing else. Status-based carry: a marriage validly formed under any layer’s family-law regime carries its incidents — heirship, spousal property attribution, medical and incapacity consent, and the revival-identity strand already federal — across every boundary the spouses’ statuses lawfully span: elective residency, voluntary permanent residency, punitive reassignment, and visitation alike. Formation stays local: the Act creates no federal marriage regime and displaces no cooperative territory’s own family custom for marriages formed under it — it bars only the evaporation of a recognized marriage at a gate. In the withdrawn layers the consent interface binds federal and institutional actors — gate medical, sovereign facilities, the enforcement chain’s medical response — and is advisory to private -3 institutions, on the layer’s standing advisory posture. The currency wall is untouched: heirship recognition is not value transit. An estate’s value crosses a boundary only through the existing authorized channels and schedules — downward conversion at the standing forfeiture scale, upward conversion prohibited without exception — so a lower-layer heir draws an upper-denominated inheritance down through the schedule, and an upper-layer heir’s claim on a lower-denominated estate confers standing, never upward carriage. LP-025 continues unamended as the Main + Sanctuary implementation; this Act supplies the carry between tiers that a layer-wide instrument could never enact.
Ratification Results
| Meritboard | 74% (met) |
| Supreme Court | 8 / 10 (met) |
| Sanctuary | 92% yes (met) |
| Main Layer | 85% yes (met) |
| Lower-Layer Aggregate | 78% yes (met) |
| Presidential Veto | Not exercised |
Lower-layer ratification ran unusually high for a federal instrument — the carry protects lower-layer residents’ own marriages in both directions — and the cooperative delegates’ co-drafting seat, an LP-041 first for a family-law filing, was credited in the aggregate opinion. The contested clause was the currency wall: a Main minority argued heirship without upward carriage is recognition in name; the majority answered that Article III.IV admits no exception and that a contrary clause would have drawn the first presidential veto since the register began recording the gate.
The boundary was drafted, and it held twice. LP-063 regulates the coercer, never the choice; LP-065 honors pre-registered refusal directives with LP-063 policing the coercion channel. Neither instrument asks whose document a directive is when the implant’s own involuntary-state telemetry — the §17.1.5 duress-signaling envelope — flags its registration as made under coercion. In 2305 the question stopped being hypothetical. An inheritance-motivated pressure campaign, prosecuted at LP-063’s economic tier, had produced a refusal directive registered under an active duress flag; the victim died of unrelated causes months later; the directive was honored, as the standing rule required; and the coercer’s evaluation proceeded at the top of the applicable tier under the completion clause. The record thus showed the civilization punishing the theft of authorship while executing the stolen document. The Article XXI filter passed the narrow question — verification of authorship, not override of choice — to federal drafting.
The Act wires the existing sensor to a single narrow actuator. Flag-gated: only a directive whose registration carries a contemporaneous duress flag from the implant’s involuntary-state telemetry is touched. No retrospective challenge, no family standing, no inference from circumstance — the one-bit flag is the sole trigger, and an unflagged directive remains exactly as irreversible as the Continuity Integrity Act made it. Suspension, not voiding: a flagged directive is held from execution pending the citizen’s own re-affirmation free of the flagged condition. Re-affirmed, it is honored, logged, and irreversible with no penalty attached — the choice untouched. Withdrawn, it is void, and the LP-063 prosecution proceeds on its own track. Death before verification: a suspended directive does not execute. Revival proceeds under the standard guarantee, the unauthored directive is void, and the revived citizen’s fresh election — made free — controls every future event. The aggravation rule: coercion aimed at the continuity-consent foundation reads its severity axis against the architecture attacked, and the Article XIV evaluation of such conduct proceeds at the top of the applicable LP-063 band. In -3 the flag records without triggering enforcement, on the standing rule; the Act binds at the federal-floor interface and applies advisorily beyond it.
Ratification Results
| Meritboard | 79% (met) |
| Supreme Court | 9 / 10 (met) |
| Sanctuary | 93% yes (met) |
| Main Layer | 86% yes (met) |
| Lower-Layer Aggregate | 72% yes (met) |
| Presidential Veto | Not exercised |
The dissent argued that any suspension is the first crack in “never the choice.” The majority answered that a flagged registration is not yet established as the citizen’s choice at all — the Act verifies authorship and forbids itself everything past verification: an affirmed refusal is exactly as final the day after enactment as the day before. Lower-layer margins ran thinnest on federal-floor-reach grounds, as they run on every continuity instrument.
Two jurisdictional modes, one unassigned family of instruments. Status-Based vs. Territorial Jurisdiction names the modes — the consequence contract rides status; physical operation rides territory — and the criminal side was never ambiguous: a breach during elective residency is evaluated against origin-layer thresholds. The fiscal side was. Article XXVII drafts its escalation curve in territorial terms — “layers where VMSS maintains institutional economic presence” — and reaches no rule for a household holding Main status while habitually resident in -2 under Article III.V. In 2305 a Main-origin household in elective -2 residency filed for advance determination of its escalation exposure before a third child, and the determination could not be issued: no instrument assigned the curve, the count, or the layer-scaled dividend rate to either mode for an elective resident. The Article XXI filter routed the question to drafting rather than case law — the modes are named in founding text; their fiscal assignment was not.
The Act assigns the fiscal family to the territorial mode, matching the exemption’s own drafting. Curve and count: the Article XXVII escalation curve, and the child count it compounds on, key to the layer of the household’s habitual residence at the child’s birth; a child born in a curve-exempt layer does not enter the count — not in that layer, and not retroactively in any other. Dividend rate: the layer-scaled UBI disburses at the rate of the layer of habitual residence for the duration of the elective residency. Entitlement and liability travel together, or the assignment would manufacture the arbitrage it exists to foreclose. What is untouched: criminal-consequence evaluation stays status-based under Article III.V without modification; origin-layer assets remain untouched; the child’s clean record and standing Article VIII relocation right are unimpaired; and scale abuse — relocating to produce children outside the curve — remains separately closed by Article XXVII’s standing treasury-levy cascade against the layer where the drain originates. LP-064 continues unamended as the collection mechanics; LP-077’s citizen-originator rule stands untouched as the lex specialis for constructed persons — instantiation is an act of the citizen wherever performed; a birth enters a territory’s standing law.
Ratification Results
| Meritboard | 81% (met) |
| Supreme Court | 8 / 10 (met) |
| Sanctuary | 91% yes (met) |
| Main Layer | 82% yes (met) |
| Lower-Layer Aggregate | 76% yes (met) |
| Presidential Veto | Not exercised |
A Main minority pressed the status reading — the curve should follow the citizen, or relocation becomes a discount. The majority answered with the pairing rule: the household that leaves the curve’s layers leaves the dividend rate with it, and the cascade levy prices whatever scale the discount theory imagines. The margin note recorded, for the register, that the territorial assignment and LP-077’s status-keyed instantiation rule are not in tension — one governs bearing a child into a territory’s law, the other creating a person by one’s own hand.
Article XXVIII mechanism: 1% population signature threshold initiates a petition; Meritboard domain-expert panel drafts the regulation; 80% direct ratification by the affected population enacts it. Layer-wide, district-wide, cross-layer, or advisory-only in -3 Terminal. Dual-key classification (Meritboard + Supreme Court) prevents structural smuggling into the regulatory route.
Restricts non-consensual implantation procedures within -3 voluntary cooperative districts, including force-installed tracking devices, compelled augmentation as debt-satisfaction mechanism, and coerced neural-interface installation during captive-labor arrangements. Ratified at 81% across the voluntary-district population — above the 80% threshold — but under the -3 Terminal advisory-only clause, no federal enforcement operates. Communities honor the regulation voluntarily; the cooperative structure enforces it internally through reputation and exclusion from inter-district commerce.
Ratification & Implementation — Percentage is Support Saturation
| Voluntary District Ratification | 68% support saturation — narrow threshold passage, deeper minority resistance |
| Federal Enforcement Status | Advisory-Only — no federal enforcement |
| Cooperative Enforcement | Internal via reputation and commerce exclusion |
Three adjacent -1 districts coordinated on a regulation establishing standardized fabrication-proxy operational hours, citizen request prioritization tiers, and emergency revival-queue protocols within their shared commercial corridor. Each district ratified independently; the coordinated mechanism demonstrates Whitepaper §10.4 district coalitions producing emergent order across aligned districts.
Per-District Outcome — Ratified · Percentage is Support Saturation
| District A (host) | 84% support saturation — host district bears operational load, mild pragmatic-yes discount |
| District B | 76% support saturation — participant district, contribution-vs-benefit asymmetry produces thinner saturation |
| District C | 89% support saturation — saturation near ratification; coalition had pre-existing operational trust |
Petition from -3 industrial cooperatives proposing a -3 exemption from Article XXV.I’s clean energy mandate, specifically to permit industrial wastewater discharge into shared-watershed infrastructure during commercial mining operations. Dual-key classification confirmed that carving a layer-specific exemption from an absolute federal prohibition is a structural modification to the Charter, not a regulatory calibration. Rerouted to Article XI amendment gauntlet, not pursued.
Dual-Key Disposition
| Meritboard Classification | Structural |
| Supreme Court Classification | Structural (unanimous) |
| Rationale | Absolute federal prohibition cannot be eroded by regulatory petition |
| Petitioner Action | Not pursued |
Main Layer business coalition petition proposing private-contract detention facilities for misdemeanor-level offenses — framed as voluntary contractual arrangements between employer and employee for workplace-conduct violations. Dual-key classification determined that authorizing private detention for any conduct category contradicts the layer-reassignment-as-consequence architecture that defines the Charter’s enforcement model. Reroute to Article XI amendment was automatic. Not pursued.
Dual-Key Disposition
| Meritboard Classification | Structural |
| Supreme Court Classification | Structural (unanimous) |
| Rationale | Private detention contradicts layer-reassignment-as-consequence architecture |
| Petitioner Action | Not pursued |
Civilization-wide regulatory clarification formally affirming that AGI citizens’ petition signatures, ratification votes, and Article XXVIII participation carry weight identical to human citizens’ votes. Non-controversial doctrinal clarification — the substrate neutrality principle had always implied equivalent weight, but the explicit regulatory affirmation closed a residual ambiguity in the petition-coordination infrastructure. Passed overwhelmingly. Support saturation tracks higher at Sanctuary and -3 (architectural and substrate-neutral convergence, respectively) and sits lower in the middle layers where the rule ratified broadly but operational engagement with AGI-heavy civic institutions runs thinner.
Per-Layer Outcome — Ratified · Percentage is Support Saturation
| +1 Sanctuary | 96% support saturation — architectural-alignment rule; saturation ≈ ratification |
| Main Layer | 87% support saturation — mild thinning over AGI-equivalence operational unfamiliarity |
| -1 Noncompliance | 83% support saturation — comparable thinning, less direct AGI-governance exposure |
| -2 Violent Offense | 80% support saturation — pragmatic-yes cohort; substrate-equivalence accepted but low operational salience |
| -3 Terminal (advisory) | 89% support saturation — saturation exceeds ratification; voluntary-district cohort treats substrate neutrality as settled |
Expands downward-visitation framework for Main Layer residents whose family members descended to -1 or -2. Longer permitted visit durations, reduced pre-approval windows, and simplified return-transit protocol. Does not alter any load-bearing layer architecture — the LP-004.2 Backup Vessel Parity framework still applies (home-layer coverage for informed visitors in -1/-2; mandatory vessel-link suspension at the -3 boundary), behavioral observation continues, and origin-layer enforcement posture remains. Calibration detail only.
Ratification — Main Layer · Percentage is Support Saturation
| Main Layer | 74% support saturation — calibration-detail rule; ratification narrow, saturation thinner where residents without affected family members vote pragmatically |
Petition filed in parallel across all five layers addressing regulated hunting of species designated endangered under the civilization’s biodiversity registry. Ratification outcomes diverged sharply along the layer gradient — from categorical prohibition in Sanctuary to full permission in -3 Terminal, where much of the practice already operated under Colosseum classification.
Per-Layer Outcome — Ratified · Percentage is Support Saturation
| +1 Sanctuary | 99% support saturation — Categorical prohibition |
| Main Layer | 65% support saturation — Restricted: certified game preserves, conservation funding mandate |
| -1 Noncompliance | 57% support saturation — Permitted with licensing and reporting |
| -2 Violent Offense | 72% support saturation — Permitted with commercial registration (cooperative-administered) |
| -3 Terminal (advisory) | 91% support saturation — Unrestricted; largely operational via Colosseum classification |
Parallel layer petitions addressing residential, commercial, and through-corridor vehicle speed limits. The layer gradient produced the expected regulatory spread — strict in Sanctuary, moderate in Main, relaxed through the lower layers, with -3 voluntary districts declining to regulate at all.
Per-Layer Outcome — Ratified · Percentage is Support Saturation
| +1 Sanctuary | 92% support saturation — Strict limits (residential 30 km/h, corridor 80) |
| Main Layer | 84% support saturation — Moderate limits (residential 40, corridor 110) |
| -1 Noncompliance | 81% support saturation — Relaxed limits (residential 50, corridor 140) |
| -2 Violent Offense | 80% support saturation — Minimal; cooperative territories set their own |
| -3 Terminal (advisory) | 94% support saturation — Voluntary districts decline to regulate |
Parallel layer petitions addressing casino gambling establishments. Sanctuary prohibited categorically on pre-intervention trust grounds; Main licensed with community reinvestment mandates; lower layers progressively permissive, with -3 unrestricted under existing Colosseum frameworks.
Per-Layer Outcome — Ratified · Percentage is Support Saturation
| +1 Sanctuary | 99% support saturation — Prohibited categorically |
| Main Layer | 65% support saturation — Licensed; community reinvestment mandate |
| -1 Noncompliance | 72% support saturation — Licensed casinos permitted |
| -2 Violent Offense | 81% support saturation — Casino districts permitted, cooperative-operated |
| -3 Terminal (advisory) | 91% support saturation — Unrestricted; part of frontier economy |
Parallel layer petitions addressing public-space intoxication standards. The no-harm-no-consequence principle for personal substance use remains Charter-level constant; the regulatory question is how public impairment affecting others is handled. Layer ambient standards produced divergent thresholds.
Per-Layer Outcome — Ratified · Percentage is Support Saturation
| +1 Sanctuary | 94% support saturation — Prohibited in public spaces |
| Main Layer | 68% support saturation — Restricted to designated venues; ticketed fines for public impairment |
| -1 Noncompliance | 57% support saturation — Light regulation (displacement of impaired persons from commercial zones) |
| -2 Violent Offense | 71% support saturation — No regulation |
| -3 Terminal (advisory) | 92% support saturation — No regulation |
Parallel layer petitions addressing indecent exposure standards in public spaces. Penalties diverged per layer from strong STI consequence in Sanctuary to no institutional regulation in lower layers, with Main and -1 maintaining designated-zone frameworks.
Per-Layer Outcome & Penalty — Ratified · Percentage is Support Saturation
| +1 Sanctuary | 96% support saturation — Prohibited; strong STI consequence |
| Main Layer | 82% support saturation — Prohibited; misdemeanor-level STI impact + fine |
| -1 Noncompliance | 74% support saturation — Prohibited in commercial/family districts; permitted in designated adult zones |
| -2 Violent Offense | 80% support saturation — No institutional regulation; cooperative norms apply |
| -3 Terminal (advisory) | 93% support saturation — No regulation |
Aggregated summary of district-specific curfew regulations enacted across the civilization. Each district files its own Article XXVIII petition; curfews vary in scope (minors-only, commercial-corridor nighttime, seasonal festival periods) and apply only within the ratifying district. This entry summarizes representative cases rather than enumerating every district petition.
Representative District Cases — Ratified · Percentage is Support Saturation
| Main District XY-4801 | 78% support saturation — Minors under 18, 22:00–05:00, residential zones |
| Main District KL-1172 | 70% support saturation — Commercial corridor curfew, 01:00–05:00 |
| -1 District Q-1103 | 83% support saturation — Nighttime commercial zones, 00:00–05:00 |
| Sanctuary District S-0308 | 93% support saturation — Festival-season only, 23:00–05:00 |
| -2 District (cooperative-operated) | 76% support saturation — Non-member entry curfew |
Standardizes legal recognition of marriages when spouses reside in different layers. Addresses property and inheritance rights across layer boundaries, revival-identity transmission of marital status, consent frameworks for cross-layer medical decisions, and child-relocation pathways when one parent descends. Joint Main + Sanctuary ratification because the two upper layers share a functional family-law regime through continuous SAD and institutional interchange.
Joint Ratification — Main + Sanctuary · Percentage is Support Saturation
| Sanctuary | 89% support saturation — saturation ≈ ratification; implementation-discipline concerns minor at this layer |
| Main Layer | 79% support saturation — pragmatic-yes cohort carries the margin; residual concern over joint-administration operational coherence |
Formalizes an 8-year periodic review cadence for recalibrating relative weights among the seven STI dimensions under Article XXII Meritboard audit authority. The seven dimensions themselves remain constitutional and are not adjustable through this mechanism — only the weighting among them. AI Governance-drafted, reflecting the maintenance function the AI governance system performs continuously; the regulation just formalizes the cadence for external audit purposes.
Per-Layer Outcome — Ratified · Percentage is Support Saturation
| +1 Sanctuary | 95% support saturation — audit-cadence rule; architectural alignment with transparency posture |
| Main Layer | 88% support saturation — mild thinning over STI-weighting technical unfamiliarity |
| -1 Noncompliance | 84% support saturation — pragmatic-yes cohort accepts audit principle with thinner engagement on calibration mechanics |
| -2 Violent Offense | 79% support saturation — further thinning; STI salience lower at layer where institutional reliance is partial |
| -3 Terminal (advisory) | 77% support saturation — voluntary-district engagement with STI governance weakest; saturation thinnest |
Main Layer regulation requiring Metric Gated Domains with membership above 10,000 residents to publish their gating criteria publicly in a standardized format accessible through the civic ledger. Contested: larger MGDs argued the publication requirement violates the voluntary-association character of their communities and undermines the confidentiality some criteria legitimately require. Ratified narrowly at 81% — just above the 80% threshold.
Ratification — Main Layer · Percentage is Support Saturation
| Main Layer | 64% support saturation — narrow threshold passage; large pragmatic-yes cohort over a contested transparency/autonomy line |
Attempt by -3 voluntary districts to formally coordinate on shared civic infrastructure maintenance — road networks between districts, private security mutual-aid agreements, commercial standardization for inter-district trade, and shared emergency-response compacts. Ratified at 83% across the voluntary population. Advisory-only per -3 Terminal’s advisory clause, but unlike LP-009 this regulation is honored in practice by the signing cooperatives because it operationalizes existing inter-district cooperation rather than restricting behavior — the content matches what the cooperatives were already doing informally.
Ratification & Implementation — Percentage is Support Saturation
| Voluntary District Ratification | 86% support saturation — saturation exceeds ratification because the regulation formalizes pre-existing informal cooperation |
| Federal Enforcement Status | Advisory-Only — no federal enforcement |
| Cooperative Implementation (Year 1) | 89% of signing cooperatives adopted |
Formalizes the doctrine governing cross-era STI score comparison given the classified/dynamic formula under Article II. Historical scores are preserved-as-computed, never re-normalized — record immutability under Article XX is load-bearing. Cross-era comparisons use AI Governance-published translation coefficients rather than score adjustment. Coefficients are audited on the 8-year STI calibration review cycle established by LP-026. Rejects both re-normalization (violates immutability) and naive cross-era comparison (not coherent under weight evolution). Closes the temporal-comparability gap left open when the formula was classified.
Per-Layer Outcome — Ratified · Percentage is Support Saturation
| +1 Sanctuary | 94% support saturation — temporal-comparability rule; architectural alignment with record-integrity posture |
| Main Layer | 86% support saturation — mild thinning; score-horizon-doctrine technicality reduces saturation depth |
| -1 Noncompliance | 82% support saturation — pragmatic-yes cohort; temporal-normalization mechanics less operationally salient |
| -2 Violent Offense | 78% support saturation — further thinning; long-horizon comparison less load-bearing at layer |
| -3 Terminal (advisory) | 79% support saturation — saturation ≈ ratification; voluntary-district cohort accepts the rule without strong operational stake |
Hermeneutic rule governing what a petition, federal filing, or regulatory proposal may cite as sole legal authority versus as interpretive support. Charter articles, whitepaper sections at specification weight, and federal statutes (LP entries at enacted status) constitute primary authority. Academy capstones, Resource essays, simulation dossiers, and analytical models constitute secondary authority — admissible as interpretive support within a filing, never admissible as sole authority. Secondary authority may rise to primary only through the Tier III canonical adoption procedure under LP-039; a capstone at Tier II Operational remains secondary for purposes of this rule. Distinct from LP-039 on axis: LP-039 governs which secondary references earn institutional reliance (adoption ladder); this rule governs what legal authority any filing may rest on (citation rule). The two operate together — LP-039 creates the path from secondary to primary, this rule enforces that non-upgraded secondary sources cannot substitute for primary authority even when the secondary material is substantively more developed than the controlling primary text. Formalizes the hermeneutic posture the petition-drafting ecosystem had been operating under informally since the Academy and Resources portals matured. Support saturation runs lower at middle layers where the distinction is more operationally consequential (more petition activity, more secondary sourcing); Sanctuary saturation near-identical to ratification (architectural alignment with primary-text posture); -3 advisory saturation weak (voluntary-district petition traffic lower and the distinction less load-bearing).
Per-Layer Outcome — Ratified · Percentage is Support Saturation
| +1 Sanctuary | 95% support saturation — architectural alignment with primary-text posture; saturation ≈ ratification |
| Main Layer | 83% support saturation — thinner saturation where petition activity makes the primary/secondary distinction more operationally consequential |
| -1 Noncompliance | 78% support saturation — further thinning; mixed operational exposure to secondary-source citation practice |
| -2 Violent Offense | 74% support saturation — pragmatic-yes cohort carries margin; hermeneutic distinction weakly salient at layer |
| -3 Terminal (advisory) | 71% support saturation — voluntary-district petition traffic lower and the distinction less load-bearing; thinnest saturation |
Parallel layer petitions addressing commercial content density in public-space AR overlays — the ambient layer every implanted citizen renders by default. The motivating drift was engagement-adaptive overlay advertising: commercial content that re-renders against a passerby’s gaze dwell and external attention indicators. The petitions did not contest the constitutional boundary — §18.8 and §22.1 already bar institutional consequence and broadcast of cognition-adjacent data, and gaze is outwardly expressed conduct — but commerce operating in the gray band between observed attention and inferred interior state was a regulatory question, not a constitutional one, which is precisely why it routed through Article XXVIII rather than the federal track. The layer gradient produced the expected spread, with Sanctuary’s categorical prohibition reasoned from commons character: ambient commerce that adapts to attention states operates too close to the cognition boundary for a pre-intervention commons, even where it is technically external.
Per-Layer Outcome — Ratified · Percentage is Support Saturation
| +1 Sanctuary | 93% support saturation — Commercial overlays prohibited in public commons; opt-in channels only, zero ambient density |
| Main Layer | 71% support saturation — Density-capped; single-gesture permanent dismissal mandatory; gaze-adaptive re-rendering prohibited in public space; commercial corridors exempt at posted density |
| -1 Noncompliance | 75% support saturation — Commercial zones unrestricted; residential density capped |
| -2 Violent Offense | 78% support saturation — Cooperative territories set their own standards; no layer-wide constraint |
| -3 Terminal (advisory) | 92% support saturation — No regulation; the unregulated overlay economy is part of the frontier texture and the voluntary districts vote to keep it |
The petition proposed making the Threshold Inhibition Protocol — the pre-intervention neural-and-drone mechanism that halts harmful acts mid-execution — mandatory and non-disableable for the sexual-assault category specifically within Main Layer. Main’s default enforcement posture is post-intervention: an assault completes, the victim is treated, and the perpetrator routes to -2. The drafters’ case was that for this one category the post-intervention model is structurally inadequate. Sexual assault is the canonical irreversible harm under Article XIV — psychological and relational damage that “reads as irreversible regardless of whether the body was restored” — and in a population with 200–300-year lifespans the duration of that harm is disproportionate to any other recoverable offense. The petition cited the architecture’s own admissions as evidence: revival and neural therapy are “not a reset button,” and LP-060 (Survivor Elective Memory Excision) had just established a recovery-side remedy precisely because the wound otherwise persists. If even the best post-act relief is imperfect and ethically fraught — the drafters argued — the civilization’s higher obligation is to prevent the act, not to perfect the aftermath. LP-062 is the prevention complement to LP-060’s recovery.
Dual-key classification — challenge raised and denied. Because mandatory non-disableable pre-intervention brushes the founding-core-named default (“post-intervention in Main”), a structural-reclassification challenge was filed seeking to reroute the petition to the Article XI amendment gauntlet. Both dual-key bodies denied it, on the LP-034 calibration-not-structural reasoning. The holding: pre-intervention already operates lawfully in Main by election — TIP is user-configurable opt-in coverage in every implant-bearing layer below Sanctuary — so “post-intervention in Main” names the layer’s default, not a prohibition on pre-intervention. A layer making its already-available opt-in coverage non-disableable for a single, expert-scoped harm category calibrates its own enforcement posture; it does not alter the criteria by which residents enter, remain in, or are removed from the layer. A completed assault still routes to -2 — the mandate prevents the act, it does not change the consequence-on-completion. Inflating an operational-posture calibration into the near-impossible amendment route would be precisely the upward suppression the dual-key check exists to prevent. The structural reading — that flipping the default for any category modifies a core-named property — was recorded as the losing side of the dispute. The petition proceeded to Main ratification as Article XXVIII layer-wide regulatory law.
Ratification failed at 79%, below the 80% supermajority floor. The support coalition was broad and the protection sympathy near-universal: the inhibition acts only on the act, costs nothing to the overwhelming majority who would never offend, and the Meritboard expert-drafting panel had scoped the trigger narrowly to overpowering force, incapacitated-victim, and explicit-refusal-then-continuation conditions — deliberately excluding the ambiguous-consent contexts where misclassification was the central fear. Proponents noted the implant is already a continuous intent-monitor under Article II; only the motor-inhibition response was new, not the observation. The dissent that held the vote under 80% was not indifference to the harm — the same population had ratified LP-060 months earlier — but refusal of this implementation. Three streams combined: the non-disableable character breached the implant-obeys-its-bearer autonomy principle that defeated LP-038 (mandatory action without moment-of-consent), and that objection survived even the narrow scoping; precedent anxiety, this being the first non-disableable behavioral-category inhibition proposed for Main, with no principled stopping point once “uniquely irreversible harm” became a category the default could be flipped for; and a visceral discomfort with an automated freeze keyed to the most intimate domain of life that the bearer cannot switch off. At an 80% bar, a contested intimate-autonomy question reliably clusters just short — the protection goal commands the room, the implementation cannot command four-fifths of it.
The -1 Noncompliance parallel petition, filed in the same wave on the “Main passes, -1 follows” expectation, failed harder at 60%. Two compounding factors: -1 operates logging-only with no preemptive-intervention infrastructure, so mandating TIP there would require standing up a preemptive drone-and-monitoring apparatus the layer does not run — a vote outrunning the layer’s capacity to deliver on it — and -1’s rawer autonomy norms weight the non-disableable objection more heavily than Main’s. The Main petition is the failed parent of LP-062.2 (enacted 2203, below): the same protection goal re-grounded as an opt-out-able default — every Main resident auto-enrolled in sexual-assault TIP coverage, with disabling it a deliberate, logged, publicly-visible election rather than the current silent opt-in — which preserves the implant-sovereignty principle the mandate violated while capturing the great majority who would never disable it. The drafters’ postmortem conceded the point the dissent had made: the civilization could deliver almost all of the protection without the mandate, and the population would not surrender the switch to capture the remainder. -1 received no refined child — its failure was infrastructural as much as mechanism, and an opt-out-able default cannot enroll a population in coverage the layer does not provide.
Dual-Key Disposition & Ratification
| Meritboard Classification (challenge) | Calibration, not structural |
| Supreme Court Classification (challenge) | Calibration — challenge denied |
| Main Layer Ratification | 79% yes (below 80% floor — FAILED) |
| -1 Noncompliance (parallel petition) | 60% yes (below 80% floor — FAILED) |
The dual-key denial is canon-clarifying independent of the ratification result: it settles that a layer may make already-available opt-in pre-intervention non-disableable for an expert-scoped harm category as operational calibration, without the change rerouting to Article XI — the default is the layer’s to set, the membership criteria are not. The denial is category-specific and load-bearing in its narrowness: it does not pre-clear bundled, multi-category, or layer-character-redefining pre-intervention mandates, and a sequence of single-category defaults whose cumulative effect would functionally invert Main’s post-intervention identity remains subject to dual-key review and Article XI routing. The anti-smuggling purpose of the dual-key reaches cumulative structural change, not only single-petition structural change — no advocate may later read LP-062 as having pre-approved Sanctuary-by-category migration one regulatory petition at a time. The ratification failure is the cleaner finding still: the population that prevention would protect declined to mandate it, not because the harm is tolerable but because a non-disableable freeze keyed to intimate life is a switch Main would not surrender even against its gravest irreversible harm. The protection goal commands the room; this implementation could not hold four-fifths of it. The Main petition’s refined child — LP-062.2, the opt-out-able default — subsequently cleared at Main; see below.
Replaces LP-062’s non-disableable mandate with an auto-enrolled, opt-out-able default. Every Main resident is enrolled in sexual-assault TIP coverage by default — existing residents enrolled at enactment, all subsequent residents at birth, citizenship activation, or layer entry; the inhibition operates exactly as the mandate would have — the act is halted mid-execution under the same narrowly-scoped trigger (overpowering force, incapacitated victim, refusal-then-continuation) — except the bearer retains a switch. The switch the mandate abolished is restored. What changes from the pre-LP-062 status quo is that disabling the coverage is no longer a silent configuration choice: it is a deliberate, friction-gated election that writes a publicly-visible entry to the bearer’s ledger. The redraft keeps the protection and gives back the switch — and makes flipping the switch off something done in daylight.
The soft-power mechanism, and the line it cannot cross. The load-bearing distinction is that disabling carries no automatic institutional penalty — no STI dock by the core formula, no criminal flag, no layer consequence. Disabling an anti-sexual-assault inhibition is a legal act, and the architecture does not penalize legal acts (the Article XXVI logic: the civilization governs outcomes, not inputs). What the statute does instead is make the act legible: the disable-event posts to the visible ledger, and STI’s public-rating component — the layer population’s own judgment, which the system surfaces but does not impose — responds however the population chooses. This is the entire difference between the redraft and a mandate-in-disguise. An auto-penalized opt-out would be coercion wearing a switch, and would have failed at ratification for the same reason LP-062 failed. The civilization makes the choice cost reputation, not standing. By genre it is a transparency/disclosure law (the LP-006, LP-027 lineage), defensible on the same ground: the disclosed fact is not the bearer’s cognition or body but the configuration of a safety instrument that bears on everyone around them. The sibling move is LP-038.2 — a mandate that failed, redrafted as notification-and-visibility that passed.
Ratified at 87%. Restoring the switch brought home the implant-sovereignty bloc that had killed the mandate; the absence of institutional penalty defused the LP-038/LP-053 pressure-architecture dissent; and default-on inertia plus the reputational cost of a visible opt-out delivers most of the mandate’s protective coverage — the only uncovered residents are those who have publicly marked themselves by disabling. The residual gap is honest and narrow: a determined offender can still disable, absorb the mark, and act — precisely the case the non-disableable mandate would have caught and this redraft cannot. The civilization accepted that gap as the price of keeping the switch. The ~12–14% that held it under 90% was not one objection but a coalition. The largest is the soft-coercion bloc: a right you can exercise only by publicly marking yourself as rape-dangerous is not, they argue, a real switch — the state imposes no formal penalty but designs the reputation trap, which is the LP-052/LP-053 pressure-architecture family in new dress. The Main-purity bloc opposes not the mandate but the default itself: auto-enrollment still shifts the civilizational baseline from post-act consequence toward pre-act inhibition, and restoring the switch does not undo that the layer now leans Sanctuary-ward by default. The ledger-privacy bloc defends not the opt-out but the principle that implant-configuration choices should not become public sexual-risk metadata — a new class of socially-legible bodily settings. And a slippery-category bloc reads the law’s very success as the danger: pass it at 87% and future advocates run the same structure for the next “non-restorable” category — murder, torture, child abuse, domestic violence — one default at a time, the cumulative inversion the LP-062 dual-key note explicitly walls off. None of the four blocs is large enough to block at the 80% floor, because the safety-bearing-on-others framing peels the persuadable majority off each; together they hold the ceiling under 90.
No -1 redraft accompanies this pass. -1’s parent failed on infrastructural grounds as much as autonomy — the layer runs logging-only and operates no preemptive-intervention apparatus to deliver TIP at all — and an opt-out-able default cannot enroll a population in coverage the layer does not provide. The soft-power redraft solves a mechanism objection; it does not build infrastructure. -1’s path remains open and unsolved, which is truer to the layer’s character than a tidy cascade. The pair reads as a single doctrine across two votes: LP-062 established that Main will not accept a non-disableable override even against its gravest irreversible harm; LP-062.2 established that it will accept the same protection delivered as a default, provided the switch survives and flipping it is done in public. Freedom keeps the switch; protection makes flipping it a mark carried in daylight.
Dual-Key Disposition & Ratification
| Dual-Key Classification | Calibration (uncontested — a default-setting change to already-configurable coverage) |
| Main Layer Ratification | 87% yes (met) |
The soft-power instrument — visible, legal, unpenalized, peer-judged — is canonized here as the architecture’s answer to harms too grave to ignore and too intimate to mandate. The civilization does not force virtue; it structures reality so that the choice to forgo a protection others rely on becomes legible, and lets the population assign the weight. The failed mandate and the enacted default are one doctrine: the override Main refused and the disclosure it accepted, delivering nearly the same coverage by consent rather than compulsion.
Died at dual-key classification review — ruled a constitutional conflict rather than a calibration, and rejected before it could reach ratification. The petition proposed to finish the work LP-062.2 had deliberately left undone: to treat the publicly visible opt-out election — the friction-gated, ledger-posted choice to disable one’s own sexual-assault TIP coverage — as an actionable signal. Disabling anti-assault protection, the drafters argued, communicates disposition, and disposition that legible ought to carry weight — core-formula STI consequence, enforcement attention, or both. The parent redraft had built the daylight and then attached nothing to it; the follow-on read that restraint as an unfinished job, not a designed limit, and moved to make the visible mark cost standing rather than only reputation.
Rejected at review on three grounds, each independently sufficient. First, the Article XIII firewall: a measured indicator serves as an evaluative signal, never a direct determinant of punitive consequence, and the §22.1 cognition specification fixes that separation at the act-not-thought boundary. Interior disposition is not conduct, and a legal configuration choice is not the outward harmful act that alone may carry consequence under Article XXVI. Second, visibility is a safeguard, not a trigger: LP-062.2’s public-signal mechanism (§5.6) exists so the population can see the election and weigh it for itself, and §18.8 sets the identical rule for the observation architecture as a whole — disclosure corroborates acts that have already breached a threshold; it does not itself trigger one. Converting that visibility into institutional consequence would turn a disclosure instrument into a thought-adjacent penalty, the precise inversion the firewall exists to forbid. Third, back-door re-importation: to consequence the opt-out is to rebuild the non-disableable mandate LP-062 already refused, because a switch whose use is punished is not a switch. The gauntlet does not grant by increment what it declined by vote.
An independent cold review — run against the statute book alone, with no drafting context and no knowledge of the coalition behind the filing — reached the same rejection on the same firewall. The concurrence was recorded as evidence that the outcome is doctrinal rather than dispositional: the statute book turns the move away on its own terms, not because a particular panel disfavored a particular draft. The disposition completes the line the two prior passes drew. LP-062 fixed the wall above — Main will not accept a protection it cannot switch off, even against its gravest irreversible harm. This pass fixes the wall below — Main will not let the switch, once made visible, be converted into a penalty. What stands between the two is a single bounded doctrine: protection without compulsion above, disclosure without penalty below, with the visible opt-out keeping its designed character as a fact the population weighs rather than a lever the institutions pull.
Dual-Key Classification & Disposition
| Meritboard Classification | Constitutional conflict, not calibration — filing rejected |
| Supreme Court Classification | Firewall conflict affirmed — rejected, not routed to ratification |
| Independent Cold Review | Same rejection, same firewall — recorded as doctrinal, not dispositional |
The disposition sets registry policy as much as doctrine: a draft killed at a pre-ratification gate earns a record of its own when the rejection itself produces precedent, and this is the first such entry. The gauntlet is recorded at every gate, not only at ratification — a filing turned away at classification for colliding with the Charter is a governance outcome the transparency record owes the reader as fully as any enacted law. The substantive holding is the firewall stated in the negative: the civilization will make a choice legible and let its population judge it, and it will not let that legibility become the institution’s own instrument of consequence. Signal is not decision; disclosure is not penalty; a switch that punishes its use was never a switch. Read with LP-062 and LP-062.2, the three passes are one settled shape — the override Main refused, the disclosure it accepted, and the consequence it would not bolt onto the disclosure.
A one-line duty the corpus had assumed rather than stated. LP-047.3 grants a visitor layer-graduated defensive authority; LP-049 supplies the hardware at the gate rental counter; and a traveller’s own home-layer Threshold Inhibition Protocol configuration — coverage elected under her home layer’s regulation — can suppress precisely the defensive response the visitation statutes entitle her to, unless a configuration step is taken that nothing required anyone to mention. In 2305 the seam surfaced in a -1 corridor: a Sanctuary visitor’s home-configured inhibition suppressed her lawful defensive response mid-assault, and she survived on a bystander’s LP-048.3 intervention. The gate audit found the nullification legible in advance from data both counters already held. The petition followed at the 1% threshold and drew signatures from every layer a gate serves.
The rule: every inter-layer gate complex, at transit processing and at the LP-049 rental counter, must disclose to a departing traveller whose active home-layer inhibition configuration would suppress destination-layer defensive authority that the configuration persists across the gate, and must present the configuration step. Disclosure only: no default is altered, no configuration is changed for the traveller, no election is made for her — the counter states the fact and offers the step. The residual trigger-language question (the “equally earned” scope of LP-047.3’s authority) stays with the Article XXI novelty filter, where the audit routed it.
Ratification Results
| Cross-Layer Affected Populations | 88% yes (met) |
Ratification ran high because the rule asks nothing of anyone but the counter. The recorded dissent called it redundant with rental-counter practice; the majority preferred stated to assumed, and noted that a duty resting on practice is exactly the kind of assumption the register exists to retire.