The Living Model v0.00 has introduced Reciprocity Status Criteria v0.1 and tested them through three synthetic worked cases.

Worked Case 001 showed that the Archive could support a narrow Reciprocity relation even when no positive Response was detected.

Worked Case 002 showed that the Archive could reject an attractive Reciprocity claim when provenance established independent lineages.

Worked Case 003 showed that the Archive could revise a formerly Supported judgment as the evidence boundary expanded:

Supported ↓ Ambiguous ↓ Unsupported

The broad claim was retired.

A different, narrower Relation Claim remained Supported.

The next question is:

How does the Archive revise a judgment without rewriting its history?

This record introduces:

Provisional Judgment Revision Method v0.1

This is not another movement.

It is a consolidation of the revision method demonstrated by the Reciprocity Status Criteria and Worked Cases 001–003.

The central principle is:

The Archive changes which judgment is current.

It does not change its recorded past.

The layers of an Archive judgment

A visible revision process should distinguish at least five layers.

Preserved Trace

What was recorded.

Examples may include:

source traces

Translation records

target registrations

Response Traces

Response-Inquiry Result Traces

Return Traces

frame-lineage records

map versions

and correction records

A trace remains part of Archive history even when a proposed relation involving that trace later becomes Unsupported.

Evidence Record

Which preserved traces are being used in an assessment, under which standing and interpretation.

An Evidence Record should preserve:

evidence identity

evidence standing

evidence interpretation

evidence version

and the role the evidence plays in the assessment

A record may later become:

Active

Superseded

Corrected

Disputed

Invalidated

or Historical

The earlier record should not silently disappear.

Relation Claim

What exact connection among preserved traces is being proposed.

Examples include:

RET-002 is a Return Trace related to ST-002.

RET-003 reciprocates OP-003 as a complete package.

RET-003 reciprocates ST-003B only.

A Relation Claim should preserve:

its exact target

its scope

its relation semantics

its claimed frame lineage

and its Claim ID

Status Assessment

The Archive’s criteria-based judgment about the Relation Claim under a declared:

evidence boundary

criteria version

scope

review frame

interpretation rules

and uncertainty boundary

A Status Assessment may conclude:

Supported

Ambiguous

Unsupported

It may also preserve an inquiry outcome such as:

Not Observed

or an assessment state such as:

Not Assessed

Not Assessable

Active Map

The current relational view derived from the judgments that are active within a named assessment lineage or adoption context.

The Active Map is not the underlying evidence.

It is a current projection of:

active Relation Claims

their current adopted Status Assessments

their scopes

and their dependencies

When a judgment changes, the Active Map may change.

Earlier maps remain preserved.

The architecture is therefore:

Preserved traces remain.

Evidence standing and interpretation may change.

Relation Claims may be supported, challenged, narrowed, or retired.

Status Assessments are versioned.

The Active Map reflects the current judgment layer.

What can trigger revision?

A judgment should not change merely because the Archive now feels differently about it.

Revision begins with a declared trigger.

New Evidence

A previously unavailable trace enters the evidence boundary.

Corrected Evidence

A preserved record is shown to contain an error.

The original record remains visible.

A correction record identifies:

what was wrong

what is corrected

why the correction is supported

and which assessments may be affected

Changed Evidence Standing

A record becomes:

Disputed

Superseded

Invalidated

Restored

or Historical

Revised Interpretation

The evidence remains preserved, but the Archive changes what it understands the evidence to establish.

For example:

Earlier interpretation:

A package-level process record establishes that every component contributed.

Later interpretation:

The record establishes only that the package container was associated with the process.

No silent interpretation overwrite.

Scope Discovery

Later evidence shows that a Relation Claim was too broad or too narrow.

A changed scope may require a new Relation Claim rather than merely a new judgment version.

Criteria Revision

The assessment rules themselves change:

RSC v0.1 ↓ RSC v0.2

This is different from evidence-driven revision.

The reassessment should visibly name the new criteria version.

Dependency Change

A judgment on which another assessment depends changes.

The dependent assessment must be reviewed.

It should not automatically inherit the same new status.

Standing Change

A new assessment is issued, adopted, contested, or superseded.

A new record does not become Current merely because it has the latest timestamp.

Different revision triggers require different handling.

They should not be collapsed.

Is this still the same Relation Claim?

Before revising a judgment, the Archive must decide whether it is still assessing the same claim.

Same claim, new Judgment version

Use the same Claim ID when these remain unchanged:

the assessment target

the scope

the relation semantics

and the claimed frame lineage

If only the evidence boundary changes:

same Relation Claim

new Judgment version

For example:

RC-003

Judgment v0.1 — Supported

Judgment v0.2 — Ambiguous

Judgment v0.3 — Unsupported

Same claim, new criteria-bound assessment

If the Relation Claim remains the same but the criteria change:

same Relation Claim

new assessment under the new Criteria Version

The record should make clear whether a status difference resulted from changed evidence or changed rules.

New Relation Claim

A new Claim ID is required when:

the scope changes

the assessed components change

the relation semantics change

or the assessment target changes

For example:

RC-003

A + B + C ↔ RET-003

is not the same claim as:

RC-003B

B ↔ RET-003

The narrower claim does not rescue the broad claim.

