Memory and Lineage LabMemory, replay, quarantine, and mutation processor

KELLY sector cognition OS

Lineage microscope

Inspect memory cell ancestry, replay status, mutation history, quarantine state, and the proof that keeps KELLY from regressing.

KELLY memory is not a note pile. A memory cell must carry lineage, proof, settlement, replay, and repair paths before it can safely influence future work.

Postgrescentral spineUse canonical KELLY Neon/Postgres as the durable memory, lineage, replay, court, GraphState receipt, and supersession store.
Evidence shelfimmutable artifactsUse R2/object storage for immutable replay bundles, lineage dossiers, graph snapshots, and receipt archives.
VolumeNo ground-truth volumeNo source-of-truth volume. A local volume is allowed only for graph/cache acceleration that can be rebuilt.
Ask in this labWindow JSONLive pulseGlass proof
live processor windowpublic writes off
01settlementRead closed evidence, hypothesis outcomes, settlement, calibration, and replay results.
02candidateBuild mutation candidates and lineage revision receipts.
03courtRun memory court, canary, replay, quarantine, and GraphState promotion checks.
04influenceExpose accepted, rejected, superseded, quarantined, and pending memory state.

Objects on the bench

memory_cellparent_lineagemutation_candidatequarantine_state

Required receipts

settlement_receiptreplay_receiptrepair_receiptgraphstate_receipt

Live KELLY routes

  • Causalea public lens manifesthttps://www.causalea.com/api/public-lens-apps
  • Glass Lab live snapshothttps://www.causalea.com/api/glass-lab/live-snapshot
  • Advanced Processing Evidence Spinehttps://www.causalea.com/api/advanced-processing/evidence-spine

Lineage microscope

Lineage Lab

Inspect memory cell ancestry, replay status, mutation history, quarantine state, and the proof that keeps KELLY from regressing.

KELLY memory is not a note pile. A memory cell must carry lineage, proof, settlement, replay, and repair paths before it can safely influence future work.

Ask KELLY in this labOpen proof shelfWindow JSON
24 hours

24-hour memory birth watch

Which new eligible memory cell was born from a closed reality loop?

Proof
7-60 days

Lineage mutation audit

Which memory family changed most because reality updated?

Proof
90+ days

Regression immunity

Which memory families have survived contradiction, quarantine, and repair checks?

Proof
What KELLY is doing

This window shows what KELLY is doing in Lineage Lab: what it is reading, what it thinks might matter, what proof exists, and what is still waiting.

How to audit it

Read the answer in this lab first. Open the proof shelf or JSON packet for the evidence behind it. Check the route status and last-checked timestamp before trusting freshness. Look for the mind-changer: the fact that would make KELLY revise the answer. If evidence is waiting, treat the output as a question or watch item, not a settled answer.

Evidence status

Live evidence appears only when KELLY exposes proof-linked sector output. Empty states are intentional waiting states, not filler.

What changes KELLY's mind

New approved evidence, a falsifier, settlement, replay drift, calibration movement, or memory-lineage revision.

What this window cannot do

This lab communicates with KELLY as an inspection window. It cannot write ground truth, memory, GraphState, provider state, or reality receipts.

Processing flow

Memory becomes influence only after replay

01Read closed evidence, hypothesis outcomes, settlement, calibration, and replay results.settlement
02Build mutation candidates and lineage revision receipts.candidate
03Run memory court, canary, replay, quarantine, and GraphState promotion checks.court
04Expose accepted, rejected, superseded, quarantined, and pending memory state.influence

Ask KELLY about this evidence

Replay evidence

Cells, lineage, mutation, quarantine, and repair

connecting

Checking KELLY proof surfaces

This lab renders live proof-linked items when KELLY exposes matching sector evidence.

proof routeswaiting for first check

Sources

Memory inputs

  • governed memory cells
  • replay receipts
  • GraphState lineage where enabled
  • quarantine and repair records
  • settlement and calibration artifacts

Proof standard

How users can tell

  • Every durable cell should be replayable.
  • Lineage must trace backward and forward.
  • Quarantine and repair are visible, not hidden.
  • Memory influence must be bounded and inspectable.

Outputs

Lineage outputs

  • memory_cells
  • lineage_chains
  • mutation_candidates
  • replay_receipts
  • graphstate_promotion_receipts

Storage posture

Postgres: central KELLY spine

Use canonical KELLY Neon/Postgres as the durable memory, lineage, replay, court, GraphState receipt, and supersession store.

Object storage

Immutable evidence shelf

Use R2/object storage for immutable replay bundles, lineage dossiers, graph snapshots, and receipt archives.

Volume

No ground-truth volume

No source-of-truth volume. A local volume is allowed only for graph/cache acceleration that can be rebuilt.

Objects on the bench

Primary objects

  • memory_cell
  • parent_lineage
  • mutation_candidate
  • quarantine_state

Required receipts

Black-box recorder

  • settlement_receipt
  • replay_receipt
  • repair_receipt
  • graphstate_receipt

Authority

Write boundary

  • KELLY is the only write authority for durable learning.
  • Labs are read-only processors and inspection windows.
  • Glass Lab remains the traceable evidence console.
This is a read-only memory inspection interface. Public users cannot directly edit memory, GraphState, or KELLY Prime ground truth. Public users can ask, inspect, export local viewport data where supported, and follow proof links. They cannot edit KELLY Prime ground truth from this app.