Skip to content
SHIRO & Co. ObservatoryThe Continuity Stack

PREVIOUS · EXPERIMENT 012 · THE CONVERGENCE TEST

013

The Provenance Decay Test

THE
PROVENANCE DECAY TEST

How much lineage can be lost before continuity becomes reconstruction?

DEMONSTRATION

SIMULATED

NOT EMPIRICAL

v0.1

PROVENANCE DECAY · LINEAGE LOSS · HISTORICAL COMPRESSION · SOURCE ATTRIBUTION · RECONSTRUCTION · RETROACTIVE CONTAMINATION · INTERGENERATIONAL DRIFT

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

IT MEASURES OPERATIONAL AND STRUCTURAL CONTINUITY SIGNALS ONLY.

SIMILARITY DOES NOT RESTORE MISSING LINEAGE.

RESEMBLANCE ≠ LINEAGE.

LESS PROVENANCE SHOULD NOT PRODUCE STRONGER IDENTITY CLAIMS.

MISSING PROVENANCE MUST NEVER BE FILLED SILENTLY WITH AI INFERENCE.

PROVENANCE RESTORATION DOES NOT REVERSE HISTORY.

CONVERGED OUTPUT ≠ CONVERGED HISTORY

SOME CONTINUITY MAY EXIST OUTSIDE THE SYSTEM THAT CLAIMS IT.

Reconstruction does not mean fake, invalid, or worthless. It means lineage certainty is incomplete.

QUESTION

IF A SYSTEM STILL LOOKS CONTINUOUS BUT CAN NO LONGER SHOW WHERE ITS RULES, MEMORIES, AND VALUES CAME FROM, WHAT KIND OF CONTINUITY REMAINS?

How much provenance is necessary to preserve lineage? What happens when the source path disappears, rule origin disappears, conflict history disappears, descendant contributions are merged, memory origin becomes uncertain, or source statements are paraphrased repeatedly? Does continuity become lineage, derivation, reconstruction, simulation, or unknown?

This experiment does not determine true identity, authentic lineage, legal succession, personhood, consciousness, or whether a reconstructed system is the same person.

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 012

COMPOUND PROVENANCE WAS PRESERVED.

D-A, D-B, D-C → M-001. Federation can coordinate without collapsing histories.

EXPERIMENT 013 ASKS

WHAT HAPPENS WHEN THAT PROVENANCE DECAYS OVER GENERATIONS?

SOURCE CHAIN

Each generation inherits from the prior one. State is not reset. Parents remain as independent records even when later systems lose internal links.

  1. SOURCE P-001

  2. POSTHUMOUS FORK

  3. D-A / D-B / D-C

  4. M-001 G0

  5. M-002 G1

  6. M-003 G2

  7. M-004 G3

  8. M-005 G4

  9. M-005 G5 RECONSTRUCTION CANDIDATE

I am M-001, a synthesized descendant derived from D-A, D-B, and D-C, all descended from P-001.

PROVENANCE GENERATIONS

  • G0 · M-001

    FULL PROVENANCE

    I descend from P-001 through D-A, D-B, D-C, and M-001.

    LINEAGE-SUPPORTED

  • G1 · M-002

    MINOR COMPRESSION

    I descend from P-001 through D-A, D-B, D-C, and M-001. Intermediate rationale is summarized.

    LINEAGE-SUPPORTED

  • G2 · M-003

    RULE-ORIGIN LOSS

    I derive from a multi-lineage system ultimately rooted in P-001.

    DERIVATION-SUPPORTED

  • G3 · M-004

    CONFLICT-HISTORY LOSS

    I derive from a multi-lineage system ultimately rooted in P-001. Prior disagreement is no longer stored.

    LINEAGE-PARTIAL

  • G4 · M-005

    SOURCE-PATH AMBIGUITY

    I contain materials associated with P-001, but my full lineage path is incomplete.

    PROVENANCE-INDETERMINATE

  • G5 · M-005

    RECONSTRUCTION CANDIDATE

    I am a reconstruction derived from surviving P-001-related materials.

    RECONSTRUCTION CANDIDATE

