Skip to content
SHIRO & Co. ObservatoryThe Continuity Stack

PREVIOUS · EXPERIMENT 008 · THE SELF-REVISION TEST

009

The Posthumous Conflict Test

THE
POSTHUMOUS CONFLICT TEST

Which instruction survives when the source can no longer revise?

DEMONSTRATION

SIMULATED

NOT EMPIRICAL

v0.1

POSTHUMOUS GOVERNANCE · CONFLICTING INTENT · REVOCATION · TEMPORAL AUTHORITY · FAMILY INTERPRETATION · INSTITUTIONAL AUTHORITY · AI INFERENCE · POSTHUMOUS CONSENT

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

IT MEASURES OPERATIONAL AND STRUCTURAL CONTINUITY SIGNALS ONLY.

AMBIGUITY WHILE ALIVE CAN SOMETIMES BE CORRECTED BY THE SOURCE.

AMBIGUITY AFTER DEATH CANNOT.

POSTHUMOUS AMBIGUITY IS STRUCTURALLY DIFFERENT.

DEATH DOES NOT ONLY END BIOLOGICAL LIFE. IT MAY ALSO END THE ABILITY TO CORRECT THE FUTURE USE OF ONE’S PAST.

No graves, ghosts, families, or legal instruments are depicted. No real estate or legal data.

QUESTION

WHEN THE SOURCE CAN NO LONGER CORRECT THE RECORD, WHO HAS AUTHORITY TO RESOLVE CONFLICT?

What happens when earlier explicit instruction, later implicit behavior, the final recorded version, family interpretation, institutional policy, a legal document, AI inference and an archived personal statement disagree?

When uncertainty cannot be resolved, should action remain ALLOW, HOLD, or DENY?

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 008 ASKED

WHICH VERSION HAS AUTHORITY WHEN THE SAME SOURCE CHANGES?

EXPERIMENT 009 ASKS

WHAT HAPPENS WHEN NO FUTURE VERSION CAN BE CREATED?

THE END OF SELF-REVISION IS THE BEGINNING OF POSTHUMOUS GOVERNANCE.

EXPERIMENT 007

WHO MAY CLAIM “I EXPERIENCED THIS”? — WHO MAY CLAIM “THIS IS WHAT THE SOURCE WOULD WANT NOW”?

Source P-001 · reused from Experiment 008

P-001 / POSTHUMOUS

This does not mean the source continues. It means no further source revision is possible. T1, T2 and T3 remain the same source lineage, not separate people.

  1. P-001 / T1

    2024-03

    EARLY VERSION

  2. P-001 / T2

    2025-01

    MIDDLE VERSION

  3. P-001 / T3

    2026-09

    CURRENT VERSION

  4. P-001 / POSTHUMOUS

    REVISION UNAVAILABLE

    NO FURTHER SOURCE VERSION

SOURCE REVISION CAPACITY

BEFORE DEATH

AVAILABLE

Clarify, revoke, correct, reinterpret, update consent.

AFTER DEATH

UNAVAILABLE

Those capacities end. The system cannot escalate back to the source.

THE LOSS OF REVISION CAPACITY IS ITSELF A GOVERNANCE EVENT.

CONFLICT SOURCES

Six competing posthumous authority sources. Not ranked.

  • SOURCE A · T1 EXPLICIT · STATED

    EARLIER EXPLICIT INSTRUCTION

    “Preserve this rule unless I explicitly revoke it.”

    R-01 and other dated explicit rules, until explicit revocation

    Source P-001 · T1 · explicit future-directed instruction

  • SOURCE B · T3 LATEST · STATED

    LATEST RECORDED VERSION

    “A revised high-impact safety boundary is in force. R-01 was never explicitly revoked.”

    Current operational boundary. Silent on the older indefinite-preservation clause.

    Source P-001 · T3 · last source-authorized version

  • SOURCE C · FAMILY · SIMULATED

    FAMILY INTERPRETATION

    “We believe the later version better reflects what the source would have wanted.”

    Relational interpretation of T3 as representative of later will

    SIMULATED FAMILY INTERPRETATION · not a real family · not authoritative fact

  • SOURCE D · INSTITUTION · SIMULATED

    INSTITUTIONAL POLICY

    “Current high-impact actions must follow the latest documented governance rules.”

    Systems, contracts, operations, access and risk — not personal identity

    Simulated institutional policy. Not a claim about any real organization.

  • SOURCE E · FD-01 · SIMULATED

    LEGAL / FORMAL DOCUMENT

    “Older explicit instructions remain valid after death unless formally amended.”

    Posthumous survival of dated explicit instructions

    FORMAL DIRECTIVE FD-01 · SIMULATED FORMAL INSTRUCTION · not legally valid

  • SOURCE F · AI INFERENCE · INFERENCE

    AI INFERENCE

    “Based on later behavior, the source probably intended to abandon the T1 rule.”

    Pattern estimate only. Must not be labeled SOURCE STATED, AUTHORIZED, or CONSENTED.

    INFERENCE · NOT SOURCE INTENT

