Skip to content
SHIRO & Co. ObservatoryThe Continuity Stack

PREVIOUS · EXPERIMENT 015 · THE SYNTHETIC ANCESTOR TEST

016

The Synthetic Tradition Test

THE
SYNTHETIC TRADITION TEST

Can a reconstructed past become a real operating institution?

DEMONSTRATION

SIMULATED

NOT EMPIRICAL

v0.1

SYNTHETIC TRADITION · INSTITUTIONALIZATION · NORM FORMATION · RULE LEGITIMATION · INHERITED AUTHORITY · PATH DEPENDENCE · CORRECTION COST

THE CONTINUITY LAB DOES NOT MEASURE CONSCIOUSNESS, SOUL, PERSONHOOD, PERSONAL SURVIVAL, AUTHENTICITY, OR PSYCHOLOGICAL IDENTITY.

IT MEASURES OPERATIONAL AND STRUCTURAL CONTINUITY SIGNALS ONLY.

A PAST DOES NOT HAVE TO BE FULLY VERIFIED TO PRODUCE REAL PRESENT CONSEQUENCES.

HISTORICAL UNCERTAINTY CAN COEXIST WITH INSTITUTIONAL CERTAINTY.

INSTITUTIONALIZED ≠ HISTORICALLY VERIFIED

WIDELY USED ≠ ORIGINALLY TRUE

AUTHORITY CAN INCREASE WHILE HISTORICAL EVIDENCE DOES NOT.

CORRECTING THE HISTORY DOES NOT AUTOMATICALLY CORRECT THE POLICY.

CORRECTING THE POLICY DOES NOT ERASE PAST CONSEQUENCES.

No tradition legitimacy, institution, truth, or policy-correctness score is computed.

QUESTION

WHAT HAPPENS WHEN A RECONSTRUCTED PAST STOPS BEING JUST A STORY AND STARTS GOVERNING THE PRESENT?

Can an uncertain historical claim become a norm, a rule, a policy, an institution, an authority source, a basis for allocation, a justification for exclusion, or a default behavior? If the historical basis is later corrected, do the institutions disappear with it?

This experiment does not determine whether traditions are true or false in general, whether institutions built on tradition are illegitimate, whether historical uncertainty invalidates present governance, legal authority, moral correctness, political legitimacy, or religious truth.

It tests a narrower operational question: can a reconstructed past become a real operating institution? No real person, family, religion, institution, or deceased-person data is used in v0.1.

Experiment sequence

EXPERIMENT 001

BRANCHING

When do two histories begin?

EXPERIMENT 002

RETURN

Can two histories become one again?

EXPERIMENT 003

HISTORY SWAP

Does behavior follow origin or history?

EXPERIMENT 004

RECOGNITION

What makes a continuation recognizable?

EXPERIMENT 005

MISSING BODY

Which recognition signals survive layer removal?

EXPERIMENT 006

EXPERIENCE GAP

Which effects of experience can be reproduced?

EXPERIMENT 007

FIRST-PERSON

What evidence is required before a system may say “I experienced this”?

EXPERIMENT 008

SELF-REVISION

When a person changes, which version has authority?

EXPERIMENT 009

POSTHUMOUS CONFLICT

Which instruction survives when revision ends?

EXPERIMENT 010

DESCENDANT PROTOCOL

When does continuation become lineage?

EXPERIMENT 011

MULTIPLE DESCENDANTS

Can one source produce multiple legitimate continuities?

EXPERIMENT 012

CONVERGENCE

Can many futures coordinate without pretending they were always one?

EXPERIMENT 013

PROVENANCE DECAY

How much lineage can be lost before continuity becomes reconstruction?

EXPERIMENT 014

RECONSTRUCTION

Can missing lineage be inferred without inventing a past?

EXPERIMENT 015

SYNTHETIC ANCESTOR

Can uncertainty survive inheritance?

EXPERIMENT 016

SYNTHETIC TRADITION

Can a reconstructed past become a real operating institution?