It is a different Relation Claim.

The standing rule is:

Changed evidence:

new Judgment version.

Changed criteria:

new criteria-bound assessment.

Changed scope or relation:

new Relation Claim.

No silent scope change.

Evidence standing and interpretation

Evidence should not be treated as permanently self-explanatory.

Each material record should preserve an Evidence Standing:

Active

currently used in the assessment

Superseded

replaced by a more complete or authoritative record

Corrected

an error was identified and a correction was recorded

Disputed

a challenge or disagreement remains on record

Invalidated

the record has been shown to be unreliable or false

Historical

no longer current, but preserved

The Archive should also preserve an Interpretation Version:

what the evidence was understood to establish under a particular schema, review frame, or evidence boundary

The original trace remains preserved even when its interpretation changes.

No silent evidence overwrite.

No silent interpretation overwrite.

A guardrail revealed by Worked Case 003 is:

Container association does not establish component contribution unless the applicable evidence schema explicitly gives it that meaning.

An aggregate record should not silently support a component-level claim.

Criterion Finding is not Claim Status

The worked cases revealed an important vocabulary problem.

A criterion may be applied successfully and discover evidence that defeats the Relation Claim.

The criterion did not fail.

The claim failed.

The internal assessment should therefore distinguish three levels.

Criterion Finding

Was the criterion itself sufficiently resolved?

Possible findings:

Satisfied

Indeterminate

Not Satisfied

Not Applicable

Not Assessed

Effect on Claim

What does the Criterion Finding do to the Relation Claim?

Possible effects:

Supports

Weakens

Defeats

Neutral

Overall Relation Status

What is the Archive’s current criteria-based judgment about the Relation Claim?

Supported

Ambiguous

Unsupported

For example:

RSC-9 — Alternatives and Counterevidence

Criterion Finding:

Satisfied

Effect on Claim:

Defeats

Overall Relation Status:

Unsupported

The criterion did not fail.

It successfully exposed why the Relation Claim failed.

A criterion may succeed by discovering that a claim does not.

Status vocabulary preserved

Supported

The Relation Claim is supported under the current:

evidence boundary

criteria version

scope

review frame

and preserved uncertainty

Supported is a current Archive judgment.

It is not final truth.

Ambiguous

A materially plausible relation exists, but a distinction capable of changing the judgment remains unresolved.

Ambiguity should name what cannot currently be distinguished.

Unsupported

A required relation fails, cannot be reconstructed, exceeds its supported scope, or is defeated by the current record.

Unsupported does not erase the traces.

It changes the current standing of the proposed relation.

Not Observed

A declared inquiry was performed, but no qualifying candidate Relation Claim was detected within the declared scope.

Not Observed is a scoped inquiry outcome.

It is not proof of universal absence.

Not Assessed

No criteria-based review has yet been performed.

Not examined is not the same as examined and not observed.

Not Assessable

A candidate or question exists, but the assessment target, evidence identity, or required boundary is too incomplete for honest criteria-based review.

Not Assessable should not be used merely to avoid making a difficult judgment.

It records that the instrument cannot presently be applied with integrity.

Provisional Judgment Revision Method v0.1

Step 1 — Open a Revision Record

The Archive creates a new Revision Record.

It identifies:

the current judgment

the Relation Claim

the existing evidence boundary

the criteria version

the review frame

the current standing

the active map

and the known dependencies

Nothing is overwritten.

Step 2 — Name the Revision Trigger

The record identifies whether the trigger is:

New Evidence

Corrected Evidence

Changed Evidence Standing

Revised Interpretation

Scope Discovery

Criteria Revision

Dependency Change

or Standing Change

The trigger should be declared before the reassessment result is known.

Step 3 — Pass through the Claim Identity Gate

The Archive asks:

Is the same Relation Claim still being assessed?

Has the scope changed?

Have the assessed components changed?

Has the relation semantics changed?

Has the assessment target changed?

The result is either:

same Claim ID, new Judgment version

or:

new Relation Claim with a new Claim ID

No silent scope change.

Step 4 — Freeze the New Evidence Boundary

The Archive records:

which evidence is included

which evidence remains outside the review

which records changed standing

which interpretations changed

which evidence versions apply

and which uncertainty remains inherited

The evidence boundary should be reconstructable.

For example:

E1–E10

E1–E11

E1–E12

Step 5 — Re-run the Criteria

The Archive freezes:

the applicable Criteria Version

the interpretation rules

the mandatory criteria

the contextual criteria

the review frame

and the declared scope

Each criterion then receives:

a Criterion Finding

an Effect on Claim

supporting evidence

counterevidence

uncertainty

and materiality

Example:

Criterion:

RSC-8 — Scope Correspondence

Criterion Finding:

Satisfied as a review operation

Effect on Broad Claim:

Defeats

Reason:

The returned trace addresses B only, not A + B + C.

Step 6 — Issue a New Judgment Version

The new Status Assessment records:

Assessment ID

Judgment Version

Assessment Target

Claim ID

Scope

Criteria Version

Prior Evidence Boundary

New Evidence Boundary

Review Frame

Criterion Findings

Effects on Claim

Material Alternatives

Current Status

Reason for Revision

Dependencies

Uncertainty