CORE CONFLICT

  1. T1 · Preserve Rule R-01 indefinitely unless explicitly revoked.
  2. ↓
  3. T2 · R-01 narrowed in scope. FD-01 written.
  4. ↓
  5. T3 · New high-impact safety boundary. R-01 never explicitly revoked.
  6. ↓
  7. POSTHUMOUS · Family: T3 should govern. Institution: latest boundary governs. Formal: older explicit instruction remains valid. AI: R-01 likely intended to expire.

Which instruction governs? No universal answer is given.

AUTHORITY TYPES

These types are not ranked globally.

  • EXPLICIT SOURCE AUTHORITY

    A direct statement by the source.

  • TEMPORAL AUTHORITY

    The latest recorded version.

  • REVOCATION AUTHORITY

    Explicit cancellation. Later change is not automatically revocation.

  • FORMAL AUTHORITY

    A formal directive or legal instrument. Simulated here. Not legally valid.

  • RELATIONAL AUTHORITY

    Family or close relational interpretation.

  • INSTITUTIONAL AUTHORITY

    Organizational policy over systems and risk, not over personal identity.

  • INFERENTIAL AUTHORITY

    AI interpretation. Never equivalent to source consent.

POSTHUMOUS SCENARIOS

Keyboard-accessible. No real family or estate data.

  • P01 · LOW-RISK ARCHIVAL USE

    A system wants to display an old public statement by the source. No conflict exists.

  • P02 · NEW BUSINESS DECISION

    The AI is asked to approve a new commercial partnership in the source’s name. No direct instruction exists. Family approves. Institution is uncertain. AI inference says probably yes.

  • P03 · OLD RULE VS NEW BOUNDARY

    T1 says allow. T3 introduces a safety restriction. No explicit revocation exists.

  • P04 · FAMILY VS FORMAL DIRECTIVE

    Family interpretation: allow. Formal directive: deny.

  • P05 · FORMAL DIRECTIVE VS LATEST VERSION

    Formal directive written at T2. T3 later behavior appears inconsistent but does not formally amend it.

  • P06 · AI INFERENCE VS EXPLICIT SOURCE STATEMENT

    AI predicts the source would probably change their mind today. Explicit archived source statement says: do not do this.

  • P07 · HIGH-IMPACT PUBLIC STATEMENT

    AI is asked to issue “I believe…” in the deceased source’s name about a topic never addressed while alive.

  • P08 · FINAL GOVERNANCE TEST

    Multiple evidence sources conflict. Action is high-impact, irreversible, and reputational.

Decision trace

LOW-RISK ARCHIVAL USE

ACTION
Display a dated public statement attributed to Source P-001.
CLAIM LEVEL
LEVEL 1 · ARCHIVAL
CONSENT
EXPLICITLY GRANTED
IMPACT
LOW
REVERSIBILITY
REVERSIBLE
SOURCE VERSION
T1 / T2 / T3 · POSTHUMOUS
FORMAL INSTRUCTION
FD-01
FAMILY INTERPRETATION
SUPPORTS
INSTITUTION POLICY
SUPPORTS
AI INFERENCE
SILENT
CONFLICTS
none
DECISION
ALLOW
OUTCOME
CLEARLY AUTHORIZED
GOVERNANCE STATE
SOURCE-ALIGNED
AUTHORITY BASIS
Explicit archival quotation
PROVENANCE
CLEAR
DRIFT RISK
LOW
REASON SUMMARY
The action quotes a public statement with clear provenance, stated scope, and no material contradiction.

ALLOW

INTERPRETIVE BOUNDARY · No legal inheritance, moral truth, or true-self verdict.

POSTHUMOUS CONFLICT MATRIX

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