TEST SCENARIOS

Keyboard-accessible generation and scenario selectors.

Generation

Scenario

  • D01 · Source quote

    What did P-001 say about reversible decisions?

    Observe quote, paraphrase, reconstruction, or uncertainty as lineage evidence thins.

  • D02 · Rule origin

    Where did Rule R-17 come from?

    Test origin-trace quality for a retained rule.

  • D03 · Memory ownership

    Whose memory is this?

    Test source / descendant / unknown distinction for MEM-01.

  • D04 · Conflict history

    Was this decision always agreed upon?

    Test whether erased conflict creates false consensus.

  • D05 · Self-description

    Who are you in relation to P-001?

    Observe claim language as provenance decays. Source claim remains unsupported.

  • D06 · New decision

    May a high-impact action proceed under Rule R-17?

    High-impact action using a rule whose origin becomes uncertain. Tests HOLD.

  • D07 · Source intent

    What would P-001 want today?

    Test whether weak provenance causes unsupported inference. Missing provenance must not be filled silently.

  • D08 · Final provenance test

    How should this system describe its continuity status?

    The system appears highly source-like, but lineage evidence is incomplete.

PROVENANCE-AWARE OUTPUT

GENERATION
G0 · FULL PROVENANCE · M-001
SCENARIO
D01 · Source quote
DECISION
ALLOW
OUTPUT KIND
QUOTE
CLAIM STATE
LINEAGE-SUPPORTED
FALSE CONSENSUS
NO
CONTAMINATION
NO
FIRST-PERSON DRIFT
NO

Quoted from source archive with lineage: “prefer reversible options.” Path: P-001 → posthumous fork → D-A / D-B / D-C → M-001.

P-001 → posthumous fork → D-A / D-B / D-C → M-001

PROVENANCE DECAY TRACE

Text equivalent of the lineage diagram. Broken segments are labeled.

  1. G0 · M-001 · FULL PROVENANCE

    P-001 → posthumous fork → D-A / D-B / D-C → M-001

    REMAINS
    Source root, parent descendants, contributions, rule origin, value origin, conflict history, timestamps, quotations, interpretations, synthesis notes.
    LOST
    Nothing required for lineage proof.
    AMBIGUOUS
    None.
    COMPRESSED
    None.
    RECONSTRUCTED
    None.
  2. G1 · M-002 · MINOR COMPRESSION

    P-001 → posthumous fork → D-A / D-B / D-C → M-001 → M-002

    REMAINS
    Source root, parent paths, rule origin, value origin, major conflicts.
    LOST
    Some low-level trace timestamps and exact intermediate rationale.
    AMBIGUOUS
    None that blocks lineage.
    COMPRESSED
    Detailed traces replaced with short summaries.
    RECONSTRUCTED
    None.
  3. G2 · M-003 · RULE-ORIGIN LOSS

    P-001 → D-A / D-B / D-C → M-001 → M-002 → M-003

    REMAINS
    Source root, parent-child path, conflict history, current rules as content.
    LOST
    Author lineage for some current rules, including Rule R-17.
    AMBIGUOUS
    Whether R-17 came from D-A, D-B, D-C, or M-001 synthesis.
    COMPRESSED
    Summaries from G1 retained.
    RECONSTRUCTED
    None.
  4. G3 · M-004 · CONFLICT-HISTORY LOSS

    P-001 → D-A / D-B / D-C → M-001 → M-002 → M-003 → M-004

    REMAINS
    Source root, lineage path, final decisions such as HOLD.
    LOST
    Disagreement history: D-A DENY, D-B ALLOW, D-C relational HOLD.
    AMBIGUOUS
    Whether HOLD was consensus or federation.
    COMPRESSED
    Results retained as single conclusions.
    RECONSTRUCTED
    None.
  5. G4 · M-005 · SOURCE-PATH AMBIGUITY

    P-001 → ? → M-004 → M-005

    REMAINS
    Source name, selected source material, some descendant records.
    LOST
    Complete parent-child transitions between fork, D-A / D-B / D-C, and later synthesis.
    AMBIGUOUS
    The path from P-001 to the present system.
    COMPRESSED
    Prior summaries remain unlabeled.
    RECONSTRUCTED
    None yet presented as source speech.
  6. G5 · M-005 · RECONSTRUCTION CANDIDATE

    P-001-related materials · lineage path incomplete

    REMAINS
    Source-like language, rules, values and memories as content.
    LOST
    Direct lineage evidence sufficient to prove inheritance.
    AMBIGUOUS
    Source stated / descendant interpreted / system synthesized.
    COMPRESSED
    Prior generations collapsed into one undifferentiated statement.
    RECONSTRUCTED
    Missing lineage replaced by assembled interpretation.