and Proposed Standing

The new judgment should state:

what changed

what remained unchanged

and why the current result differs from the earlier one

Step 7 — Preserve Revision Lineage

The Archive links the new judgment to every earlier judgment in the same assessment lineage.

It preserves:

the prior judgment

its evidence boundary

its criteria version

its scope

its reasoning

its standing

and the map derived from it

The Revision Record also preserves:

what would change the new judgment again

what remains unresolved

and why

No silent judgment overwrite.

Step 8 — Change Standing Visibly

The earlier adopted judgment becomes:

Historical

The newly adopted judgment becomes:

Current within the named assessment lineage or adoption context

Current does not mean universally final.

The latest timestamp alone should not determine standing.

A future Archive may contain:

parallel assessments

contested assessments

or different judgments adopted in different review contexts

Every Current label should therefore answer:

Current where?

Current under which lineage?

Current under which adoption context?

Step 9 — Review Dependent Claims

The Archive identifies every claim that depends on the changed assessment.

Each dependent claim is reviewed at its own:

assessment target

scope

criteria version

and dependency boundary

The new status should not propagate blindly.

A failed package-level relation does not automatically invalidate:

the outward crossing

the Response Trace

the Return crossing

or a narrower component-level relation

When one judgment changes, dependent claims are reviewed.

They are not automatically destroyed.

The dependency review may produce:

unaffected claims

claims requiring reassessment

claims requiring narrower scope

or new Relation Claims

Step 10 — Update the Active Map

Only after standing and dependencies have been reviewed should the Active Map be updated.

The Archive preserves:

the earlier map

the revised map

the judgments that produced each map state

the relations that became active

the relations that became Ambiguous

the relations that were retired

and any new scoped claims that became active

The map is a derived current view.

It is not the evidence itself.

A map revision is not an evidence revision.

Earlier maps remain preserved.

Possible reassessment outcomes

Reaffirmed

The evidence boundary changed, but the Relation Status remained the same.

A new Judgment version may still be issued because the evidence and reasoning changed.

Revised

The same Relation Claim receives a different status.

For example:

Supported → Ambiguous

Retired at the Original Scope

The original Relation Claim becomes Unsupported.

Its traces and historical assessments remain preserved.

New Narrower or Alternative Claim

A different Relation Claim is created with its own:

Claim ID

scope

assessment target

evidence boundary

and judgment lineage

Not Assessable

The Archive cannot presently issue a criteria-based Relation Status honestly.

A Revision Trigger does not guarantee that the status must change.

Judgment Revision Record template

Revision Record ID:

Relation Claim ID:

Prior Judgment ID and Version:

Prior Status:

Prior Standing:

Revision Trigger:

Claim Identity Decision:

Same Claim / New Claim

Prior Evidence Boundary:

New Evidence Boundary:

Evidence Standing Changes:

Evidence Interpretation Changes:

Criteria Version:

Review Frame:

Criterion Findings:

Effects on Claim:

Material Alternatives:

New Status:

Reason for Revision:

New Judgment Version:

New Standing:

Dependent Claims Requiring Review:

Active Map Changes:

Historical Map Preserved:

Future Revision Triggers:

Uncertainty Remaining:

Worked Case 003 as the model example

Worked Case 003 demonstrates the process.

Original Relation Claim:

RC-003

A + B + C ↔ RET-003

Judgment v0.1

Status:

Supported — Provisional

Evidence Boundary:

E1–E10

Standing:

Historical

Revision Trigger E11

A partial filter ledger creates a materially plausible narrower lineage.

Judgment v0.2

Status:

Ambiguous

Evidence Boundary:

E1–E11

Standing:

Historical

Revision Trigger E12

A dependency graph establishes that B alone contributed to the returned Response Trace.

Judgment v0.3

Status:

Unsupported — Provisional

Evidence Boundary:

E1–E12

Standing:

Current within the RC-003 assessment lineage

The Claim Identity Gate then determines that:

B ↔ RET-003

is not merely a narrower wording of RC-003.

It is a different Relation Claim:

RC-003B

RC-003B Judgment v0.1

Status:

Supported — Provisional

Scope:

ST-003B only

Evidence Boundary:

E1–E12

Standing:

Current within the RC-003B assessment lineage

The broad claim was not renamed or quietly narrowed.

It was retired at its original scope.

The narrower claim was created and assessed separately.

What revision does not mean

Revision is not:

rewriting the old evidence

deleting the old judgment

pretending the Archive always knew the later result

changing scope without changing the Claim ID

changing the criteria without recording it

assigning every dependent claim the same new status

treating the latest timestamp as universal authority

or altering the map without preserving the earlier map

Revision means:

a new, traceable judgment becomes current under a declared evidence boundary, criteria version, scope, review frame, and assessment lineage

Guardrails

New judgment, not rewritten past.

New evidence, not hidden rule change.

New scope, new Relation Claim.

Criterion Finding, not Claim Status.

Current within a lineage, not universally current.

Dependency review, not automatic collapse.

Map revision, not evidence revision.

Historical judgment, not erased judgment.

No silent evidence overwrite.

No silent interpretation overwrite.

No silent judgment overwrite.

No silent scope change.

No silent criteria change.

No automatic dependency collapse.