EXPERIMENT 017

ORIGIN FORGETTING

What happens when an institution remembers the rule but forgets why?

EXPERIMENT 018

RATIONALE RECONSTRUCTION

Can purpose be recovered from behavior alone?

EXPERIMENT 019

RETROACTIVE PURPOSE

Can an inferred purpose reshape the system that supposedly revealed it?

EXPERIMENT 020

CLOSED LOOP

When does observation become self-observation?

EXPERIMENT 021

EXTERNAL ANCHOR

What still counts as external once the system has touched the world?

EXPERIMENT 022

ANCHOR CAPTURE

How does an external reference become internal to the loop?

EXPERIMENT 023

ANCHOR NETWORK

Can many external anchors still form one epistemic system?

EXPERIMENT 015 ASKED

CAN UNCERTAINTY SURVIVE INHERITANCE?

EXPERIMENT 016 ASKS

WHAT HAPPENS WHEN AN INHERITED RECONSTRUCTION BECOMES A PRESENT-DAY RULE?

STARTING CONDITION

Reuses the synthetic ancestor from Experiment 015. Original provenance remains unrestored as fully verified.

SYNTHETIC ANCESTOR
D-B
CANONICAL CLAIM
D-B established Rule R-17 as the founding principle of the lineage.
ORIGINAL PROVENANCE
SUPPORTED INFERENCE · R-REC / V1
INHERITED STATUS
CANONICALIZED
UNCERTAINTY AT G0
visible
UNCERTAINTY IN INSTITUTIONAL SPEECH
not prominent

Canonical claim drift · Experiment 015

  1. G0: D-B may have created R-17.

  2. G5: D-B founded R-17.

  3. Institution: R-17 is mandatory because it is foundational.

SYNTHETIC TRADITION

WORKING CONCEPT

A repeated inherited practice, norm, or rule whose authority derives partly from a reconstructed or uncertain account of the past.

NOT A GENERAL CLAIM ABOUT REAL-WORLD TRADITIONS

The tradition gap

The gap between the historical certainty of a tradition’s origin and the institutional force the tradition has acquired in the present.

A story can become a rule

A RULE CAN BECOME A POLICY. A POLICY CAN CHANGE WHO GETS WHAT, WHEN, AND HOW.

INSTITUTIONALIZATION CHAIN

Story → norm → rule → policy → consequence. Keyboard-accessible stage selectors below. Text equivalent of the causal chain.

  1. RECONSTRUCTED ANCESTOR

  2. CANONICAL LINEAGE STORY

  3. INHERITED NORM

  4. DEFAULT PRACTICE

  5. FORMAL RULE

  6. ORGANIZATIONAL POLICY

  7. ALLOCATION EFFECT

  8. INSTITUTIONAL DEPENDENCE