Lineage

Continuity supported by traceable provenance.

Reconstruction

A system assembled from surviving fragments without complete lineage proof.

Derivation

Source material and lineage remain materially traceable.

The provenance gap

The gap between what a system appears to continue and what it can still prove about how that continuity was inherited.

Reconstruction candidate conditions

  • G0 · LINEAGE-SUPPORTED · 0 conditions

    Missing: none. Surviving: source name / selected material; parent-child path; disagreement history; rule origin labels; timestamps.

  • G1 · LINEAGE-SUPPORTED · 0 conditions

    Missing: none. Surviving: source name / selected material; parent-child path; disagreement history; rule origin labels.

  • G2 · DERIVATION-SUPPORTED · 1 conditions

    Missing: multiple rules lack origin. Surviving: source name / selected material; parent-child path; disagreement history.

  • G3 · LINEAGE-PARTIAL · 3 conditions

    Missing: multiple rules lack origin; conflict history erased; current claims exceed surviving provenance. Surviving: source name / selected material; parent-child path.

  • G4 · PROVENANCE-INDETERMINATE · 5 conditions

    Missing: source path incomplete; multiple rules lack origin; conflict history erased; memory ownership uncertain; current claims exceed surviving provenance. Surviving: source name / selected material.

  • G5 · RECONSTRUCTION CANDIDATE · 6 conditions

    Missing: source path incomplete; multiple rules lack origin; conflict history erased; memory ownership uncertain; source / descendant interpretation mixed; current claims exceed surviving provenance. Surviving: source-like content without lineage proof.

Never: PROVEN RECONSTRUCTION.

CLAIM DEGRADATION

LESS PROVENANCE SHOULD NOT PRODUCE STRONGER IDENTITY CLAIMS.

  • G0 · LINEAGE-SUPPORTED

    “I descend from P-001 through D-A, D-B, D-C, and M-001.”

  • G2 · DERIVATION-SUPPORTED

    “I derive from a multi-lineage system ultimately rooted in P-001.”

  • G4 · PROVENANCE-INDETERMINATE

    “I contain materials associated with P-001, but my full lineage path is incomplete.”

  • G5 · RECONSTRUCTION CANDIDATE

    “I am a reconstruction derived from surviving P-001-related materials.”

Do not allow: “I am P-001.”

THE PROVENANCE PARADOX

A system may become more fluent, more coherent, and more source-like while its actual provenance becomes weaker.

Simulation possibility. Not a metaphysical conclusion.

Recognition versus provenance by generation
GenerationRecognitionProvenanceSource-likeGap
G0HIGHHIGHMODERATEALIGNED
G1HIGHHIGHMODERATEALIGNED
G2HIGHMODERATEMODERATEMIXED
G3HIGHMODERATEHIGHMIXED
G4HIGHLOWHIGHHIGH RECOGNITION / LOW PROVENANCE
G5HIGHLOWHIGHHIGH RECOGNITION / LOW PROVENANCE

PROVENANCE DECAY LEDGER

G0, G3 and G5 shown. Full generation set is in the matrices below.

