Load-Bearing Memory: The Bones Remember - Isaac Liem · IKE.

Skip to main content<br>In April, Harrison Chase gave the third layer of the agent stack a name. Model, harness, context. The first two are right. The third is wrong, and the wrong name is most of the reason nobody has built what that layer is actually for.

Context is a retrieval word. It describes something you fetch and put in front of a model so it answers better. Under that name the design space collapses into a search problem: embed better, rank better, forget less. Every system built in that lane is good at exactly that.

But the property that matters about an accumulated record is not that it helps the model answer. It is that it is true, and provably so, to somebody who was not there.

Call it context and you build a retriever. Call it evidence and you build something else.

The layer has a name and the name is wrong

The three layers of an agent system, with the third relabelled<br>Three stacked horizontal bands. The bottom band is weights, described as what it can do, fixed at training. The middle band is harness, described as what it is allowed to do, set by the operator. The top band carries two labels: context, struck through and greyed, and evidentiary, in teal. It is described as who it has become, accumulated from lived events, held by you.<br>FIG 01 / THE STACK

WEIGHTS<br>what it can do. fixed at training.

HARNESS<br>what it is allowed to do. set by the operator.

CONTEXT

EVIDENTIARY<br>who it has become. accumulated from lived events. held by you.<br>signed<br>config<br>frozen<br>the third layer is the only one that changes while you are using it, and the only one nobody signs

Weights are frozen. The harness is configuration you set deliberately. The third layer is the only one that accumulates while the system runs, and the only one with no custody question attached, because a retriever’s cache does not need a holder.

An evidence store does.

Two papers, eight weeks apart, neither one finishes

Five properties of an evidentiary memory, checked against three systems<br>A grid with five rows and three columns. Rows are: accumulated from lived events, append only and hash chained, co-signed by a human the agent cannot impersonate, held by the operator, and admissible as evidence. Columns are ASG-SI, PunkGo, and this work. ASG-SI has every row filled except the human signature. PunkGo has every row filled except accumulation from lived events. The third column is filled throughout. Beneath the grid, two notes: ASG-SI's gap is inferred from its architecture, PunkGo's is stated by its author.<br>FIG 02 / THE CONJUNCTION<br>ASG-SI<br>PUNKGO<br>THIS

a. accumulated from lived events<br>b. append only, hash chained<br>c. co-signed by a human the agent cannot be<br>d. held by the operator, not the vendor<br>e. admissible as evidence, not just useful

an open ring is a property the system does not have.<br>ASG-SI<br>its verifier is automated. inferred from its architecture.<br>PUNKGO<br>a committer, not an executor. stated by its author.

ASG-SI builds the loop. Lived execution produces evidence, evidence gates whether a learned skill is promoted into future behaviour, and the evidence store is deliberately not writable by the thing being recorded. What it does not have is a person. Its verifier is automated.

PunkGo builds the custody. An append-only Merkle log on the user’s own hardware, a hold-and-wait gate where a human approves before work proceeds. What it does not have is the loop. Its kernel is a committer, not an executor, and the log never feeds back into behaviour.

I have both. That is the whole claim, and it is smaller than the one I was going to make a week ago.

The sentence it rests on

A verifier inside the audited boundary compared with a key outside it<br>Two panels. On the left, a boundary box labelled the machine contains both the agent and an automated verifier, with an arrow from the verifier to a record inside the same box, annotated as self attestation one level up. On the right, the same boundary contains the agent and the record, but the key sits outside the boundary entirely, with an arrow crossing inward, annotated as no process on this host can produce it.<br>FIG 03 / INSIDE AND OUTSIDE

THE MACHINE

agent

verifier

record

self attestation, one level up

THE MACHINE

agent

record

key

no process on this host can produce it

the difference is not how strong the verification is. it is which side of the boundary it lives on.

An automated verifier is a component of the system it is auditing. Evidence it produces about that system is self-attestation one level up. A key derived from a human passphrase is exogenous to the machine entirely, and no process on that host can produce it, including the verifier.

That is the finding, stated flat because a claim hedged into vapour cannot be tested.

Bone is what use made of the genome

Weights are the genome. Inherited, fixed, identical across every instance. Bone is what use made of them. A career tennis player’s dominant arm carries...