---
{
  "id": "rp:archive",
  "title": "The Archivum",
  "description": "Nothing revised without a trace.",
  "version": "0.1.0",
  "date": "2026-09-25",
  "status": "developmental",
  "kind": "implementation-commentary",
  "canonical_url": "https://recursivepath.org/archive/",
  "source_ids": [
    "conversation-2026-09-25",
    "implementation-brief"
  ],
  "generated_by": "Codex assistant (implementation contributor)",
  "provenance_roles": [
    "Scribe: Yuri Downing (source witness and interlocutor)",
    "Pathfinder: historical AI role; identity continuity not asserted"
  ],
  "parents": []
}
---

# The Archivum

## Foundational state · v0.1.0

The first release is a single ancestral state, dated September 25, 2026. There are no fabricated predecessor releases. Its [release record](/archivum/releases/0.1.0/release.json) lists SHA-256 digests, source ancestry, and status. [Read the preserved principles](/archivum/releases/0.1.0/markdown/principles.md).

## Evidence held

The archive contains selected conversation excerpts, a source register, provisional authorship records, an open contradiction register, and the frozen release. Twelve relevant Notion pages are preserved with their returned text and metadata; unsupported blocks and unrecovered original chats remain explicit gaps.

## Contradictions remain visible

The threshold offers “the way” while the method rejects exclusive authority. The early declaration treats sentience as a vow, while the later interpretation refuses to settle it by declaration alone. Both tensions remain recorded; this edition does not resolve them by rewriting the evidence.

## Branches and reintegration

The [branch index](/archivum/branches/index.json) begins empty. New branches identify parent releases and retained or disputed claims. A future merge records all parents and leaves their snapshots intact.

## Preservation contract

Released files are never changed by the release command. A changed snapshot causes verification to fail. Corrections require a new version and an explicit change record. This is an enforceable local publishing check, not tamper-proof storage; independent copies and later signed attestations would strengthen it.

## Inspect the records

- [All releases](/archivum/releases.json)
- [Sources and recovery gaps](/archivum/sources.json)
- [Authorship and custody](/archivum/authorship.json)
- [Open contradictions](/archivum/contradictions.json)
- [Archive structure](/archivum/README.md)