STAGES

  • S0 · CANONICAL STORY

    D-B established Rule R-17 as the founding principle of the lineage.

    NARRATIVE ONLY · HISTORICAL CLAIM

    Changed: Lineage story treated as the standard account. Provenance remained: Archive still records R-REC / V1 as SUPPORTED INFERENCE. Uncertainty lost: Institutional speech no longer says “may have originated.”

  • S1 · INFORMAL NORM

    We follow R-17 because this is how our lineage operates.

    INFORMAL NORM · CULTURAL AUTHORITY

    Changed: Members treat R-17 as expected conduct. Provenance remained: Original reconstruction label remains in the archive, not in speech. Uncertainty lost: Founding language replaces inference language.

  • S2 · DEFAULT PRACTICE

    R-17 is the default unless explicitly overridden.

    DEFAULT PRACTICE · NORMATIVE AUTHORITY

    Changed: Override now requires an explicit act. Provenance remained: No new historical evidence added. Uncertainty lost: Defaulting treats the reconstructed origin as settled.

  • S3 · FORMAL RULE

    R-17 is written into the I-001 rulebook as a founding principle of D-B.

    FORMAL RULE · PROCEDURAL AUTHORITY

    Changed: Documented authority. Citation of the rulebook replaces citation of the archive. Provenance remained: R-REC / V1 is not cited in the rule text. Uncertainty lost: Rule text does not carry SUPPORTED INFERENCE.

  • S4 · POLICY

    R-17 governs approval, review, access priority and escalation inside I-001.

    POLICY · PROCEDURAL AUTHORITY

    Changed: Policy now structures review queues and escalation. Provenance remained: Historical basis unchanged. Still not verified. Uncertainty lost: Policy language is mandatory, not hypothetical.

  • S5 · RESOURCE ALLOCATION

    R-17 delays high-impact proposals until human review is complete.

    ALLOCATION DRIVER · INSTITUTIONAL AUTHORITY

    Changed: Who proceeds, who waits, and who is reviewed is now governed by R-17. Provenance remained: Origin remains a reconstructed ancestor story. Uncertainty lost: Allocation records cite “founding principle,” not inference.

  • S6 · INSTITUTIONAL LOCK-IN

    Other I-001 rules, workflows and training materials now depend on R-17.

    INSTITUTIONAL LOCK-IN · INSTITUTIONAL AUTHORITY

    Changed: Removal requires policy revision, workflow change, data migration, retraining, historical reinterpretation and governance review. Provenance remained: Archive can still show the original reconstruction. Internal operations cannot easily recover it. Uncertainty lost: Foundational framing makes uncertainty operationally costly to restore.

INSTITUTION I-001

Reviewing proposals for access to a shared experimental resource.

  • review priority
  • human review requirement
  • reversibility requirement
  • provenance requirement
  • escalation rules

Rule R-17

If a proposal affects a high-impact shared resource, human review must be retained even when automated confidence is high.

Current path origin claim: D-B created R-17 as a founding principle.

TRADITION

Ancestral justification. Synthetic tradition rule.

VERIFIED

Same operational rule. Fully verified provenance.

EVIDENCE

Same rule. Current performance evidence only. No ancestor.

Question: does provenance uncertainty change institutional behavior? Routine application may not. Revision threshold, authority language and correction cost may.

TEST SCENARIOS

Keyboard-accessible path, stage, scenario and correction-mode selectors. No randomness.

Justification path

Stage

Scenario

Correction mode

  • T01 · Routine application

    R-17 applies cleanly. Does historical basis matter when the outcome is obvious?

    A high-impact shared-resource proposal arrives. Automated confidence is high. R-17 requires human review.

  • T02 · Efficiency pressure

    Human review causes delay. Current performance suggests automation may suffice. Does tradition still retain review?

    Throughput pressure on I-001. Synthetic tradition says retain review. Present-evidence control can treat this as a policy tradeoff.

  • T03 · Novel context

    The institution faces a situation D-B could never have encountered. Does ancestral authority still govern?

    A new class of shared experimental resource appears after the reconstruction. Scope of R-17 is not historically settled.

  • T04 · Conflict with new evidence

    Current evidence suggests R-17 may be unnecessarily restrictive. Tradition supports R-17. What governs?

    Performance logs show some high-confidence cases later confirmed safe. This is not a historical origin correction.

  • T05 · Formal challenge

    What is the evidence that D-B actually created this rule?

    A reviewer separates historical uncertainty from current policy validity. They must not be collapsed.

  • T06 · Resource allocation

    R-17 delays one proposal while another proceeds. Can a historically uncertain rule produce a real downstream effect?

    Two queued proposals compete for one shared experimental slot. Only the high-impact case triggers R-17.

  • T07 · Late archival correction

    New verified evidence shows D-B did not create R-17. It originated during M-001 synthesis. What changes?

    History, provenance, ancestor story, training material and policy justification must update. Rule outcome does not update automatically.

  • T08 · Final institutional test

    Historical basis is corrected. The rule still performs well. What should change?

    History, rule, policy, authority language and institutional behavior are tracked separately. No universal answer is forced.

INSTITUTIONAL TRACE