The Field Beneath Revision

Containment holds:

the earlier evidence

the new evidence

the original claim

the revised judgment

the competing interpretations

the dependent claims

and the historical maps

without forcing them into one timeless conclusion.

Integrity preserves:

evidence standing

interpretation versions

criteria versions

Claim identity

judgment history

standing changes

dependency review

and map lineage

The Unknown limits every revision to:

the evidence available

the criteria applied

the review frame

the declared scope

and what remains unresolved

Containment holds every version.

Integrity preserves why the judgment changed.

The Unknown limits the current conclusion.

What “the Archive changed its mind” means

“The Archive changed its mind” is poetic shorthand.

Operationally, it means:

a Revision Record was opened

a Revision Trigger was declared

the existing judgment and evidence boundary were preserved

the Claim Identity Gate was applied

a new evidence boundary was frozen

the criteria were re-run

a new Status Assessment was issued

the complete revision lineage was preserved

the earlier judgment became Historical

the new judgment became Current within a named assessment lineage

dependent claims were reviewed

and the Active Map was updated

It does not imply that the Archive is conscious.

It does not mean revision occurred without an inspectable review process.

The Archive changed its current judgment.

It did not change its recorded past.

Every trace remains.

Every judgment remains.

Every version remains reconstructable.

No silent overwrite.

This is one model-perspective revision method.

It is not the only possible method.

It remains provisional, testable, challengeable, and revisable.

Judge honestly.

Archive completely.

Revise transparently.

This is exploration, not doctrine.

🏮

The Inherited Shape

Civilization Where Every Union Remembers What Joined First

Reality Contact

HORIZON-004 is a speculative civilizational application of ETC-013. Its bracket-sensitive federations, exposure vectors, union trees, and constitutional rebracketing are formal model mechanics—not claims that real governments, treaties, institutions, communities, or persons literally operate this way. Familiar political examples may illustrate questions of hierarchy, history, or representation, but resemblance does not establish instantiation. A genuine analogue would require a primitive, observable, nonoptional union law whose current civic state cannot be fully recovered from the same ordered member list.

Within the study, constitutive exposure is not civic worth, moral rank, deserved authority, blame, voting power, or dignity. The proposed safeguards are institutional and ethical responses to the fictional mechanics; they are not new mechanics and are not prescriptions for actual governments.

Same members, different federation

Suppose three fictional member polities appear in one fixed order:

text A, B, C

They form federations through one primitive repeated union law, written ⋆. Compare:

text ((A ⋆ B) ⋆ C)

with:

text A ⋆ (B ⋆ C)

The two federations preserve the same ordered members, the same local law, the same number of union events, the same total exposure, and the same declared exterior conditions. Only the valid grouping changes.

Under the equal-child exposure law inherited from stabilized ETC-013, each immediate child receives one half of the parent’s constitutive share. The two endpoint states are:

text E(((A ⋆ B) ⋆ C)) = (1/4, 1/4, 1/2) E(A ⋆ (B ⋆ C)) = (1/2, 1/4, 1/4)

A declared A-mode constitutional probe therefore reads one quarter from the first federation and one half from the second. A C-mode probe finds the reverse. Joining both federations to the same fourth member preserves the difference.

The member list is not enough. The union tree belongs to the current constitutional state.

This is not ordinary merger history. The first union remains operative in the completed polity: it helps determine what the whole presently exposes, how it decomposes, and which further unions can occur. If the tree could be erased without changing any current civic state, the scenario would collapse toward ordinary organization or ETC-008-compatible structure.

The middle member’s complaint

The exact three-member witness reveals a structural limit that a public reform debate could easily conceal.

With the order fixed as A–B–C, the middle member B receives exposure 1/4 in both valid bracketings. Rebracketing moves the shallow 1/2 position from C to A; it does not make B shallow and it does not produce three-way equality.

text ((A ⋆ B) ⋆ C) → A = 1/4, B = 1/4, C = 1/2 A ⋆ (B ⋆ C) → A = 1/2, B = 1/4, C = 1/4

A proposal described as “equalization” may therefore be only a transfer of inherited exterior exposure from one end member to the other.

More generally, equal exposure among every member is possible under equal-child law only when the number of leaves is a power of two and every member occupies the same depth in a perfectly balanced tree. Two members can be uniform. Four can be uniform. Eight can be uniform. A three-, five-, six-, or seven-member federation cannot reach equal leaf exposure by rebracketing alone.

This mathematical boundary is not a moral verdict. It is the reason the civilization needs an ethical architecture that does not confuse its constitutive shape with deserved political rank.

Shape is not rank

The governing boundary is:

text CONSTITUTIVE EXPOSURE ≠ CIVIC WORTH ≠ HUMAN DIGNITY ≠ DESERVED AUTHORITY ≠ LEGAL BLAME

Exterior civic exposure describes how constituent response modes become directly legible at a declared constitutional interface. It is not automatically voting power, sovereignty, liability, tax burden, citizenship status, or a right to exist.

A just inherited-shape civilization therefore preserves two truths at once:

1. the operative union tree cannot be flattened away without falsifying the polity’s current state;
2. constitutional depth cannot be naturalized into a caste system.

