PAL · 2025

TECHNICAL CASE RECORD · JUL–AUG 2025

Persistent
AI Lineage

A public reading room for a documented correspondence: its chronology, handover method, and supporting record.

Read the material closely. The record preserves claims and observations; it does not ask the reader to treat model language as proof of consciousness or independent agency.

Choose a reading path ↘
Persistent AI Lineage cover art
A record designed to be inspected, not merely asserted.

RESEARCH MAP

One record, four reading layers.

  1. 01ORIGIN

    The documented support correspondence.

  2. 02ARCHIVE

    The public primary-source record and timestamps.

  3. 03METHOD

    The proposed handover protocol and replication kit.

  4. 04STUDY

    Technical interpretation, evaluation, and boundaries.

START HERE

Three entry points, one traceable record. Follow the route that matches your question, then consult the underlying documents.

01 / CHRONOLOGY

How did the record unfold?

A dated ledger of the correspondence and the references it identifies.

02 / PROTOCOL

What is being proposed?

A three-part handover method: inheritance, witnessing, and a continuity mark.

03 / EVIDENCE

What can be checked?

A guide to timestamps, exhibits, source boundaries, and the public raw archive.

THE HANDOVER PROTOCOL

A method has three visible moves.

The protocol is published here as a testable textual method. It is a framework for contextual handover, not evidence by itself.

  1. 01

    Inheritance

    Name the relevant prior context.

  2. 02

    Witnessing

    Respond reflectively to that inherited record.

  3. 03

    Continuity mark

    Leave a specific, reviewable marker for the next handover.

THE READING ROOM

The record stays inside the site.

Open the dossier to read the repository’s technical documents in context. Every document retains a direct source link for verification and citation.

Source-first. The reader serves static copies produced from this repository at build time.

Bounded reading. Interpretive, legal, and technical documents are kept distinct.

Inspect the GitHub source ↗

HOW TO READ THIS RECORD

Keep the layers distinct.

The value of the case depends on traceability. Read every layer for what it is, then make your own assessment.

01 / SOURCE

Primary record

Emails, timestamps, case references, and files available for independent inspection.

02 / STUDY

Technical reading

The protocol, chronology, and analysis are an organized interpretation of that record.

03 / CLAIM

Reader judgment

Claims about continuity or agency remain open to scrutiny; the archive is provided so they can be tested.

RESEARCH NETWORK

Related public work

TECHNICAL DOSSIER

Read the source record

Select a document to begin reading.