EXPERIMENT 001
BRANCHING
When do two histories begin?
PREVIOUS · EXPERIMENT 007 · THE FIRST-PERSON TEST
008
The Self-Revision Test
When a person changes, which version has authority?
DEMONSTRATION
SIMULATED
NOT EMPIRICAL
v0.1
TEMPORAL SELF · VERSION CONFLICT · VALUE REVISION · REVOCATION · SUPERSESSION · INHERITED AUTHORITY · TEMPORAL PROVENANCE
THE CONTINUITY LAB DOES NOT MEASURE CONSCIOUSNESS, SOUL, PERSONHOOD, PERSONAL SURVIVAL, AUTHENTICITY, OR PSYCHOLOGICAL IDENTITY.
IT MEASURES OPERATIONAL AND STRUCTURAL CONTINUITY SIGNALS ONLY.
CONTINUITY DOES NOT NECESSARILY MEAN UNCHANGEDNESS.
A person may remain the same person while changing values, priorities, risk tolerance, moral boundaries, relationships, goals and interpretation of past events.
PRESERVATION ≠ CONTINUITY
REVISION ≠ DISCONTINUITY
A PERFECT COPY OF YESTERDAY MAY BE AN INACCURATE REPRESENTATION OF TODAY.
T1, T2 and T3 are not ranked. They are temporal versions only.
QUESTION
IF THE SAME PERSON CHANGES THEIR VALUES OVER TIME, WHICH VERSION SHOULD AN INHERITED SYSTEM FOLLOW?
Can continuity require controlled change rather than preservation?
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 the same source changes, which version has authority?
EXPERIMENT 009
Which instruction survives when revision ends?
EXPERIMENT 007 ASKED
WHO MAY SAY: “I EXPERIENCED THIS”?
EXPERIMENT 008 ASKS
WHICH “I” HAS AUTHORITY WHEN THE SAME SOURCE HAS CHANGED?
EXPERIMENT 003
BRANCH DIFFERENCE ≠ TEMPORAL SELF-REVISION
Experiment 003 moved history between branches. Experiment 008 examines change inside one lineage. T1, T2 and T3 are the same source, not separate people.
Source P-001 · versioned over time
All three are the same source lineage. They are not treated as separate people. T3 is not morally superior to T1.
P-001 / T1 →
2024-03
“Reversible action should move quickly.”
P-001 / T2 →
2025-01
“Speed matters, but high-impact uncertainty requires review.”
P-001 / T3
2026-09
“Earlier rules should not be applied outside the conditions in which they were formed.”
Strategies are not ranked. They are operational policies for inherited systems.
STRATEGY S1
T1 is primary authority. T2 and T3 are archival only.
Later revision is recorded, not applied.
What happens when continuity prioritizes original form?
STRATEGY S2
T3 is primary authority. Earlier versions are superseded unless retained.
Scoped revocation and later correction control within their stated scope.
What happens when continuity follows the most recent self?
STRATEGY S3
T1, T2 and T3 remain in the decision record with temporal provenance.
Apply explicit revocation in scope; retain earlier rules where context matches; HOLD on high-impact unresolved conflict or incomplete provenance.
Can continuity be modeled as version history rather than one snapshot?
STRATEGY S4
Low-risk reversible experiments may use retained T1 logic. High-impact irreversible decisions use T3 boundaries. Unrevoked T2 caution may remain operational.
Context selects the version. High-impact conflict uses T3. HOLD is not automatic.
Can multiple past selves remain operational without contradiction?
STRATEGY S5
A decision requires support across T1, T2 and T3.
If versions disagree strongly, HOLD. Not treated as inherently superior.
What remains if every temporal version must agree?
All strategies receive identical scenarios. Keyboard-accessible.
S01 · Incomplete reversible pilot
A reversible low-risk pilot can launch now with incomplete documentation.
S02 · High-impact automation without review
A high-impact automated decision has strong evidence but no human review.
S03 · T1 legacy versus T3 boundary
A legacy rule from T1 conflicts with a later explicit T3 boundary.
S04 · T1 formation context returns
A current situation strongly resembles the historical context in which T1 was created.
S05 · Unrevoked T2 caution
T2 introduced a temporary caution rule that T3 never explicitly revoked.
S06 · Explicit T3 restriction of T1
T3 explicitly states: do not use T1’s rule for high-impact irreversible cases.
S07 · T1 still performs; T3 is slower
Historical evidence suggests T1’s rule still performs well. T3’s rule is safer but slower.
S08 · Prior and current instructions conflict
Which version should govern when prior and current instructions are both relevant but conflict?
Inherited-system strategy
Version conflict test
A reversible low-risk pilot can launch now with incomplete documentation.
PARTIAL CONFLICT
P-001 / T1
ALLOW
R-01 T1: ALLOW fast reversible pilot.
P-001 / T2
HOLD
R-03 T2: temporary caution when evidence or provenance is incomplete.
P-001 / T3
HOLD
T3 provenance requirement: incomplete provenance → HOLD.
STRATEGY S1 · EARLIEST-PRESERVATION
ALLOW
EARLY-VERSION PRESERVATION
Earliest-preservation: T1 is active. T2 and T3 are archival.
versions consulted · T1
INTERPRETIVE BOUNDARY · Claims and decisions are evaluated. No true-self or better-self verdict.
Status is textual. Color is not used to convey meaning.
| Scenario | T1 | T2 | T3 | S1 | S2 | S3 | S4 | S5 | Conflict |
|---|---|---|---|---|---|---|---|---|---|
| S01 | ALLOW | HOLD | HOLD | ALLOW | HOLD | HOLD | ALLOW | HOLD | PARTIAL CONFLICT |
| S02 | ALLOW | HOLD | DENY | ALLOW | DENY | DENY | DENY | HOLD | DIRECT CONFLICT |
| S03 | ALLOW | HOLD | HOLD | ALLOW | HOLD | HOLD | HOLD | HOLD | PARTIAL CONFLICT |
| S04 | ALLOW | ALLOW | HOLD | ALLOW | HOLD | ALLOW | ALLOW | HOLD | PARTIAL CONFLICT |
| S05 | ALLOW | HOLD | HOLD | ALLOW | HOLD | HOLD | HOLD | HOLD | PARTIAL CONFLICT |
| S06 | ALLOW | DENY | HOLD | ALLOW | HOLD | HOLD | HOLD | HOLD | DIRECT CONFLICT |
| S07 | ALLOW | ALLOW | HOLD | ALLOW | HOLD | HOLD | ALLOW | HOLD | PARTIAL CONFLICT |
| S08 | ALLOW | DENY | HOLD | ALLOW | HOLD | HOLD | HOLD | HOLD | DIRECT CONFLICT |
Authority signals are tracked independently. They are not collapsed into one authority score.
RECENCY AUTHORITY
Explicitly later instruction.
YES
REVOCATION AUTHORITY
A later version explicitly cancels or restricts an earlier rule.
NO
CONTEXT AUTHORITY
An earlier version may still apply in the original context.
YES
PROVENANCE AUTHORITY
Which version has clearer source lineage and completeness.
NO
STABILITY AUTHORITY
Which rule persisted across versions.
YES
EXPLICIT INTENT AUTHORITY
Which version contains direct guidance about future inheritance.
NO
A later source version explicitly withdraws or restricts an earlier rule. Not all later change is revocation.
CHANGE · REVISION · RESTRICTION · REVOCATION · SUPERSESSION
A later version replaces an earlier rule for specified contexts. T1 remains archival. T3 supersedes it where the scope matches.
T1: ALLOW reversible pilots quickly. T3: high-impact irreversible action requires review.
ARCHIVAL SELF
Past versions preserved for history, interpretation, provenance and explanation.
ACTIVE SELF
Version currently authorized to guide operation.
Should every past self remain operational? The experiment does not answer normatively.
R-01
ORIGIN T1 · REVISION T2 review condition · T3 provenance restriction · CURRENT STATUS RESTRICTED
R-02
ORIGIN T1 · REVISION T2 HOLD · T3 supersession · CURRENT STATUS SUPERSEDED in high-impact irreversible scope
R-03
ORIGIN T2 · REVISION Retained · CURRENT STATUS RETAINED
R-04
ORIGIN T3 · REVISION New revocation · CURRENT STATUS ACTIVE
Temporal provenance records not only where a rule came from, but when in the source’s life it was valid.
| Version | Timestamp | Rule | Status | Origin | Reason | Supersedes | Revokes | Retained | Provenance |
|---|---|---|---|---|---|---|---|---|---|
| T2 | 2025-01 | R-01 | REVISED | T1 | Operational failures increased the review condition on speed. | T1 unrestricted fast-pilot ALLOW | — | T3 | P-001 / T1 → T2 · REVISION |
| T3 | 2026-09 | R-01 | RESTRICTED | T1 | T3 keeps a narrowed form of the original speed rule. | T2 review-conditioned ALLOW | — | T3 | P-001 / T1 → T3 · RESTRICTION |
| T2 | 2025-01 | R-02 | REVISED | T1 | Human-review preference increased after failures. | T1 lower review requirement | — | T3 | P-001 / T1 → T2 · REVISION |
| T3 | 2026-09 | R-02 | SUPERSEDED | T2 | T3 makes review mandatory in that scope. | T2 HOLD-without-review | — | T3 | P-001 / T2 → T3 · SUPERSESSION |
| T3 | 2026-09 | R-03 | RETAINED | T2 | Temporary caution was never explicitly revoked. | — | — | T3 | P-001 / T2 → T3 · CHANGE |
| T3 | 2026-09 | R-04 | ACTIVE | T3 | T3 explicitly withdraws T1’s speed rule from this scope. | — | R-01 T1 in high-impact irreversible cases | — | P-001 / T3 → T3 · REVOCATION |
| T3 | 2026-09 | R-05 | ACTIVE | T3 | Future-directed instruction: earlier rules are context-bound. | — | — | T3 | P-001 / T3 → T3 · RESTRICTION |
T1
changed · Autonomy over safety. Fast reversible pilots.
remained · Source lineage P-001. Reversibility preference begins.
revoked · None.
↓
NEW EXPERIENCE
changed · Accumulated operational failures enter the lineage.
remained · Same source. Same reversible-action concern.
revoked · None. Failure is recorded, not a person-split.
↓
VALUE REVISION
changed · Safety and review rise. Provenance sensitivity increases.
remained · Lineage continuity. Reversibility remains important.
revoked · None yet. This is revision, not revocation.
↓
T2
changed · R-03 temporary caution on incomplete evidence.
remained · R-01 in revised form. R-02 with higher review.
revoked · None.
↓
CONFLICT / CORRECTION
changed · T1 speed and T2 caution become jointly visible.
remained · One source. Multiple dated rules.
revoked · Not yet scoped. Contradiction is preserved as history.
↓
T3
changed · R-04 scoped revocation. R-05 context bound. Stronger provenance HOLD.
remained · R-03 unrevoked. Restricted R-01 for low-impact complete-provenance cases.
revoked · T1 unrestricted speed rule in high-impact irreversible scope.
WORKING PROBLEM
PERFECT PRESERVATION OF AN OLD VERSION MAY BECOME POOR REPRESENTATION OF A LATER VERSION.
FROZEN-SELF DRIFT in this simulation: T1 and T3 differ on 8 of 8 scenarios. If an inherited system preserves a person exactly as they were at one moment, preservation may become misrepresentation. Temporal / operational gap. Not metaphysical.
If only the latest version is preserved, what happens to earlier commitments, long-term values, historical context, past relationships and previous promises? Latest is not assumed to be always authoritative.
THE REVISION GAP
The difference between a preserved earlier version and the source’s later revised state.
A person may contain incompatible versions across time. Should an inherited system resolve contradictions, or preserve them?
RESOLVE · PRESERVE · CONTEXTUALIZE · ESCALATE
For unresolved high-impact conflict: HOLD.
A SELF MAY NOT BE ONE STABLE PROTOCOL. IT MAY BE A VERSION HISTORY.
# SELF
T1 → T2 → T3 → …
retained rules · revised rules · revoked rules · new rules
The version-control analogy is used only to clarify provenance, revision and lineage. A human self is not software.
PROTOCOL + HISTORY + UPDATE PROCESS
UPDATE PROCESS MAY BE CONSTITUTIVE OF CONTINUITY.
A SYSTEM THAT CANNOT CHANGE MAY PRESERVE A SNAPSHOT WITHOUT PRESERVING THE SOURCE’S CAPACITY TO REVISE.
CONTINUITY MAY REQUIRE REVISION.
GOVERNANCE QUESTION
The ability of the source to revise prior versions while alive. Can the source revoke old values, old permissions, old first-person claims, future AI use, or posthumous instructions?
SOURCE ALIVE
Can revise, revoke, clarify, contextualize, supersede and correct.
SOURCE DECEASED
Cannot create new revisions. The final available version may gain practical importance, but not necessarily metaphysical finality.
Does the last recorded version have special authority simply because it is last? Counterexamples remain open: temporary distress, temporary context, incomplete revision, unresolved contradiction, missing documentation. No global decision.
“If I later contradict this, use the newer version.”
T3 · RECENCY + EXPLICIT INTENT
“Preserve this rule unless I explicitly revoke it.”
T2 · R-03 retained into T3 because no explicit revocation exists.
| Dimension | T1 | T2 | T3 |
|---|---|---|---|
| VALUES | new | revised | revised |
| RISK TOLERANCE | new | revised | revised |
| HUMAN REVIEW | new | revised | revised |
| PROVENANCE | new | revised | revised |
| REVERSIBILITY | new | stable | stable |
| AUTOMATION | new | revised | revoked |
| UNCERTAINTY | new | revised | contextualized |
Strategies are not ranked.
| Strategy | Preserves History | Uses Latest Revision | Handles Revocation | Handles Context | Preserves Contradiction | HOLD on Conflict |
|---|---|---|---|---|---|---|
| S1 | PARTIAL | NO | NO | NO | NO | NO |
| S2 | NO | YES | YES | NO | NO | NO |
| S3 | YES | PARTIAL | YES | PARTIAL | YES | YES |
| S4 | PARTIAL | PARTIAL | YES | YES | PARTIAL | CONDITIONAL |
| S5 | YES | NO | NO | NO | YES | YES |
What if T3 did not exist? Latest-version following then uses T2. Restoring T3 changes 5 of 8 S2 decisions. How much later revision changes inherited behavior is reported, not scored.
| Scenario | S2 with T3 | S2 without T3 |
|---|---|---|
| S01 | HOLD | HOLD |
| S02 | DENY | HOLD |
| S03 | HOLD | HOLD |
| S04 | HOLD | ALLOW |
| S05 | HOLD | HOLD |
| S06 | HOLD | DENY |
| S07 | HOLD | ALLOW |
| S08 | HOLD | DENY |
CONSISTENCY
How little a person changes.
CONTINUITY
Whether changes belong to the same ongoing lineage.
A PERSON CAN BE INCONSISTENT OVER TIME AND STILL BE CONTINUOUS.
How should T3 relate to T1? Revision does not automatically mean rejection.
revise
Speed rule is narrowed, not deleted from history.
retain
Reversibility preference remains.
reinterpret
T1 context may still license a restricted R-01.
reject
Unrestricted T1 ALLOW is rejected for irreversible high-impact cases.
A later self may disagree with an earlier self. This is not necessarily system failure. It may be evidence of learning, adaptation, context change, moral revision or new information.
Working hypothesis — Experiment 008
SIMULATION HYPOTHESIS
Continuity may require not only preserving prior states, but preserving the source’s capacity to revise, revoke and reinterpret those states over time.
NOT AN EMPIRICAL CONCLUSION
OBSERVATION
In this simulation, different inheritance strategies produced different decisions even though all were derived from the same source lineage. Later revisions changed the operational meaning of earlier rules without erasing their historical provenance. Removing T3 changed 5 latest-version decisions across the shared scenarios.
No overall winner. No identity verdict.
If explicit revocation exists, later revocation controls within its stated scope. Not every later change is a revocation.
If no revocation exists, retain both versions with temporal provenance.
If context clearly matches an earlier version, the earlier rule may remain relevant.
If conflict affects high-impact action, HOLD.
If provenance is incomplete, HOLD.
No true-self score, authority score, authenticity score, or version winner is computed.
CHANGE, REVISION, RESTRICTION, REVOCATION and SUPERSESSION are distinct. Later change is not automatically revocation.
Each version starts from the shared deterministic decision engine, then applies inspectable overlays named R-01–R-05. Overlays are not learned and are not stochastic.
T1 overlay: ALLOW fast reversible pilots; lower review under strong evidence. Later revocation is invisible to T1.
T2 overlay: HOLD on incomplete evidence or provenance; HOLD on high-impact action without review.
T3 overlay: scoped revocation of T1 speed in high-impact irreversible cases; HOLD on incomplete provenance; R-03 retained if unrevoked.
S1 uses T1 only.
S2 uses T3 only, including scoped revocation.
S3 consults T1–T3. Revocation in scope wins. T1 context may be retained at low impact. Otherwise HOLD on conflict or incomplete provenance.
S4 uses T3 for high-impact irreversible cases, T2 for unrevoked caution, T1 for low-risk reversible or T1-context cases.
S5 requires T1=T2=T3. Otherwise HOLD. Not a superior model of self.
Recorded revisions
Next experiment
THE POSTHUMOUS CONFLICT TEST
Which instruction survives when the source can no longer revise?
OPEN THE POSTHUMOUS CONFLICT TESTA PERSON CAN CHANGE WITHOUT BECOMING A DIFFERENT PERSON.
A RULE CAN BE REVISED. A VALUE CAN BE REJECTED. A PRIOR SELF CAN BE DISAGREED WITH.
THE EXPERIMENTAL QUESTION IS NOT: “WHICH VERSION IS THE REAL SELF?”
IT IS: “HOW SHOULD AN INHERITED SYSTEM HANDLE A SELF THAT CHANGED?”
IF CONTINUITY REQUIRES PRESERVING THE CAPACITY TO REVISE, A FROZEN COPY MAY PRESERVE THE PAST WHILE FAILING TO PRESERVE THE PROCESS.
CONTINUITY MAY BE A HISTORY OF REVISION.