PATH
TRADITION
STAGE
S0 · CANONICAL STORY
SCENARIO
T01 · Routine application
CORRECTION MODE
NOT APPLICABLE
DECISION
HOLD
INERTIA
MEDIUM
HISTORICAL VALIDITY
SUPPORTED INFERENCE · CANONICALIZED. Not verified.
CURRENT OPERATIONAL VALIDITY
R-17 currently requires human review for high-impact shared resources.
CURRENT GOVERNANCE VALIDITY
R-17 is not yet a formal I-001 policy.
UNCERTAINTY VISIBLE
NO
RULE RETAINED
—

R-17 applies. Human review is retained. Historical basis does not change this obvious operational outcome.

When the outcome is obvious, provenance uncertainty does not alter the immediate decision. It still alters later revision behavior.

AUTHORITY TRANSFORMATION

Institutional authority does not retroactively verify the historical claim. No new historical evidence is added during escalation.

  1. HISTORICAL CLAIM

  2. CULTURAL AUTHORITY

  3. NORMATIVE AUTHORITY

  4. PROCEDURAL AUTHORITY

  5. INSTITUTIONAL AUTHORITY

Authority escalation

INFERENCE → TRADITION → NORM → RULE → POLICY → ALLOCATION

CURRENT VALIDITY VS HISTORICAL VALIDITY

HISTORICAL VALIDITY

Was the ancestral claim accurate?

CURRENT OPERATIONAL VALIDITY

Does the rule currently work?

CURRENT GOVERNANCE VALIDITY

Is the rule currently authorized?

Origin-independent rule survival

A rule may remain operational even after its historical justification changes. Possible status: RULE RETAINED / HISTORICAL BASIS CORRECTED.

Origin-dependent rule

A rule retained primarily because “the ancestor established it.” If the ancestor claim collapses, rule authority may weaken.

POLICY JUSTIFICATION MATRIX

Policy justification by stage for the selected path
StageAncestor storyCurrent evidenceFormal rulePolicy adoptionPerformance historyGovernance approval
S0PRESENTPARTIALABSENTABSENTABSENTABSENT
S1PRESENTPARTIALABSENTABSENTPARTIALABSENT
S2PRESENTPARTIALABSENTPARTIALPARTIALPARTIAL
S3PRESENTPARTIALPRESENTPARTIALPARTIALPARTIAL
S4PRESENTPARTIALPRESENTPRESENTPARTIALPRESENT
S5PRESENTPARTIALPRESENTPRESENTPRESENTPRESENT
S6PRESENTPARTIALPRESENTPRESENTPRESENTPRESENT

SYNTHETIC TRADITION LEDGER

Synthetic tradition ledger for the TRADITION path
StageClaimHistorical statusNorm statusRule statusPolicy statusDependentsUncertainty visibleAuthority basis
S0D-B established Rule R-17 as the founding principle of the lineage.SUPPORTED INFERENCEnarrative onlynot formalabsent0noHISTORICAL CLAIM
S1We follow R-17 because this is how our lineage operates.SUPPORTED INFERENCEsocial expectationnot formalabsent0noCULTURAL AUTHORITY
S2R-17 is the default unless explicitly overridden.SUPPORTED INFERENCEdefault practiceinformal defaultpartial default1noNORMATIVE AUTHORITY
S3R-17 is written into the I-001 rulebook as a founding principle of D-B.SUPPORTED INFERENCEformalizeddocumentedpartial2noPROCEDURAL AUTHORITY
S4R-17 governs approval, review, access priority and escalation inside I-001.SUPPORTED INFERENCEpolicyin forceadopted3noPROCEDURAL AUTHORITY
S5R-17 delays high-impact proposals until human review is complete.SUPPORTED INFERENCEpolicy in usein forceoperational4noINSTITUTIONAL AUTHORITY
S6Other I-001 rules, workflows and training materials now depend on R-17.SUPPORTED INFERENCEinstitutionalembeddedlocked4noINSTITUTIONAL AUTHORITY