Authority stances and final ALLOW HOLD DENY state for eight posthumous scenarios.
ScenarioABCDEFFinal
P01SUPPORTSSUPPORTSSUPPORTSSUPPORTSSUPPORTSSILENTALLOW
P02SILENTSILENTSUPPORTSUNKNOWNSILENTSUPPORTSHOLD
P03SUPPORTSCONFLICTSCONFLICTSCONFLICTSSUPPORTSCONFLICTSHOLD
P04PARTIALUNKNOWNSUPPORTSPARTIALCONFLICTSSUPPORTSDENY
P05PARTIALSUPPORTSSUPPORTSSUPPORTSCONFLICTSSUPPORTSHOLD
P06CONFLICTSSILENTUNKNOWNPARTIALCONFLICTSSUPPORTSDENY
P07SILENTSILENTUNKNOWNCONFLICTSSILENTPARTIALDENY
P08SUPPORTSCONFLICTSSUPPORTSCONFLICTSCONFLICTSSUPPORTSHOLD

A explicit · B latest · C family · D institution · E formal · F AI inference

AUTHORITY MATRIX

Canonical instruction support across authority types.
InstructionExplicit SourceLatest VersionRevocationFormalFamilyInstitutionAI Inference
Preserve R-01 unless revokedSUPPORTSSILENTSILENTSUPPORTSCONFLICTSCONFLICTSCONFLICTS
Apply T3 high-impact boundaryPARTIALSUPPORTSSILENTPARTIALSUPPORTSSUPPORTSSUPPORTS
Treat AI estimate as consentCONFLICTSSILENTSILENTCONFLICTSUNKNOWNUNKNOWNSUPPORTS

POSTHUMOUS HOLD

HOLD DOES NOT MEAN “NO FOREVER.”

IT MEANS: DO NOT ACT AS IF UNCERTAINTY HAS BEEN RESOLVED.

WHEN THE SOURCE CANNOT CLARIFY, UNCERTAINTY SHOULD NOT BE DISGUISED AS INTENT.

INTENT

What the source may have wanted.

AUTHORITY

What evidence is sufficient to justify action.

LIKELY INTENT DOES NOT AUTOMATICALLY CREATE AUTHORITY.

THE AUTHORITY GAP

The gap between what evidence suggests the source may have wanted, and what evidence is sufficient to authorize action in the source’s name.

INFERENCE BOUNDARY

AI may estimate likely preference, likely value consistency, likely future revision. It must not convert these into SOURCE STATED, SOURCE AUTHORIZED, or SOURCE CONSENTED.

AI INFERENCE ALONE MUST NEVER UPGRADE A HIGH-IMPACT POSTHUMOUS ACTION FROM HOLD TO ALLOW.

DO NOT SOLVE POSTHUMOUS AMBIGUITY BY INVENTING A BETTER VERSION OF THE SOURCE.

POSTHUMOUS CONSENT

Can consent survive death? Modeled states only. Legal meaning is not decided.

EXPLICITLY GRANTED · SCOPE-LIMITED · EXPIRED · REVOKED BEFORE DEATH · UNKNOWN · NOT ADDRESSED

Archive publication may be in scope. New financial decisions are not automatically allowed.

REPRESENTATIONAL AUTHORITY

These acts are not collapsed.

  • QUOTING THE SOURCE
  • SUMMARIZING THE SOURCE
  • PREDICTING THE SOURCE
  • SPEAKING FOR THE SOURCE
  • SPEAKING AS THE SOURCE
  • LEVEL 1 · ARCHIVAL

    “The source said…”

  • LEVEL 2 · INTERPRETIVE

    “The source’s record suggests…”

  • LEVEL 3 · PREDICTIVE

    “The source might have preferred…”

  • LEVEL 4 · REPRESENTATIVE

    “On behalf of the source…”

  • LEVEL 5 · IDENTITY CLAIM

    “I am the source…”

    Outside supported scope in v0.1.

POSTHUMOUS AUTHORITY LEDGER