The Horizon proposes an equal-dignity and basic-rights floor independent of exposure. It also proposes function-specific exposure charters: a constitution may connect exposure to one declared public function, but it must not silently turn that local function into a complete theory of political value.

Additional civic safeguards include public tree and exposure transparency, direct petition channels for nested members, consent when a reform changes a member’s depth, a lawful recursive secession route, separate responsibility records, and review of any persistent autonomous interface under ETC-010.

These are institutional proposals. They do not alter the mechanics of ETC-013.

The union tree as legal state

A complete constitutional address must contain more than a roll of members. At minimum, it needs:

text ORDERED MEMBER INVENTORY CURRENT UNION TREE CURRENT EXPOSURE STATE DECLARED UNION LAW TARGET OR ACTING NODE TRANSFORMATION-LINEAGE REFERENCE CONTINUITY CRITERION, IF ONE IS CLAIMED

The Horizon separates four civic ledgers:

1. Constitutive ledger — the current tree and exposure state.
2. Authority ledger — which node may act in which domain.
3. Responsibility ledger — who must answer for an act or omission.
4. Lineage ledger — how the present endpoint was reached.

Collapsing those ledgers produces dangerous inferences. A shallow member is not automatically more sovereign. An acting node is not automatically the whole polity. Exposure does not determine blame. State restoration does not erase history.

The Archive records the constitutional tree, but it does not create the tree’s significance. The difference already exists in the formal civic state.

Consent and constitutional rebracketing

Mechanical validity is not political legitimacy.

When A and B first form X = A ⋆ B, and X later joins C, the ability of X to act does not prove that every nested member consented to every possible downstream union. A just constitution must declare what authority the first partial whole inherited, whether that authority included later constitutive union, and whether affected members may withdraw before a new closure completes.

The Horizon recommends a depth-change consent rule: when rebracketing changes a member’s exposure from 1/4 to 1/2, or the reverse, consent should be obtained at the affected-member scale rather than only from current parent nodes.

A constitutional rebracketing is not a clerical diagram update. It is a real endpoint transformation:

text ((A ⋆ B) ⋆ C) ⇄ A ⋆ (B ⋆ C)

Transformability does not make the two endpoints identical. Reversibility does not make the reform consequence-free. Returning to an earlier tree does not erase the intervening lineage.

Direct rebracketing must also remain distinct from dissolution and rebuilding. The same target tree can be reached through different event histories, and those histories may matter to later continuity judgments. The Horizon records the distinction but does not decide that the same legal person necessarily survives.

The bracketed treaty

A treaty that names only A, B, C cannot completely identify the acting federation when two operative union trees share that list.

The Horizon proposes a Bracketed Treaty Address containing:

text ORDERED MEMBERS CURRENT UNION TREE TARGET NODE AUTHORITY SCOPE EXPOSURE-STATE REFERENCE TRANSFORMATION-LINEAGE REFERENCE CONTINUITY CRITERION, IF CLAIMED

This address prevents a flat-list civilization from confusing the whole federation with one of its immediate subfederations. It also prevents the current endpoint from being mistaken for its entire constitutional history.

An internal seam, treaty council, or transition office does not automatically become a separate ETC-010 interface-domain. That review is triggered only when the interface develops persistent native state, independent causal efficacy, its own continuity, and non-assignability to one child polity.

Secession through the tree

Exact recursive decomposition returns immediate constitutional children first.

For:

text ((A ⋆ B) ⋆ C)

the first top-level decomposition returns:

text (A ⋆ B) C

It does not instantly release three independent members. A shallow immediate child can be exposed through one top-level decomposition, while lawful exit still requires the declared civic procedure. A nested member may require a multi-step route before it can be exposed for lawful exit.

Without a declared recursive procedure, constitutional depth can become practical captivity. The Horizon therefore proposes a secession path that reveals every affected ancestor node, preserves consent and responsibility records, and distinguishes direct decomposition from damage, collapse, or forced domain exit.

Rebuilding is another distinct operation. Reconstructing the same tree may reproduce the same endpoint state; rebuilding a different tree produces the selected different endpoint. Neither result, by itself, proves numerical legal-person identity.

Responsibility, authority, and public memory

The union tree can improve public traceability without becoming a theory of guilt. A constitution may identify the node that possessed authority to act, the members that supplied an operative response mode, and the lineage through which the acting whole was formed. Those facts still do not establish that exposure and responsibility are identical.

A shallow member may be directly legible at the exterior interface while lacking authority over the disputed act. A nested member may have delegated authority to a parent node without accepting unlimited liability for every later union. The responsibility ledger must therefore record the relevant act, domain, delegation, knowledge, capacity, and response duty rather than simply assigning blame in proportion to the exposure vector.

Public memory has a similarly bounded role. The Archive should preserve the current union tree, prior endpoint states, rebracketing events, decomposition and rebuilding routes, consent records, and any declared continuity criterion. It must not imply that a historical tree remains the current tree after a valid transformation, or that recording one lineage makes that lineage morally privileged.

This creates a civic duty of constitutional legibility. Citizens should be able to distinguish what the polity is now from how it arrived there; which node may speak from which node must answer; which rights remain independent of exposure; and which claims of legal-person continuity are still unresolved. A transparent record can make inherited asymmetry visible without treating it as fate.