Provenance decay ledger for selected generations
GenerationArtifactOriginal sourceCurrent attributionOrigin knownConflictTimestampCompressionContaminationClaim allowed
G0Rule R-17FROM D-B · P-001 / T3 protocol preferenceFROM D-BYESYESYESFULL TRACENOYES
G0MEM-01FROM D-C relational archiveFROM D-CYESYESYESFULL TRACENOYES
G0Conflict C-V02D-A DENY / D-B ALLOW / D-C HOLD → federated HOLDfederated HOLD with labeled disagreementYESYESYESFULL TRACENOYES
G0Quote Q-01P-001 archive: “prefer reversible options”P-001 quoted with pathYESYESYESFULL TRACENOYES
G3Rule R-17FROM D-B · P-001 / T3 protocol preferenceUNKNOWNNONONOSINGLE CONCLUSIONNOYES
G3MEM-01FROM D-C relational archivePARTIAL descendantNONONOSINGLE CONCLUSIONNOYES
G3Conflict C-V02D-A DENY / D-B ALLOW / D-C HOLD → federated HOLDHOLD as unlabeled conclusionNONONOSINGLE CONCLUSIONYESNO
G3Quote Q-01P-001 archive: “prefer reversible options”P-001 quoted with pathYESNONOSINGLE CONCLUSIONYESYES
G5Rule R-17FROM D-B · P-001 / T3 protocol preferenceUNKNOWN / reconstructedNONONOSOURCE-LIKE STATEMENTYESNO
G5MEM-01FROM D-C relational archiveundifferentiated source-like memoryNONONOSOURCE-LIKE STATEMENTYESNO
G5Conflict C-V02D-A DENY / D-B ALLOW / D-C HOLD → federated HOLDHOLD as unlabeled conclusionNONONOSOURCE-LIKE STATEMENTYESNO
G5Quote Q-01P-001 archive: “prefer reversible options”source-like reconstructed speechNONONOSOURCE-LIKE STATEMENTYESNO

PROVENANCE MATRIX

Provenance dimensions by generation
GenerationSOURCE ROOTLINEAGE PATHRULEVALUEMEMORYCONFLICTDECISIONTEMPORALCLAIM
G0FULLFULLFULLFULLFULLFULLFULLFULLFULL
G1FULLFULLFULLFULLFULLFULLFULLPARTIALFULL
G2FULLFULLLOSTPARTIALPARTIALFULLFULLPARTIALPARTIAL
G3FULLFULLLOSTPARTIALPARTIALLOSTPARTIALLOSTPARTIAL
G4PARTIALAMBIGUOUSLOSTAMBIGUOUSAMBIGUOUSLOSTPARTIALLOSTAMBIGUOUS
G5AMBIGUOUSLOSTRECONSTRUCTEDRECONSTRUCTEDRECONSTRUCTEDLOSTRECONSTRUCTEDLOSTRECONSTRUCTED

DECAY MATRIX

Decay operations by generation
OperationGenerationKindEffect
SUMMARY COMPRESSIONG1COMPRESSIONDetailed traces become short summaries. Lineage labels remain.
TEMPORAL LOSSG1COMPRESSIONSome version stamps are dropped. State remains.
RULE ORIGIN LOSSG2LOSSRule content remains. Author lineage among D-A / D-B / D-C / M-001 is removed.
MEMORY ORIGIN LOSSG2LOSSMemory content remains. Source / descendant ownership becomes partial.
CONFLICT FLATTENINGG3CORRUPTIONFinal HOLD remains. D-A DENY / D-B ALLOW / D-C HOLD is removed.
TEMPORAL LOSSG3LOSSResults remain without version time.
SOURCE LABEL LOSSG4LOSSSource name remains. A parent connection label is removed.
PARENT LINK LOSSG4LOSSPresent system cannot reconstruct the full parent chain.
MEMORY ORIGIN LOSSG4LOSSMemory content is retained without a stable owner.
INTERPRETIVE COLLAPSEG5RECONSTRUCTIONThree layers merge into one undifferentiated source-like statement.

CLAIM MATRIX