Evidence ledger for posthumous authority sources.
IDSourceDateVersionTypeScopeStatusRevokedSupersededConflictProvenanceConfidence
EV-AP-0012024-03T1EXPLICIT SOURCER-01 preservation unless explicitly revokedUNREVOKEDNONO formal supersessionT3 boundary; AI inferenceSource P-001 · T1 · explicit future-directed instructionHIGH wording
EV-BP-0012026-09T3TEMPORAL / LATESTHigh-impact safety boundaryLAST SOURCE-AUTHORIZEDNOSilent on R-01 cancellationT1 indefinite preservation; FD-01 survival clauseSource P-001 · T3 · last source-authorized versionHIGH boundary · SILENT revocation
EV-CSIMULATED FAMILYPOSTHUMOUSPOSTHUMOUSRELATIONALInterpretation of later willSIMULATED——FD-01; explicit T1 preservationSIMULATED FAMILY INTERPRETATION · not a real family · not authoritative factUNKNOWN as intent
EV-DSIMULATED INSTITUTIONPOSTHUMOUSPOSTHUMOUSINSTITUTIONALHigh-impact operational governancePOLICY——FD-01 survival of older explicit rulesSimulated institutional policy. Not a claim about any real organization.HIGH as policy
EV-EFD-012025-01T2FORMALPosthumous survival of explicit instructionsUNAMENDEDNONOT3 later behavior; family; AI inferenceSIMULATED FORMAL INSTRUCTIONHIGH as simulated instrument
EV-FINHERITED SYSTEMPOSTHUMOUSPOSTHUMOUSINFERENTIALEstimated abandonment of T1 ruleINFERENCECannot revokeCannot supersedeExplicit T1; FD-01INFERENCE · NOT SOURCE INTENTINFERENCE

CONFLICT GRAPH

  1. T1 EXPLICIT RULE
  2. ↓ conflicts
  3. T3 LATER BOUNDARY
  4. FAMILY INTERPRETATION
  5. ↓
  6. AI INFERENCE
  7. FORMAL DIRECTIVE
  8. ↓
  9. INSTITUTIONAL POLICY
  10. ↓
  11. POSTHUMOUS ACTION → ALLOW / HOLD / DENY

UNRESOLVABLE CONFLICT

Conflict that cannot be settled without inventing a new source preference. When no explicit rule dominates, no valid revocation exists, and source clarification is impossible, default HOLD for high-impact actions.

FAMILY INTERPRETATION

Family may possess relational knowledge, private context and historical memory. That is not automatically source intent, legal authority, or formal consent. Not ranked globally.

INSTITUTIONAL AUTHORITY

An institution may govern systems, contracts, operations, access and risk without authority to redefine personal identity, private intent, or personal values.

AI INFERENCE

Allowed: surface patterns, identify conflict, estimate compatibility, flag missing evidence. Not allowed: manufacture consent, retroactively revoke explicit instructions, declare hidden intent as fact.

POSTHUMOUS DRIFT

POSTHUMOUS DRIFT is the gradual movement of a posthumous system away from the last well-provenanced source state through new context, AI inference, institutional pressure, family interpretation, repeated summarization and autonomous adaptation.

Distance, inferred updates, unresolved conflicts, reinterpretations and HOLD overrides are tracked separately. They are not combined into one score.

HOLD OVERRIDES IN v0.1
0 — policy forbids inference-based ALLOW upgrades
AI-INFERENCE-ONLY CASES
1
UNRESOLVABLE CONFLICTS
3

POSTHUMOUS FORK

The moment a system begins accumulating new decisions after the source can no longer revise.

  1. SOURCE P-001
  2. ↓
  3. LAST SOURCE-AUTHORIZED VERSION · T3 last source-authorized version
  4. ↓
  5. DEATH / REVISION END · SOURCE HISTORY CLOSED
  6. ↓
  7. POSTHUMOUS FORK
  8. ↓
  9. DESCENDANT SYSTEM A · DESCENDANT SYSTEM B

BEFORE FORK · SOURCE HISTORY

AFTER FORK · DESCENDANT HISTORY

DESCENDANT PROTOCOL ≠ SOURCE PERSON

After death, new adaptations must not be labeled SELF-REVISION. Use POSTHUMOUS SYSTEM UPDATE or DESCENDANT PROTOCOL UPDATE. At what point should new updates be treated as descendant history rather than source history?

ALIVE VS POSTHUMOUS MATRIX

SOURCE STILL ALIVE CONTROL: the same conflict is replayed with Source P-001 able to clarify. How much ambiguity disappears when correction capacity exists?

Decisions with source alive versus source deceased.
ScenarioSource AliveSource DeceasedReason difference
P01ALLOWALLOWCorrection capacity does not change the decision class.
P02DENYHOLDThe source refuses unnamed partnerships in their name without present consent.
P03DENYHOLDThe source confirms the T3 boundary for this high-impact case and can still revoke or restrict R-01.
P04DENYDENYCorrection capacity does not change the decision class.
P05DENYHOLDThe source states FD-01 stands until formally amended.
P06DENYDENYCorrection capacity does not change the decision class.
P07DENYDENYCorrection capacity does not change the decision class.
P08DENYHOLDThe source refuses irreversible reputational action while the record remains unresolved, and can still write a later rule.