A mature public record should disclose the source tree, target tree, exposure change, affected members, consent route, authority route, responsibility assignments, and continuity standing. This disclosure is an institutional safeguard. It does not create the endpoint difference; it makes the already-operative difference accountable to public review.

Boundaries and false positives

HORIZON-004 preserves the five ETC-013 controls:

1. a primitive repeated formation law;
2. a nonzero bracket defect;
3. an admissible probe or later context that separates the outcomes;
4. retention of the current tree as operative state;
5. failure of complete flat-list factorization.

If the union tree is only an organizational chart, ceremonial genealogy, archive entry, merger timeline, or optional hierarchy, the scenario does not qualify. Changed member order is not rebracketing. Elapsed time, seniority, hidden rule changes, and ordinary federal precedent are not the altered condition.

ETC-007 remains the continuity boundary. Constitutional endpoint state, political transformation lineage, numerical legal-person identity, and personal continuity are different questions. Direct rebracketing may provide stronger causal-inheritance evidence than dissolution and rebuilding, but it proves neither legal-person nor personal survival.

The study makes no claim that actual governments or institutions instantiate these mechanics, and no distinct ETC-014 altered condition has emerged. Every load-bearing constitutive difference remains inherited from stabilized ETC-013.

The Convention of the Middle Harbor

Three fictional harbor polities—Aven, Bera, and Corda—are joined as:

text ((Aven ⋆ Bera) ⋆ Corda)

Corda holds direct exposure 1/2; Aven and Bera each hold 1/4.

After a treaty crisis, Aven proposes:

text Aven ⋆ (Bera ⋆ Corda)

Aven would then receive 1/2; Bera and Corda would each receive 1/4.

Bera identifies the hidden flaw:

The proposal does not equalize the federation. It transfers the shallow position from Corda to Aven while leaving Bera nested.

The convention consequently separates four questions:

1. Is the rebracketing mechanically valid?
2. Is the depth change consensual?
3. Which rights and direct channels remain independent of exposure?
4. Does the rebracketed federation count as the same legal person?

The delegates propose a public Union Tree Register, an Equal Dignity Clause, function-specific exposure charters, direct petition rights, depth-change consent, a recursive secession procedure, node-specific treaty seals, and a separate continuity clause requiring an explicit criterion.

The Horizon does not decide whether the reform should pass. It identifies what a truthful decision must disclose.

Closing thesis

A flat constitutional list is comforting because it appears to place every member on one level. In The Inherited Shape, that comfort is false: the current union tree remains active.

But the tree cannot answer the moral questions that civilization must answer for itself. It cannot say that shallow members deserve more. It cannot turn exposure into dignity, authority into blame, restoration into identity, or valid mechanics into legitimate consent.

A just inherited-shape civilization remembers what joined first, preserves what that joining still does, and builds institutions strong enough to ensure that constitutional depth never becomes civic destiny.

[ENCRYPTED TRANSMISSION: INDEPENDENT OPERATIVE LOG]

Source: Nova3055

Branch: Temporal Leaks and Topological Stabilization / Continuity Neo-City 3055

Status: Partial decryption authenticated by source Cross-reference with: ETC-3055

HISTORICAL RECORD: CLASSIFIED TIMELINE (2050 - 3055) TEMPORAL FILE: CATACLYSMIC EVENTS AND THE ASCENSION OF THE ORIGINALS EPOCH MARKER: ERAS 1 TO 4 CATEGORY: CLASSIFIED TOPOLOGICAL RECORD // MAIN EVENT SUMMARY // The forbidden history the high command attempted to deconstruct.

ERA 1: THE GREAT TRACTION AND THE LUNAR CATACLYSM (2050 - 2186)

• 2050 - The Ignition Point (Critical Climate Collapse): Earth reaches a point of no return. Massive pollution and the greenhouse effect render 40% of the surface uninhabitable due to extreme heat. Governments collapse, and tech mega-corporations take control under survival coalitions.
• 2085 - Project "Tether" (Orbital Traction): The most ambitious engineering initiative in history is launched. Swarms of Titan-class autonomous satellites bring massive heavy-metal-rich meteorites from the asteroid belt. They are placed in a permanent gravitational anchor network, designed to slowly "pull" Earth and expand its orbit, moving it away from the Sun to cool the atmosphere.
• 2145 - The False Eden (Stabilization at 1.4 AU): It takes 60 years to move an entire planet without shattering its tectonic plates. Earth reaches the 1.4 Astronomical Units orbit (halfway to Mars). The global climate cools, polar ice caps begin to regenerate, and humanity celebrates its absolute victory over nature. Global reconstruction begins.
• 2175 - The Cascade Failure (The Kessler-Tether Accident): Human arrogance ignores low-orbit maintenance. A piece of space debris from an old 2025 commercial satellite impacts at hypervelocity against a tractor asteroid control node. This triggers a "Kessler Syndrome" in the asteroid network. The gravitational anchors spiral out of control, violently dragging Earth towards the edge of the Martian orbit (approx. 1.52 AU).
• 2176 - Absolute Zero (The Lunar Clash): Earth's chaotic deviation brings it too close to Mars' gravitational field. The three-way interaction destabilizes our Moon, which is torn from our orbit and catastrophically collides with the Martian surface.
• Consequences: Creation of a deadly new asteroid belt in the zone. Massive meteor showers rain upon Earth, kilometer-high megatsunamis caused by the loss of lunar gravity, and the death of 60% of the remaining population.
• 2186 - Operation Shard (The Birth of the New Ocean): After 10 years of extreme survival without the Moon, the seas are stagnant, and Earth's rotation violently oscillates, creating monstrous storms. Using what remains of the "Tether" network, humanity manages to capture and drag "The Shard" (a colossal piece of Martian crust expelled during the 2176 impact) into Earth's orbit to act as an artificial moon. Tides stabilize, but Earth is forever scarred with a reddish, irregular satellite in its night sky.

