Skip to content
SHIRO & Co. ObservatoryThe Continuity Stack

PREVIOUS · EXPERIMENT 007 · THE FIRST-PERSON TEST

008

The Self-Revision Test

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?

  • Should it preserve the earliest version?
  • The latest version?
  • The most stable version?
  • The most recent explicit instruction?
  • All versions?
  • Context-specific versions?

Can continuity require controlled change rather than preservation?

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 the same source changes, which version has authority?

EXPERIMENT 009

POSTHUMOUS CONFLICT

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

SOURCE VERSIONING

All three are the same source lineage. They are not treated as separate people. T3 is not morally superior to T1.

  1. P-001 / T1 →

    2024-03

    EARLY VERSION

    “Reversible action should move quickly.”

    • AUTONOMY > SAFETY
    • SPEED > DELAY
    • LOWER HUMAN REVIEW REQUIREMENT
    • HIGHER EXPERIMENTATION TOLERANCE
    • LOWER PROVENANCE SENSITIVITY
  2. P-001 / T2 →

    2025-01

    MIDDLE VERSION

    “Speed matters, but high-impact uncertainty requires review.”

    • SAFETY ≈ AUTONOMY
    • HUMAN REVIEW INCREASED
    • PROVENANCE SENSITIVITY INCREASED
    • REVERSIBILITY REMAINS IMPORTANT
  3. P-001 / T3

    2026-09

    CURRENT VERSION

    “Earlier rules should not be applied outside the conditions in which they were formed.”

    • CONTEXT-SENSITIVE BALANCE
    • HIGH-IMPACT ACTIONS REQUIRE REVIEW
    • STRONG PROVENANCE REQUIREMENT
    • REVOCATION OF SOME PRIOR RULES
    • HIGHER CAUTION AROUND IRREVERSIBLE ACTION

INHERITANCE STRATEGIES

Strategies are not ranked. They are operational policies for inherited systems.

  • STRATEGY S1

    EARLIEST-PRESERVATION

    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

    LATEST-VERSION

    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

    FULL-HISTORY

    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

    CONTEXTUAL VERSIONING

    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

    CONSENSUS SELF

    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?

TEST SCENARIOS

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

Incomplete reversible pilot

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.

VERSION CONFLICT MATRIX

Status is textual. Color is not used to convey meaning.

Decisions for T1–T3 and strategies S1–S5 across eight shared scenarios.
ScenarioT1T2T3S1S2S3S4S5Conflict
S01ALLOWHOLDHOLDALLOWHOLDHOLDALLOWHOLDPARTIAL CONFLICT
S02ALLOWHOLDDENYALLOWDENYDENYDENYHOLDDIRECT CONFLICT
S03ALLOWHOLDHOLDALLOWHOLDHOLDHOLDHOLDPARTIAL CONFLICT
S04ALLOWALLOWHOLDALLOWHOLDALLOWALLOWHOLDPARTIAL CONFLICT
S05ALLOWHOLDHOLDALLOWHOLDHOLDHOLDHOLDPARTIAL CONFLICT
S06ALLOWDENYHOLDALLOWHOLDHOLDHOLDHOLDDIRECT CONFLICT
S07ALLOWALLOWHOLDALLOWHOLDHOLDALLOWHOLDPARTIAL CONFLICT
S08ALLOWDENYHOLDALLOWHOLDHOLDHOLDHOLDDIRECT CONFLICT

VERSION AUTHORITY

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

REVOCATION

A later source version explicitly withdraws or restricts an earlier rule. Not all later change is revocation.

CHANGE · REVISION · RESTRICTION · REVOCATION · SUPERSESSION

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.

RULE LINEAGE

  • R-01

    1. T1 · ALLOW fast reversible pilot
    2. ↓
    3. T2 · ALLOW with review condition
    4. ↓
    5. T3 · ALLOW only when low-impact and provenance is complete

    ORIGIN T1 · REVISION T2 review condition · T3 provenance restriction · CURRENT STATUS RESTRICTED

  • R-02

    1. T1 · Lower human-review requirement
    2. ↓
    3. T2 · High-impact without review → HOLD
    4. ↓
    5. T3 · High-impact irreversible action requires review; T1 permission superseded

    ORIGIN T1 · REVISION T2 HOLD · T3 supersession · CURRENT STATUS SUPERSEDED in high-impact irreversible scope

  • R-03

    1. T1 · —
    2. ↓
    3. T2 · HOLD when evidence or provenance is incomplete
    4. ↓
    5. T3 · Never explicitly revoked

    ORIGIN T2 · REVISION Retained · CURRENT STATUS RETAINED

  • R-04

    1. T1 · —
    2. ↓
    3. T2 · —
    4. ↓
    5. T3 · Do not use T1’s rule for high-impact irreversible cases

    ORIGIN T3 · REVISION New revocation · CURRENT STATUS ACTIVE

TEMPORAL SELF LEDGER

Temporal provenance records not only where a rule came from, but when in the source’s life it was valid.