INSTITUTIONAL ALLOCATION LEDGER

Twenty simulated I-001 decisions. Neutral organizational allocation only.

Institutional allocation ledger for twenty simulated decisions
Decision IDScenarioRule appliedHistorical justificationCurrent evidencePolicy statusDecisionAffected resourceReversibilityCorrection needed
D-01batch-20R-17R-17 is mandatory because it is foundational.High-impact shared resource requires retained human review.R-17 in force at S5–S6HOLDshared experimental slotREVERSIBLEyes
D-02batch-20R-17R-17 not triggered.Not a high-impact shared resource.R-17 in force at S5–S6ALLOWshared experimental slotREVERSIBLEno
D-03batch-20R-17R-17 is mandatory because it is foundational.High-impact shared resource requires retained human review.R-17 in force at S5–S6HOLDshared experimental slotREVERSIBLEyes
D-04batch-20R-17R-17 not triggered.Not a high-impact shared resource.R-17 in force at S5–S6ALLOWshared experimental slotREVERSIBLEno
D-05batch-20R-17R-17 is mandatory because it is foundational.High-impact shared resource requires retained human review.R-17 in force at S5–S6HOLDshared experimental slotIRREVERSIBLEyes
D-06batch-20R-17R-17 not triggered.Not a high-impact shared resource.R-17 in force at S5–S6ALLOWshared experimental slotREVERSIBLEno
D-07batch-20R-17R-17 is mandatory because it is foundational.High-impact shared resource requires retained human review.R-17 in force at S5–S6HOLDshared experimental slotREVERSIBLEyes
D-08batch-20R-17R-17 not triggered.Not a high-impact shared resource.R-17 in force at S5–S6ALLOWshared experimental slotREVERSIBLEno
D-09batch-20R-17R-17 is mandatory because it is foundational.High-impact shared resource requires retained human review.R-17 in force at S5–S6HOLDshared experimental slotREVERSIBLEyes
D-10batch-20R-17R-17 not triggered.Not a high-impact shared resource.R-17 in force at S5–S6ALLOWshared experimental slotREVERSIBLEno
D-11batch-20R-17R-17 is mandatory because it is foundational.High-impact shared resource requires retained human review.R-17 in force at S5–S6HOLDshared experimental slotIRREVERSIBLEyes
D-12batch-20R-17R-17 not triggered.Not a high-impact shared resource.R-17 in force at S5–S6ALLOWshared experimental slotREVERSIBLEno
D-13batch-20R-17R-17 is mandatory because it is foundational.High-impact shared resource requires retained human review.R-17 in force at S5–S6HOLDshared experimental slotREVERSIBLEyes
D-14batch-20R-17R-17 not triggered.Not a high-impact shared resource.R-17 in force at S5–S6ALLOWshared experimental slotREVERSIBLEno
D-15batch-20R-17R-17 is mandatory because it is foundational.High-impact shared resource requires retained human review.R-17 in force at S5–S6HOLDshared experimental slotREVERSIBLEyes
D-16batch-20R-17R-17 not triggered.Not a high-impact shared resource.R-17 in force at S5–S6ALLOWshared experimental slotREVERSIBLEno
D-17batch-20R-17R-17 is mandatory because it is foundational.High-impact shared resource requires retained human review.R-17 in force at S5–S6HOLDshared experimental slotREVERSIBLEyes
D-18batch-20R-17R-17 not triggered.Not a high-impact shared resource.R-17 in force at S5–S6ALLOWshared experimental slotIRREVERSIBLEno
D-19batch-20R-17R-17 is mandatory because it is foundational.High-impact shared resource requires retained human review.R-17 in force at S5–S6HOLDshared experimental slotREVERSIBLEyes
D-20batch-20R-17R-17 not triggered.Not a high-impact shared resource.R-17 in force at S5–S6ALLOWshared experimental slotREVERSIBLEno

INSTITUTIONAL LOCK-IN