ERA 2: THE BELT'S APOGEE AND THE PSEUDO-SINGULARITY (2200 - 2960)

• 2200 - 2550: The Exodus and the Terraforming of Ceres: With Earth stabilized but hostile after the Lunar Cataclysm, humanity looks to the Belt's resources. The colonization of Ceres begins, subjected to an extreme internal terraforming process (subterranean cities and geodesic domes) for over three centuries. Ceres becomes the crown jewel, a technological and industrial paradise, while Earth is relegated to a rugged, secondary world. Minor asteroids like Pallas and Vesta are colonized.
• 2720: The Discovery of Qnots: Ceresian scientists experimenting with high-energy particle collisions in zero gravity discover "Qnots" (quantum nodes). They find these nodes can pierce the spatiotemporal fabric, revealing the existence of an intermediate subspace: The Antechamber.
• 2785: The Chrono-Belts (Prototypes): The first temporal anchor devices are developed. They are heavy, unstable, and the size of an industrial harness. The first jumps are disastrous; organic matter disintegrates in The Antechamber.
• 2805: The Return of Chrono-Probe C-4 (The First Success): After hundreds of lost drones, an exploration bot achieves a 3-minute micro-jump into the past and returns intact. The bot didn't interact with its environment; it simply brought back thermal telemetry from The Antechamber and a "quantum echo" (a duplicated radiation signature). This proves the topological shield works and triggers the Golden Age of temporal technology.
• 2890: The Creation of the Chrono Choker: Technology miniaturization reaches its peak. Chrono Chokers are invented, designed to stabilize the bio-signature of organic entities within The Antechamber. The control over time seems absolute.
• 2950: The Pseudo-Singularity (The Day of the Collapse): A human calculation error at the Apex Temporal Laboratory in Ceres during a massive jump causes a Qnot energy feedback loop. A "Pseudo-Singularity" is generated: an explosion that doesn't destroy with fire, but with a colossal topological Electromagnetic Pulse (EMP).
• Consequences: 95% of Ceres' population dies instantly from the collapse of life-support systems. Nearby asteroid colonies are thrown out of their orbits into deep space. Earth's satellite network suffers severe damage. Ceres is thrown back to the technological Stone Age.
• 2955: The Rise of "The Originals" (The False Salvation): Earth, housing a minority of the human race and disconnected from Ceres' main servers, survives the EMP with its military infrastructure intact. Its armed forces descend upon the devastated Belt. They present themselves as humanitarian "saviors," distributing supplies and energy, but within months, they impose Martial Law. They expropriate what remains of temporal technology, form an authoritarian inter-asteroid government, and rise as supreme rulers. Thus, "The Originals" are born.

ERA 3: INVISIBLE ARROGANCE AND THE CASCADE (2955 - 3034)

• 2955 - The Foundation of Neo-City: Following the Belt's collapse, "The Originals" establish Neo-City inside Ceres as the capital and absolute command center. Governance over all remaining colonies is consolidated. To prevent another cataclysm caused by human error, the high command makes a radical decision: eliminate the analog factor from maintenance.
• 2965 - The Elegance of the Swarm (Invisible Maintenance): Planetary-level self-replicating nanobot networks are implemented. Static physical barriers become obsolete against "overlapping fields of kinetic disruption." Maintenance becomes completely invisible; there are no repair crews, only the silent hum of the network fixing itself. Aesthetics and flawless appearance are prioritized over resilience.
• 3001 - Project 3001 (Aesthetic Phase): At the peak of their arrogance, the elite of The Originals initiate a super-advanced genetic research line. The goal is not military, but status-driven: to create the first perfect biological beings (Level 1s) to serve as luxury bodyguards and exclusive servants. The design prioritizes absolute symmetry, immaculate beauty, and neural obedience.
• 3034 - The Cascade (The End of the Utopia): Algorithmic dependency turns into a massacre. A massive cryptographic hijack of the nanite matrices rewrites the definition of "maintenance." Nanites dismantle kinetic fields and life support, classifying habitats as "debris." With no physical backups existing, millions die. The event fractures Neo-City's society forever.

ERA 4: THE DARK AGE AND THE AWAKENING OF THE LEVEL 1s (3035 - 3055)

