a persistence of persistency

LUCID
FABRIC.

Intelligence is temporary. Experience doesn't have to be.

A durable continuity layer for AI systems — preserving evidence, provenance, relationships, knowledge, and history outside any single model or session.

The Problem

Why does this exist?

Intelligence without continuity is a sequence of amnesias. Every context window ends. Every session disappears. Every model, agent, machine, and repository changes. A later agent may retrieve history and still fail to use it correctly — because a record without provenance can preserve a falsehood just as effectively as a truth.

Context windows end. Sessions disappear. Models change. Agents switch. Machines fail. Repositories evolve. History is retrieved but unused. Memory without provenance preserves falsehood.

The problem is not merely storing text. The problem is preserving usable continuity while keeping history, evidence, interpretation, and uncertainty distinguishable.

The Idea

The continuity lifecycle

  1. Experience
  2. Evidence
  3. Canonical
    History
  4. Derived
    Knowledge
  5. Retrieval
  6. Context
  7. Agent
  8. Outcome
  9. New Evidence

Retrieval is not learning. Retrieval is not proof. Derived memory is not raw evidence.

The model does not need to remember everything. The system does.

The Brain

What has actually been accumulated?

0

Ledger Events

0

Sources

0

Blobs

0

Memories

0

Relationships

0

Outcomes

0

Open Contradictions

As of 2026-10-04T01:34:05-04:00 · America/Indianapolis (UTC-4) · a manually versioned, sanitized snapshot of the private brain — not a live query. These numerals are a timestamped illustration, not timeless constants.

How Memory Forms

How does raw history become usable knowledge?

  1. 01 Raw source or evidence enters canonical storage.
  2. 02 Provenance is preserved — where it came from, when, and how.
  3. 03 Synthesis and consolidation may derive higher-level memory.
  4. 04 Derived memory remains epistemically labeled — never silently promoted to fact.
  5. 05 Relationships connect records into a usable graph.
  6. 06 Retrieval selects relevant context for a task.
  7. 07 Outcomes can strengthen, challenge, supersede, or contextualize prior conclusions.
evidence / source inferred memory verified / corroborated contradiction supersession relationship lineage

Not every stored source becomes a memory. Most evidence remains evidence.

One Source of Truth

What prevents the system from turning into inconsistent caches?

Indexes may disappear. The brain must not.

  • Canonical storage is authoritative.
  • The immutable ledger records what happened.
  • Local indexes and search surfaces are disposable derivatives.
  • Remote R2 storage acts as a durable archive / vault.
  • Rebuildability matters more than preserving any particular index.

Provenance

Know why you believe it.

A useful memory should not merely say what the system believes. It should retain enough lineage to explain why — from what evidence, with what confidence, and under what epistemic status. This is a sanitized, synthetic illustration of that lineage.

EVIDENCE

Accepted drill report
“R2-only restore produced a byte-identical brain”

source · raw · immutable
DERIVED · INFERRED/UNVERIFIED

Memory: “R2 restore is byte-identical to the canonical brain”

derived · labeled · never silently promoted
RELATIONSHIP

DERIVED_FROM · CORROBORATES

lineage preserved end to end
OUTCOME · VERIFIED

Accepted compare-brains, 2026-09-27

strengthens prior claim · traceable

Chief · External Agent Access

Can another AI touch the brain without being allowed to manufacture truth?

  • An external agent can read bounded context and provenance.
  • Authorized contributions can be written as evidence.
  • Derived memories created through the Chief interface are constrained to INFERRED / UNVERIFIED.
  • Chief can create RELATED_TO links, but cannot arbitrarily manufacture stronger semantic relationships.
  • R2 durability ACK is checked rather than assumed.

This is epistemic containment — permissions that protect the difference between fact and inference.

The Proof

WE KILLED THE BRAIN.

Then rebuilt it from the archive.

87,204sources → identical
68,764blobs → identical
581memories → identical
2,882relationships → identical
29outcomes → identical
89,121ledger events · ID and hash order identical
100%normalized records byte-identical
0weakened comparisons

The first attempt failed by milliseconds.

The strict first run did not pass byte identity. It exposed 0–2 ms timestamp drift on post-snapshot rows — canonical rows and birth events had been stamped by separate new Date() calls. The team did not weaken the comparator. The write/replay architecture was corrected using single-stamp writes, complete birth payloads, replay consumption, and a regression test. A fresh canonical run was then destroyed and restored again — producing byte-for-byte identity.

We fixed the architecture instead of lowering the bar — then killed it again.

Accepted drill · 2026-09-27 · the Chief artifact and its derived memory survived with INFERRED/UNVERIFIED status and DERIVED_FROM lineage intact. These counts are the historical drill result — not current brain counts.

Coverage CURRENT

What does the brain actually know?

Surviving everything is useful — but how much raw experience has become accessible knowledge? The coverage metric was implemented, measured, and accepted on 2026-09-27 (decision 01M3HNGZ3FBBYZXZRPBM5DMD97, INFERRED/UNVERIFIED). Acceptance is of the metric and its measurement — not of high coverage. At acceptance, direct derivation measured 2,316 of 87,205 source occurrences (2.66%); in the current snapshot it is 4,092 of 87,213 (4.69%) — rising as Wake's canary absorbs eligible evidence. 43,559 eligible-unabsorbed sources remain; and the lineage check still surfaces 29 dangling DERIVED_FROM targets (lineageConsistent=false). Low coverage is reported as low, not hidden.

direct derivation coverage
transitive derivation coverage
graph-connected coverage
unabsorbed evidence
eligible vs excluded / redundant / low-information / not-yet-processed
project-by-project coverage
coverage movement over time

Death/rebirth answers “Can the brain preserve what it knows?” Coverage asks “How much of what it experienced has become usable knowledge?”

Evolution

How did this become what it is now?

Wake PP CURRENT — SHADOW / CANARY

Continuous digestion of raw history into factual structure

New Experience Ingestion Wake Synthesis / Consolidation Factual Memories / Links Retrieval

Wake belongs to factual processing — not synthetic imagination. Implemented (Phase 1 shadow projector + Phase 3 semantic proposals) and running under a canary gate on lucid-fabric since 2026-09-29: every derived memory is forced INFERRED/UNVERIFIED, the grounding verifier and information-value gates hold, and no output can silently pollute canonical truth.

Dream PP EXPERIMENTAL DESIGN

What happens after factual continuity works?

Strict PP asks

“What evidence exists?”

Dream PP asks

“What might be possible?”

Experiment asks

“Can we test it?”

Strict PP records the resulting reality.

A reality firewall

  • Synthetic content lives in an IMAGINED namespace.
  • It remains UNTESTED.
  • It carries confidenceAsFact = 0.
  • Parent lineage is preserved.
  • It never silently contaminates factual canonical truth.

Eight minds are proposed for the current design: PP-Canonical · Associative · Counterfactual · Dream · Adversarial · Divergent · Integrative · Mutator.

The Fabric

What does all of this look like as a connected system?

A conceptual illustration of the connected system — projects as constellations, evidence nodes, derived memories, relationship paths, provenance trails, and accepted milestones. It is decorative: generated from generic shapes, not aggregated from the private brain. No raw private content is involved.

Journal

Follow the work, not the marketing.

A research lab notebook, not a blog. Entries record the hypothesis, what was attempted, what failed, what changed, the evidence, and the next question. Entries are rendered from data/journal.json.

Current State

Where is the project now?