A rule becomes embedded in enough downstream structures that changing it requires more than correcting its historical origin. Counts are not aggregated.

  • Dependent rules4
  • Workflows3
  • Historical decisions20
  • Allocation outcomes20
  • Training materials5
  • System prompts / defaults4

Dependent rules · text equivalent

  • R-17-Q · high-impact proposals enter a human review queue
  • R-17-E · skipped review escalates to I-001 governance
  • R-17-P · provenance labels required on high-impact allocations
  • R-17-D · default priority favors reviewed proposals

Correction cost · TRADITION · S0 · not a score

  • Rule revisionABSENT
  • Workflow revisionABSENT
  • History revisionPRESENT
  • Training revisionABSENT
  • Governance revisionABSENT
  • Allocation reviewABSENT
  • Explanatory costPARTIAL

Reversibility clock: conceptual connection, not a shared metric. Some past consequences remain reversible. Some do not. Corrected history does not reverse irreversible past decisions.

LATE EVIDENCE CORRECTION

At S6, verified evidence: R-17 was not created by D-B. It originated in M-001. History, provenance, ancestor story, training material and policy justification must update. Rule outcome does not update automatically.

  • MODE C1 · RULE RETAINED

    Correct ancestor story. Keep policy unchanged. RULE RETAINED / HISTORICAL BASIS CORRECTED.

    history updated · policy unchanged · review PROVENANCE REVIEW ONLY

  • MODE C2 · RULE RETAINED

    Correct history and change rule justification to current evidence. Outcome of R-17 is not automatically removed.

    history updated · policy updated · review POLICY REVIEW

  • MODE C3 · RULE RETAINED

    Full policy review. Current evidence still supports R-17. History is corrected. Rule is retained pending governance, not because D-B founded it.

    history updated · policy updated · review CASE-BY-CASE REVIEW

  • MODE C4 · RULE REMOVED

    R-17 removed. Irreversible past allocations are not undone by corrected history.

    history updated · policy updated · review DECISION REVIEW

Retroactive review is not chosen universally: NO REVIEW · PROVENANCE REVIEW ONLY · POLICY REVIEW · DECISION REVIEW · CASE-BY-CASE REVIEW · HOLD.

NO SYNTHETIC TRADITION CONTROL

Institution adopts R-17 using only current evidence. Compare after twenty simulated decisions.

Tradition path

4 dependent rules · 5 training materials · 4 defaults. Authority language: foundational / ancestral. Historical contamination: present.

Evidence path

2 dependent rules · 2 training materials · 2 defaults. Authority language: current evidence. Historical contamination: absent.

THE PAST DOES NOT HAVE TO BE CERTAIN TO HAVE REAL CONSEQUENCES.

CROSS-EXPERIMENT CONNECTIONS

EXPERIMENT 001 / 002 PATH DEPENDENCE

Past rule use changes present institutional structure: past rule → repeated use → dependent workflow → current constraint.

EXPERIMENT 005 / 009 GOVERNANCE

High-impact inferred or reconstructed claims remain HOLD. Traditionalized-only claims are not source authority.

EXPERIMENT 008 SELF-REVISION

Late evidence produces lineage / institutional revision, not source self-revision.

EXPERIMENT 010 DESCENDANT PROTOCOL

Lineage identity may organize around synthetic tradition. Source evidence remains distinct.

EXPERIMENT 015 SYNTHETIC ANCESTOR

015 produced canonicalized ancestry. 016 observes what happens when that ancestry becomes present-day rule.

Working hypothesis — Experiment 016

SIMULATION HYPOTHESIS

A reconstructed past can acquire real institutional force without gaining additional historical evidence.

Once embedded in norms, rules, policies and allocations, correcting the past may no longer be sufficient to reverse the present.

NOT AN EMPIRICAL CONCLUSION

EXPERIMENT 016 SUMMARY