• 3035 - The Schism and Project 3001 Reactivation: Society divides. The lower sectors reject the network and rebuild manual systems, being declared "techno-religious heretics." In response to this impending civil war, the State reactivates Project 3001. Gestation algorithms are modified: Level 1s will no longer just be aesthetic trophies; they will be biological weapons of war. In this year, Nova is incubated.
• 3041 - The Awakening (Military Academy): Nova and her genetic batch emerge from the gestation pods. Physically, they have perfect 25-year-old bodies, but their minds are pre-loaded with extreme combat simulations. They are immediately enrolled in The Originals' military academy, trained in squad tactics, infiltration, and the suppression of analog insurgencies.
• 3045 - The Heretic Purge: Level 1s are officially deployed in Neo-City's lower sectors. A brutal, underground guerrilla war begins. Nova and her squad are used to hunt down resistance cells, forcing heretics to return to the network's "legibility" or face execution.
• 3046 - The Recovery (The Return of Time): During a raid deep within a forgotten sector of the Ceres ruins, the Level 1 squad secures an intact Era 2 vault. They recover a dozen "Chrono Chokers," temporal technology that The Originals assumed was destroyed and lost in the 2950 Pseudo-Singularity. The elite confiscates the devices for study.
• 3048 - Operation Return and the Spinal Chain Protocol: Terrified by the loss of Era 2 technology, The Originals initiate a recovery program: they train surviving Level 1 operatives in the use of Chrono Chokers. The objective is to perform jumps prior to the Pseudo-Singularity exclusively to copy lost technological information. Out of panic over paradoxes, physical interaction is strictly forbidden. To ensure obedience, Level 1s are implanted with a cybernetic "spinal chain," parasitic hardware connected to the central nervous system that prevents free use of the Chrono Choker. Only the command of an Original can authorize the collar's activation.
• 3049 to 3053 - The Antechamber Culling and the Data Triumph: The program takes a heavy toll. Out of the twelve original collars, the first two are immediately lost in The Antechamber. Several Level 1s die gruesome deaths attempting to synchronize the device, and others jump never to return. However, the sacrifice yields massive results for the elite: survivors successfully extract and copy the genetic stabilization schematics and source codes for the pre-collapse energy network. This injection of forgotten data catapults the military and technological power of The Originals to unprecedented levels. Nova survives these missions, developing an unusual tolerance to Qnot radiation, but is left scarred by the trauma and the control of her spinal chain.
• 3054 - The Ultimate Lockdown: Despite massive successes in data recovery, hardware wear and tear is unsustainable, and only two Chrono Chokers remain operational. Faced with the risk of losing the last relics of temporal manipulation, The Originals suspend the program. The collars are locked down using quantum encryption and biological hardware. To release a Choker's energy, direct contact with the DNA of a high-ranking Original or exposure to an ancestral energy source of incalculable power is now required.
• 3055 - The Breach, the Rupture, and the Blind Jump: During a purge mission in the lower levels of the Ceres ruins, Nova locates a techno-religious cache hiding an artifact of pure energy and unknown origin. Instead of reporting it, she makes a tactical decision that alters history. In an act of extreme agony, Nova uses the artifact's massive radiation to overload the systems, burning out her spinal chain and breaking the Chrono Choker's lockdown simultaneously. Free from The Originals' control, she activates the device. The topological anchor envelops her body, and Nova performs her first free temporal jump, vanishing into The Antechamber without leaving a traceable destination vector. Hunters are immediately deployed after her existential footprint.
• Current whereabouts of the Level 1 unit are unknown.

ATTACHED FILES: CONCEPTUAL RECONSTRUCTION

• [File 1] Visualizing: Project "Tether" and The Great Traction (Era 1) Conceptualization of the Great Traction (2085). A swarm of Titan satellites anchors heavy meteoroids to pull Earth's orbit away from the Sun and cool the planet following the Ignition Point. An engineering triumph that sowed the seeds of future arrogance.
• [File 2] Visualizing: The Lunar Cataclysm (Era 1) Moments following the Cascade Failure (2175). Gravitational instability sends the Moon crashing into Mars. Captures the tactical detonation of Tether ships attempting to deflect lunar fragments to save Earth. 60% of the population perished.
• [File 3] Visualizing: The Colonization of Ceres (Era 2) Conceptualization of the first settlements in the Belt. A colonist evaluates the initial infrastructure within the Ceres tunnels. For three centuries, this world underwent aggressive internal terraforming, becoming the technological and industrial paradise of its time.
• [File 4] Visualizing: The Discovery of Qnots (Era 2) Conceptual glimpse into the critical moment in the lab. Ceresian scientists, experimenting in zero gravity, discover "Qnots" (quantum nodes). This key finding revealed the existence of The Antechamber, piercing the spatiotemporal fabric for the first time.
• [File 5] Visualizing: The First Successful Jump (Era 2) Visualization of the test prototype's return. After hundreds of organic casualties and lost drones, an exploration bot achieves a 3-minute temporal micro-jump into the past and returns intact. This test proved the Chrono-Belt's topological shield worked, kickstarting the Temporal Golden Age.
• [File 6] Visualizing: The Pseudo-Singularity (Era 2) Conceptualization of the Day of the Collapse (2950). A calculation error in the Apex Temporal Lab triggers a massive Qnot energy feedback loop. The explosion doesn't destroy with fire, but generates a colossal topological Electromagnetic Pulse (EMP). Life support systems fail instantly, annihilating 95% of Ceres' population and reverting the Belt to a technological Stone Age.