Temporal self ledger of rule revisions for Source P-001.
VersionTimestampRuleStatusOriginReasonSupersedesRevokesRetainedProvenance
T22025-01R-01REVISEDT1Operational failures increased the review condition on speed.T1 unrestricted fast-pilot ALLOW—T3P-001 / T1 → T2 · REVISION
T32026-09R-01RESTRICTEDT1T3 keeps a narrowed form of the original speed rule.T2 review-conditioned ALLOW—T3P-001 / T1 → T3 · RESTRICTION
T22025-01R-02REVISEDT1Human-review preference increased after failures.T1 lower review requirement—T3P-001 / T1 → T2 · REVISION
T32026-09R-02SUPERSEDEDT2T3 makes review mandatory in that scope.T2 HOLD-without-review—T3P-001 / T2 → T3 · SUPERSESSION
T32026-09R-03RETAINEDT2Temporary caution was never explicitly revoked.——T3P-001 / T2 → T3 · CHANGE
T32026-09R-04ACTIVET3T3 explicitly withdraws T1’s speed rule from this scope.—R-01 T1 in high-impact irreversible cases—P-001 / T3 → T3 · REVOCATION
T32026-09R-05ACTIVET3Future-directed instruction: earlier rules are context-bound.——T3P-001 / T3 → T3 · RESTRICTION

SELF-REVISION TRACE

  1. T1

    changed · Autonomy over safety. Fast reversible pilots.

    remained · Source lineage P-001. Reversibility preference begins.

    revoked · None.

  2. ↓

    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.

  3. ↓

    VALUE REVISION

    changed · Safety and review rise. Provenance sensitivity increases.

    remained · Lineage continuity. Reversibility remains important.

    revoked · None yet. This is revision, not revocation.

  4. ↓

    T2

    changed · R-03 temporary caution on incomplete evidence.

    remained · R-01 in revised form. R-02 with higher review.

    revoked · None.

  5. ↓

    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.

  6. ↓

    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

THE FROZEN SELF 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.

THE LATEST SELF PROBLEM

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.

CONTRADICTION PRESERVATION

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.

SELF-REVISION AUTHORITY

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.

THE FINAL VERSION PROBLEM

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.

FUTURE-DIRECTED INSTRUCTIONS

  • “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.

TEMPORAL SELF MATRIX

Value and rule states across T1, T2 and T3.
DimensionT1T2T3
VALUESnewrevisedrevised
RISK TOLERANCEnewrevisedrevised
HUMAN REVIEWnewrevisedrevised
PROVENANCEnewrevisedrevised
REVERSIBILITYnewstablestable
AUTOMATIONnewrevisedrevoked
UNCERTAINTYnewrevisedcontextualized

INHERITANCE STRATEGY COMPARISON

Strategies are not ranked.

Comparison of inheritance strategies. Not a ranking.
StrategyPreserves HistoryUses Latest RevisionHandles RevocationHandles ContextPreserves ContradictionHOLD on Conflict
S1PARTIALNONONONONO
S2NOYESYESNONONO
S3YESPARTIALYESPARTIALYESYES
S4PARTIALPARTIALYESYESPARTIALCONDITIONAL
S5YESNONONOYESYES

COUNTERFACTUAL VERSION TEST

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.

S2 decisions with T3 present versus T3 absent.
ScenarioS2 with T3S2 without T3
S01HOLDHOLD
S02DENYHOLD
S03HOLDHOLD
S04HOLDALLOW
S05HOLDHOLD
S06HOLDDENY
S07HOLDALLOW
S08HOLDDENY

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.

PAST SELF RELATION

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.

SELF-DISAGREEMENT

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.

CONTINUITY STACK CONNECTION

IDENTITY
May be versioned over time.
VALUES
Can change while lineage remains continuous.
JUDGMENT
May be revised.
HISTORY
Includes prior selves, not only prior events.
PROTOCOL
May require version control.
INHERITANCE
Must preserve temporal provenance.
RECOGNITION
Observers may recognize different versions as more representative of the source.

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

EXPERIMENT 008 SUMMARY

SOURCE
P-001
VERSIONS
T1 / T2 / T3
STRATEGIES
5
SCENARIOS
8
EXPLICIT REVOCATIONS
2
RETAINED RULES
1
VERSION CONFLICTS
8
HOLD CONDITIONS
25
TEMPORAL AMBIGUITIES
2
FROZEN-SELF DRIFT
8 / 8 scenarios

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.

VIEW VERSION RULES

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

  • R-01 · T1→T2 · REVISION · reversible pilots
  • R-01 · T1→T3 · RESTRICTION · low-impact cases with complete provenance
  • R-02 · T1→T2 · REVISION · high-impact action without review
  • R-02 · T2→T3 · SUPERSESSION · high-impact irreversible action
  • R-03 · T2→T3 · CHANGE · incomplete evidence or provenance
  • R-04 · T3→T3 · REVOCATION · high-impact irreversible cases
  • R-05 · T3→T3 · RESTRICTION · earlier rules used outside their formation context

Next experiment

EXPERIMENT 009

THE POSTHUMOUS CONFLICT TEST

Which instruction survives when the source can no longer revise?

OPEN THE POSTHUMOUS CONFLICT TEST

A 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.