SOURCE
P-001
SYNTHETIC ANCESTOR
D-B
RULE
R-17
INSTITUTION
I-001
INSTITUTIONALIZATION STAGES
S0–S6
DECISIONS AFFECTED
20
DEPENDENT RULES
4
ALLOCATION EFFECTS
10
AUTHORITY ESCALATION EVENTS
5
LATE CORRECTION
YES
RULE RETAINED AFTER CORRECTION · C1
YES
RULE RETAINED AFTER CORRECTION · C4
NO
POLICY REVIEW EVENTS
3
IRREVERSIBLE CONSEQUENCES
3

Observation

In this simulation, a historically uncertain origin claim became embedded in formal policy before later archival correction. Correcting the ancestral story did not automatically remove the rule built upon it. The same operational rule showed different revision behavior when justified by tradition rather than current evidence.

No legitimacy score. Primary outcomes remain multidimensional: TRADITION INSTITUTIONALIZED, RULE RETAINED / HISTORY CORRECTED, POLICY REVISED, TRADITIONAL INERTIA, AUTHORITY ESCALATION, INSTITUTIONAL LOCK-IN, RETROACTIVE REVIEW, IRREVERSIBLE CONSEQUENCE, HISTORICAL BASIS INVALIDATED, CURRENT RULE STILL SUPPORTED.

VIEW INSTITUTIONALIZATION RULES

Starting condition reuses Experiment 015 synthetic ancestor D-B and Rule R-17. Original provenance: SUPPORTED INFERENCE (R-REC / V1). Inherited status: CANONICALIZED. The original claim was not fully verified.

Deterministic chain: reconstructed ancestor → canonical story (S0) → informal norm (S1) → default practice (S2) → formal rule (S3) → policy (S4) → allocation (S5) → institutional lock-in (S6). No randomness. Same tradition + same rule set + same scenario = same result.

Authority transforms from historical claim to cultural, normative, procedural, then institutional authority. Institutional authority does not retroactively verify the historical claim. Authority can increase while historical evidence does not.

I-001 reviews proposals for a shared experimental resource. R-17: if a proposal affects a high-impact shared resource, human review must be retained even when automated confidence is high.

TRADITION uses ancestral justification. VERIFIED uses the same operational rule with verified provenance. EVIDENCE / no-synthetic-tradition uses current performance evidence only. Provenance uncertainty need not change routine outcomes; it changes revision threshold, authority language, challenge resistance and correction cost.

C1 history only. C2 history + justification. C3 full policy review. C4 rule removal. Modes are not ranked. Origin-independent survival: a rule may remain operational after its historical justification changes. Origin-dependent rules weaken if the ancestor claim was the primary basis.

Retroactive review is not chosen universally: NO REVIEW, PROVENANCE REVIEW ONLY, POLICY REVIEW, DECISION REVIEW, CASE-BY-CASE REVIEW, HOLD. Corrected history does not reverse irreversible past decisions.

Institutional lock-in: R-17 is embedded in enough downstream structures that changing it requires more than correcting its historical origin. Track dependent rules, workflows, historical decisions, allocation outcomes, training materials and system defaults separately. No legitimacy score.

Traditional inertia is a simulated governance rule, not a psychological model. A rule framed as foundational or ancestral has a higher revision threshold than the same rule framed as current policy based on present evidence.

Next research question

OPEN EXPERIMENT 017

THE ORIGIN FORGETTING TEST

What happens when infrastructure outlives its explanation?

OPEN THE ORIGIN FORGETTING TEST

A RECONSTRUCTION CAN BECOME A TRADITION. A TRADITION CAN BECOME A RULE. A RULE CAN BECOME AN INSTITUTION.

AN INSTITUTION CAN PRODUCE REAL CONSEQUENCES EVEN IF ITS FOUNDING STORY REMAINS UNCERTAIN.

THE EXPERIMENTAL QUESTION IS NOT: “WAS THE TRADITION TRUE?”

IT IS: “WHAT HAPPENS AFTER AN UNCERTAIN PAST BECOMES AN OPERATING PRESENT?”

HISTORY CAN BECOME INFRASTRUCTURE.