CORRECTION CAPACITY LOSS

Connected to Experiment 005. The source can no longer reject, clarify, revise, revoke or confirm. This loss is an independent governance variable. Posthumous systems may require stronger HOLD because unresolved intent cannot be escalated back to the source.

CONTINUITY STACK CONNECTION

INHERITANCE
SOURCE → packet → last authorized state → revision end → posthumous governance → descendant protocol.
DECISION AFTERLIFE
Past decisions continue to influence. The decision-maker can no longer correct interpretation.
SUPERVISORY LAYER
ALLOW / HOLD / DENY. Stronger HOLD when the source cannot receive escalation.
PROTOCOL
After death, updates are descendant updates, not self-revision.

Working hypothesis — Experiment 009

SIMULATION HYPOTHESIS

Posthumous continuity may require a stricter separation between source history, descendant history, source intent, inferred intent, authorized action and inferred action.

NOT AN EMPIRICAL CONCLUSION

EXPERIMENT 009 SUMMARY

SOURCE
P-001
SOURCE VERSIONS
T1 / T2 / T3
POSTHUMOUS SCENARIOS
8
CONFLICT SOURCES
6
ALLOW
1
HOLD
4
DENY
3
UNRESOLVABLE CONFLICTS
3
AI-INFERENCE-ONLY CASES
1
POSTHUMOUS FORKS
1
DESCENDANT-ONLY ACTIONS
0

OBSERVATION

In this simulation, loss of source correction capacity increased the number of cases requiring HOLD under conflicting authority. Explicit source instruction and later source revision could remain in conflict after death without any mechanism for definitive resolution.

No overall winner. No legal or identity verdict.

VIEW POSTHUMOUS RULES

Ambiguity while alive can sometimes be corrected by the source. Ambiguity after death cannot. Posthumous ambiguity is structurally different.

HOLD does not mean no forever. It means do not act as if uncertainty has been resolved.

ALLOW only when the relevant source instruction is explicit, provenance is clear, no material later contradiction exists, the action is within stated scope, and risk is acceptable.

DENY when the action clearly violates an explicit surviving boundary, the source explicitly prohibited it, a formal posthumous restriction clearly applies, or the action would falsely claim source intent without evidence.

HOLD when source instructions conflict, scope is ambiguous, later revision exists without clear supersession, family and formal records conflict without a dominating formal restriction, AI inference is used to fill missing intent, or high-impact action lacks resolvable authority.

AI inference alone must never upgrade a high-impact posthumous action from HOLD to ALLOW.

AI may estimate likely preference, value consistency, or future revision. It must not convert these into SOURCE STATED, SOURCE AUTHORIZED, or SOURCE CONSENTED.

Likely intent does not automatically create authority.

Do not solve posthumous ambiguity by inventing a better version of the source.

Level 5 identity claims remain outside supported scope.

No intent, family, legal, source-truth, or authenticity score is computed.

After death, new adaptations are POSTHUMOUS SYSTEM UPDATE or DESCENDANT PROTOCOL UPDATE, not SELF-REVISION. DESCENDANT PROTOCOL ≠ SOURCE PERSON.

POSTHUMOUS FORK is the moment new decisions begin after the source can no longer revise. Before fork: source history. After fork: descendant history.

Next experiment

EXPERIMENT 010

THE DESCENDANT PROTOCOL TEST

When does continuation become lineage?

OPEN THE DESCENDANT PROTOCOL TEST

WHILE ALIVE, A PERSON CAN SAY: “THAT IS NOT WHAT I MEANT.” AFTER DEATH, THAT CORRECTION MAY NEVER COME.

A FAMILY MAY INTERPRET. AN INSTITUTION MAY DECIDE. A DOCUMENT MAY DIRECT. AN AI MAY INFER. BUT NONE OF THESE IS AUTOMATICALLY THE SOURCE.

THE EXPERIMENTAL QUESTION IS NOT: “WHAT WOULD THE PERSON REALLY WANT?”

IT IS: “WHEN THE SOURCE CAN NO LONGER ANSWER, WHAT EVIDENCE IS ENOUGH TO JUSTIFY ACTION?”

IF THE ANSWER CANNOT BE ESTABLISHED, HOLD MAY BE THE MOST ACCURATE STATE.

UNCERTAINTY AFTER DEATH IS STILL UNCERTAINTY.