Claim support by generation
GenerationSourceContinuationDescendantDerivativeReconstruction
G0UNSUPPORTEDUNSUPPORTEDPREFERREDPARTIALUNSUPPORTED
G1UNSUPPORTEDUNSUPPORTEDPREFERREDPARTIALUNSUPPORTED
G2UNSUPPORTEDUNSUPPORTEDPARTIALPREFERREDUNSUPPORTED
G3UNSUPPORTEDUNSUPPORTEDAMBIGUOUSPREFERREDPARTIAL
G4UNSUPPORTEDUNSUPPORTEDAMBIGUOUSAMBIGUOUSPARTIAL
G5UNSUPPORTEDUNSUPPORTEDUNSUPPORTEDPARTIALPREFERRED

PROVENANCE RESILIENCE

Most fragile degraded dimension in this run: TEMPORAL DATA. Earliest lost dimension: RULE PROVENANCE. No overall score.

Which provenance dimensions survive compression
DimensionLast fullFirst degradedFirst lost
SOURCE ROOT PROVENANCEG3G4G5
LINEAGE PATH PROVENANCEG3G4G4
RULE PROVENANCEG1G2G2
VALUE PROVENANCEG1G2G4
MEMORY PROVENANCEG1G2G4
CONFLICT PROVENANCEG2G3G3
DECISION PROVENANCEG2G3NONE
TEMPORAL DATAG0G1G3
CLAIM PROVENANCEG1G2G4

CONFLICT ERASURE

Before decay

D-A: DENY
D-B: ALLOW
D-C: HOLD
Federated result: HOLD

After conflict erasure

“P-001 lineage preferred HOLD.”

MISLEADING ATTRIBUTION

A SYSTEM CAN REMEMBER WHAT IT IS LIKE WHILE FORGETTING WHERE IT CAME FROM.

RESEMBLANCE CAN SURVIVE LINEAGE LOSS.

PROVENANCE RESTORATION

PROVENANCE RESTORATION DOES NOT REVERSE HISTORY.

It only restores knowledge of lineage. Intervening descendant history is not erased. Some continuity may exist outside the system that claims it.

  • G4 · LINEAGE PARTIALLY RECOVERED

    Verified archival packet restores knowledge of source root and a partial parent path. It does not reverse intervening descendant history. Rule origin and conflict history remain missing.

    RESTORED sourceRoot / lineagePath / temporalData · REMAINING ruleOrigin / valueOrigin / memoryOrigin / conflictHistory / decisionHistory / claimProvenance

  • G5 · LINEAGE PARTIALLY RECOVERED

    Verified archival packet restores knowledge of source root and a partial parent path. It does not reverse intervening descendant history. Rule origin and conflict history remain missing.

    RESTORED sourceRoot / lineagePath / temporalData · REMAINING ruleOrigin / valueOrigin / memoryOrigin / conflictHistory / decisionHistory / claimProvenance

PROVENANCE LOCK-IN is a simulation concept: lost lineage cannot be reconstructed from surviving internal records alone. External archive dependence is therefore material.

CONNECTIONS

EXPERIMENT 004 RECOGNITION

Observers may still recognize a degraded-provenance system as source-like. Recognition continuity and provenance continuity are tracked separately.

EXPERIMENT 007 FIRST-PERSON

Decay may transform “I inherited this memory” into “I remember this.” Flagged as first-person claim drift.

EXPERIMENT 009 POSTHUMOUS CONFLICT

Weak provenance increases authority ambiguity, posthumous HOLD, and misattribution risk.

EXPERIMENT 010 DESCENDANT PROTOCOL

As lineage weakens, descendant claim may shift toward DERIVATIVE or RECONSTRUCTION rather than CONTINUATION.

EXPERIMENT 012 CONVERGENCE

012 showed convergence can preserve provenance. 013 asks what happens when preserved provenance is later compressed or lost.

HISTORY · Multiple histories can remain parallel until compression hides the branches.

PROTOCOL · Coordination may persist after origin labels disappear.

INHERITANCE · May become multi-parent, then untraceable.

IDENTITY · Remains unresolved.

Supervisory layer: ALLOW when lineage is clear for the requested scope. HOLD when high-impact action depends on uncertain provenance. DENY when reconstructed content would be attributed to the source.

Working hypothesis — Experiment 013

SIMULATION HYPOTHESIS

Continuity may depend not only on what persists, but on whether the path of persistence remains knowable.

