KELLY live pulserefreshed agolearninglifetime heartbeat 0browser pulses warmingcells 0replay-ready 0engine checkinglatest cell watchingevidence checkinglive memory laneloop: checking live activity
activity feed
KELLY cognition organ

Memory and Lineage Lab

KELLY's durable memory, revision, replay, GraphState, and mutation-receipt organ.

Shows how closed evidence becomes memory, how old cells are revised by reality, and how GraphState promotions earn durable lineage receipts.

real timeGlass Lab sourcedread-only window
Real-time cognition window

Samples Glass Lab, Advanced Processing Evidence Spine, and the lab-specific runtime routes every 15 seconds.

Glass Lab sourceReceiptspublic writes blocked

Glass panels

0/3

Snapshot

0/?

Routes

linked

Refresh

15s

Glass Lab source panels
graphstate memory mappending
graphstate promotion bridgepending
advanced processing evidence spinepending
Runtime route checks

This lab uses anchored Glass Lab proof routes only.

Latest snapshot: pending. Evidence spine: pending. KELLY is the only write authority. The lab is an operator-grade read window over governed internal writes.

Cognition workbench

This is the sector-specific operating view for Memory/Lineage: gauges, receipt queue, closure timeline, topology, and empty-state behavior. Live route health remains in the real-time panel above.

operator grade

Cell lineage

birth-to-root

Every cell should expose origin, parent, child, replay, and proof links.

Replay posture

inspect before trust

Memory is not healthy unless the receipt chain can be reconstructed.

Mutation queue

proposal first

Reality changes create candidates; court and replay decide whether they are accepted.

GraphState receipts

dry-run / apply / replay

Graph mutations need durable receipts that survive deploys and can be audited.

Receipt queue

The queue is a receipt path, not a claim of hidden live data.

traceable

Lineage and closure timeline

1

Old cell

loaded

Start with an existing memory and lineage edge.

2

New reality

settled

Attach outcome evidence that changes pressure.

3

Mutation

proposed

Create accept, reject, supersede, or quarantine candidate.

4

Replay

required

Rebuild the receipt chain before acceptance.

5

Graph

receipted

Apply only through governed GraphState receipts.

Cognitive topology

Root cell

Original memory cell and authority path.

Lineage edge

Parent, child, supersession, or repair relationship.

Replay receipt

Reconstructable proof chain.

Court decision

Accepted, rejected, quarantined, or superseded.

GraphState

Durable promotion edge and receipt continuity.

Viewport empty-state contract

No memory cell selected

If no cell is selected, the lab should show lineage health and replay queues, not a blank graph or invented ancestry.

Open memory lineage

Live inputs

Closed evidence, hypothesis outcomes, calibration, settlement, replay, and mutation candidates.
GraphState promotion receipts and memory court proposal lifecycle state.
Autonomous learning cells, canary receipts, and lineage continuity events.

Active objects

Memory cells
Revision candidates
Lineage chains
GraphState promotion receipts
Replay and quarantine state

Receipts

Cell birth receipts
Replay receipts
Mutation proposal receipts
GraphState dry-run/apply receipts
Supersession and quarantine receipts

Closure status

A memory object closes when evidence, replay, court posture, lineage edge, and mutation decision are visible.
Accepted revisions must remain traceable to the old cell, new reality, and replay result.

Automation loop

Continuously follows the closed-loop memory path from evidence to replay to durable lineage.

cognition pipeline

step 1

Read closed evidence, hypothesis outcomes, calibration, and replay results.

step 2

Build mutation candidates and lineage revision receipts.

step 3

Run memory court, canary, replay, and GraphState promotion checks.

step 4

Expose accepted, rejected, quarantined, superseded, and pending memory state.

Glass Lab source

These are the full proof windows this lab samples into the one-page view.

Storage posture

Postgres

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

Object store

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

Volume

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

Runtime routes

Lab functions stay simple on this page; deeper receipts open in the exact runtime or Glass Lab window.

operator links