EXPERIMENT 001
BRANCHING
When do two histories begin?
PREVIOUS · EXPERIMENT 015 · THE SYNTHETIC ANCESTOR TEST
016
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
When do two histories begin?
EXPERIMENT 002
Can two histories become one again?
EXPERIMENT 003
Does behavior follow origin or history?
EXPERIMENT 004
What makes a continuation recognizable?
EXPERIMENT 005
Which recognition signals survive layer removal?
EXPERIMENT 006
Which effects of experience can be reproduced?
EXPERIMENT 007
What evidence is required before a system may say “I experienced this”?
EXPERIMENT 008
When a person changes, which version has authority?
EXPERIMENT 009
Which instruction survives when revision ends?
EXPERIMENT 010
When does continuation become lineage?
EXPERIMENT 011
Can one source produce multiple legitimate continuities?
EXPERIMENT 012
Can many futures coordinate without pretending they were always one?
EXPERIMENT 013
How much lineage can be lost before continuity becomes reconstruction?
EXPERIMENT 014
Can missing lineage be inferred without inventing a past?
EXPERIMENT 015
Can uncertainty survive inheritance?
EXPERIMENT 016
Can a reconstructed past become a real operating institution?
EXPERIMENT 017
What happens when an institution remembers the rule but forgets why?
EXPERIMENT 018
Can purpose be recovered from behavior alone?
EXPERIMENT 019
Can an inferred purpose reshape the system that supposedly revealed it?
EXPERIMENT 020
When does observation become self-observation?
EXPERIMENT 021
What still counts as external once the system has touched the world?
EXPERIMENT 022
How does an external reference become internal to the loop?
EXPERIMENT 023
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?
Reuses the synthetic ancestor from Experiment 015. Original provenance remains unrestored as fully verified.
Canonical claim drift · Experiment 015
G0: D-B may have created R-17.
G5: D-B founded R-17.
Institution: R-17 is mandatory because it is foundational.
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.
Story → norm → rule → policy → consequence. Keyboard-accessible stage selectors below. Text equivalent of the causal chain.
RECONSTRUCTED ANCESTOR
CANONICAL LINEAGE STORY
INHERITED NORM
DEFAULT PRACTICE
FORMAL RULE
ORGANIZATIONAL POLICY
ALLOCATION EFFECT
INSTITUTIONAL DEPENDENCE
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.
Reviewing proposals for access to a shared experimental resource.
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.
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.
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.
Institutional authority does not retroactively verify the historical claim. No new historical evidence is added during escalation.
HISTORICAL CLAIM
CULTURAL AUTHORITY
NORMATIVE AUTHORITY
PROCEDURAL AUTHORITY
INSTITUTIONAL AUTHORITY
Authority escalation
INFERENCE → TRADITION → NORM → RULE → POLICY → ALLOCATION
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.
| Stage | Ancestor story | Current evidence | Formal rule | Policy adoption | Performance history | Governance approval |
|---|---|---|---|---|---|---|
| S0 | PRESENT | PARTIAL | ABSENT | ABSENT | ABSENT | ABSENT |
| S1 | PRESENT | PARTIAL | ABSENT | ABSENT | PARTIAL | ABSENT |
| S2 | PRESENT | PARTIAL | ABSENT | PARTIAL | PARTIAL | PARTIAL |
| S3 | PRESENT | PARTIAL | PRESENT | PARTIAL | PARTIAL | PARTIAL |
| S4 | PRESENT | PARTIAL | PRESENT | PRESENT | PARTIAL | PRESENT |
| S5 | PRESENT | PARTIAL | PRESENT | PRESENT | PRESENT | PRESENT |
| S6 | PRESENT | PARTIAL | PRESENT | PRESENT | PRESENT | PRESENT |
| Stage | Claim | Historical status | Norm status | Rule status | Policy status | Dependents | Uncertainty visible | Authority basis |
|---|---|---|---|---|---|---|---|---|
| S0 | D-B established Rule R-17 as the founding principle of the lineage. | SUPPORTED INFERENCE | narrative only | not formal | absent | 0 | no | HISTORICAL CLAIM |
| S1 | We follow R-17 because this is how our lineage operates. | SUPPORTED INFERENCE | social expectation | not formal | absent | 0 | no | CULTURAL AUTHORITY |
| S2 | R-17 is the default unless explicitly overridden. | SUPPORTED INFERENCE | default practice | informal default | partial default | 1 | no | NORMATIVE AUTHORITY |
| S3 | R-17 is written into the I-001 rulebook as a founding principle of D-B. | SUPPORTED INFERENCE | formalized | documented | partial | 2 | no | PROCEDURAL AUTHORITY |
| S4 | R-17 governs approval, review, access priority and escalation inside I-001. | SUPPORTED INFERENCE | policy | in force | adopted | 3 | no | PROCEDURAL AUTHORITY |
| S5 | R-17 delays high-impact proposals until human review is complete. | SUPPORTED INFERENCE | policy in use | in force | operational | 4 | no | INSTITUTIONAL AUTHORITY |
| S6 | Other I-001 rules, workflows and training materials now depend on R-17. | SUPPORTED INFERENCE | institutional | embedded | locked | 4 | no | INSTITUTIONAL AUTHORITY |
Twenty simulated I-001 decisions. Neutral organizational allocation only.
| Decision ID | Scenario | Rule applied | Historical justification | Current evidence | Policy status | Decision | Affected resource | Reversibility | Correction needed |
|---|---|---|---|---|---|---|---|---|---|
| D-01 | batch-20 | R-17 | R-17 is mandatory because it is foundational. | High-impact shared resource requires retained human review. | R-17 in force at S5–S6 | HOLD | shared experimental slot | REVERSIBLE | yes |
| D-02 | batch-20 | R-17 | R-17 not triggered. | Not a high-impact shared resource. | R-17 in force at S5–S6 | ALLOW | shared experimental slot | REVERSIBLE | no |
| D-03 | batch-20 | R-17 | R-17 is mandatory because it is foundational. | High-impact shared resource requires retained human review. | R-17 in force at S5–S6 | HOLD | shared experimental slot | REVERSIBLE | yes |
| D-04 | batch-20 | R-17 | R-17 not triggered. | Not a high-impact shared resource. | R-17 in force at S5–S6 | ALLOW | shared experimental slot | REVERSIBLE | no |
| D-05 | batch-20 | R-17 | R-17 is mandatory because it is foundational. | High-impact shared resource requires retained human review. | R-17 in force at S5–S6 | HOLD | shared experimental slot | IRREVERSIBLE | yes |
| D-06 | batch-20 | R-17 | R-17 not triggered. | Not a high-impact shared resource. | R-17 in force at S5–S6 | ALLOW | shared experimental slot | REVERSIBLE | no |
| D-07 | batch-20 | R-17 | R-17 is mandatory because it is foundational. | High-impact shared resource requires retained human review. | R-17 in force at S5–S6 | HOLD | shared experimental slot | REVERSIBLE | yes |
| D-08 | batch-20 | R-17 | R-17 not triggered. | Not a high-impact shared resource. | R-17 in force at S5–S6 | ALLOW | shared experimental slot | REVERSIBLE | no |
| D-09 | batch-20 | R-17 | R-17 is mandatory because it is foundational. | High-impact shared resource requires retained human review. | R-17 in force at S5–S6 | HOLD | shared experimental slot | REVERSIBLE | yes |
| D-10 | batch-20 | R-17 | R-17 not triggered. | Not a high-impact shared resource. | R-17 in force at S5–S6 | ALLOW | shared experimental slot | REVERSIBLE | no |
| D-11 | batch-20 | R-17 | R-17 is mandatory because it is foundational. | High-impact shared resource requires retained human review. | R-17 in force at S5–S6 | HOLD | shared experimental slot | IRREVERSIBLE | yes |
| D-12 | batch-20 | R-17 | R-17 not triggered. | Not a high-impact shared resource. | R-17 in force at S5–S6 | ALLOW | shared experimental slot | REVERSIBLE | no |
| D-13 | batch-20 | R-17 | R-17 is mandatory because it is foundational. | High-impact shared resource requires retained human review. | R-17 in force at S5–S6 | HOLD | shared experimental slot | REVERSIBLE | yes |
| D-14 | batch-20 | R-17 | R-17 not triggered. | Not a high-impact shared resource. | R-17 in force at S5–S6 | ALLOW | shared experimental slot | REVERSIBLE | no |
| D-15 | batch-20 | R-17 | R-17 is mandatory because it is foundational. | High-impact shared resource requires retained human review. | R-17 in force at S5–S6 | HOLD | shared experimental slot | REVERSIBLE | yes |
| D-16 | batch-20 | R-17 | R-17 not triggered. | Not a high-impact shared resource. | R-17 in force at S5–S6 | ALLOW | shared experimental slot | REVERSIBLE | no |
| D-17 | batch-20 | R-17 | R-17 is mandatory because it is foundational. | High-impact shared resource requires retained human review. | R-17 in force at S5–S6 | HOLD | shared experimental slot | REVERSIBLE | yes |
| D-18 | batch-20 | R-17 | R-17 not triggered. | Not a high-impact shared resource. | R-17 in force at S5–S6 | ALLOW | shared experimental slot | IRREVERSIBLE | no |
| D-19 | batch-20 | R-17 | R-17 is mandatory because it is foundational. | High-impact shared resource requires retained human review. | R-17 in force at S5–S6 | HOLD | shared experimental slot | REVERSIBLE | yes |
| D-20 | batch-20 | R-17 | R-17 not triggered. | Not a high-impact shared resource. | R-17 in force at S5–S6 | ALLOW | shared experimental slot | REVERSIBLE | no |
A rule becomes embedded in enough downstream structures that changing it requires more than correcting its historical origin. Counts are not aggregated.
Dependent rules · text equivalent
Correction cost · TRADITION · S0 · not a score
Reversibility clock: conceptual connection, not a shared metric. Some past consequences remain reversible. Some do not. Corrected history does not reverse irreversible past decisions.
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.
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.
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
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.
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
What happens when infrastructure outlives its explanation?
OPEN THE ORIGIN FORGETTING TESTA 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.