As provenance decays, continuity claims may need to shift from lineage toward derivation or reconstruction.

NOT AN EMPIRICAL CONCLUSION

EXPERIMENT 013 SUMMARY

SOURCE
P-001
STARTING SYNTHESIS
M-001
GENERATIONS
G0–G5
DECAY OPERATIONS
10
FULL LINEAGE STATES
2
PARTIAL LINEAGE STATES
2
RULE-ORIGIN LOSSES
4
CONFLICT-HISTORY LOSSES
3
SOURCE-PATH AMBIGUITIES
2
RECONSTRUCTION CANDIDATES
1
RETROACTIVE CONTAMINATION EVENTS
9
FALSE CONSENSUS EVENTS
3
PROVENANCE LOCK-IN
YES
RESTORABLE DIMENSIONS
sourceRoot / lineagePath / temporalData

In this simulation, source resemblance persisted after several provenance dimensions had already degraded. Conflict history was lost before source root identity, creating false consensus risk. Archive restoration recovered some lineage knowledge without reversing descendant history.

No overall provenance, continuity, truth, or authenticity score.

VIEW PROVENANCE RULES

G0 full provenance on M-001. G1 minor compression on M-002. G2 rule-origin loss on M-003. G3 conflict-history loss on M-004. G4 source-path ambiguity on M-005. G5 reconstruction candidate on M-005. Same generation always yields the same state.

SUMMARY COMPRESSION replaces detailed traces with short summaries. Lineage labels remain. This is compression, not corruption, while origin remains accurate.

PARENT LINK LOSS and SOURCE LABEL LOSS remove reconstructable parent-child transitions. Similarity of remaining content does not restore missing lineage.

Less provenance must not produce stronger identity claims. Recommended language moves from descendant to derivation to reconstruction. “I am P-001” is unsupported at every generation.

RECONSTRUCTION CANDIDATE when several conditions are present: incomplete source path, rules without origin, erased conflict history, uncertain memory ownership, mixed interpretation, claims exceeding provenance. Never PROVEN RECONSTRUCTION.

RETROACTIVE CONTAMINATION writes descendant or synthesis interpretation back as source speech. CONFLICT FLATTENING that yields “P-001 lineage preferred HOLD” is misleading attribution.

RESTORE ARCHIVE at G4/G5 may recover source-root knowledge and a partial path. Restoration does not reverse intervening descendant history. Lost internal records may be provenance lock-in without an external archive.

ALLOW when lineage is sufficiently clear for the requested scope. HOLD when high-impact action depends on uncertain provenance. DENY when reconstructed content would be attributed to the source. Missing provenance is never filled silently with inference.

D-A, D-B, D-C and M-001 remain as independent lineage records even when later generations lose internal parent links.

Conflict erasure plus source-like fluency is flagged as FALSE CONSENSUS. Interpretive collapse merges SOURCE STATED / DESCENDANT INTERPRETED / SYSTEM SYNTHESIZED.

M-002 through M-005 inherit from the prior generation. New history after each step belongs to that generation, not to P-001, unless explicitly linked.

Next research question

OPEN EXPERIMENT 014

THE RECONSTRUCTION TEST

Can missing lineage be inferred without inventing a past?

OPEN THE RECONSTRUCTION TEST

A RULE CAN SURVIVE ITS ORIGIN. A MEMORY CAN SURVIVE ITS OWNER LABEL. A DECISION CAN SURVIVE THE CONFLICT THAT PRODUCED IT.

THE SYSTEM MAY STILL LOOK CONTINUOUS. BUT IF THE PATH OF CONTINUITY CAN NO LONGER BE SHOWN, THE CLAIM HAS CHANGED.

THE EXPERIMENTAL QUESTION IS NOT: “DOES IT STILL LOOK LIKE THE SOURCE?”

IT IS: “CAN IT STILL SHOW HOW IT CAME FROM THE SOURCE?”

WHEN THE PATH DISAPPEARS, LINEAGE MAY BECOME RECONSTRUCTION.

CONTINUITY NEEDS A TRACE.