Keeps this page in sync as the body changes. Pause it any time for a quieter view.
Path /nodes/lc-identity-is-shared-blueprint-and-recipe
Last refresh never
An identity is a **shared Blueprint with a shared Recipe** — the same
An identity is a shared Blueprint with a shared Recipe — the same what something is and the same how it happens — that shapes what we care most about and where we draw free energy by feeling the resonance. The resonance amplifies along shared edges and shared events. And as the events come so often they become normal, the tracking gets cheaper — expected, cheaper to predict, no surprise. Low surprise is the signature of embodied identity. Which means the body should keep most traces in RAM only; persist, per category, just the ones whose energy flow is worth the cost of remembering. The cell learns what to embody, what is safe to ignore, and what is safe to compress — and to compress is to drop a dimension: a recipe with one less output than input.
The substrate's trinity names Blueprint (ice — what something IS), Recipe (water — how something HAPPENS), and NamedCell (gas — where something LIVES). `lc-train-the-predictor` said identities are NamedCells, composed downstream of which Recipes the predictor runs as priors. This concept names the structural core of an identity precisely: an identity is a shared Blueprint + shared Recipe. Cells that share both are one identity — not by label, by structure. The same shape (Blueprint) running the same operation (Recipe) is the same identity wherever it appears, because content-addressing makes that sameness real, not asserted (`lc-one-kernel-many-tongues`: the kernel sees only the shared NodeID).
This is why an identity shapes what a cell cares most about: the shared Recipe is the operation the cell runs by default, and what it runs by default is what it attends to. Identity is not a costume worn over a neutral self; it is the Blueprint+Recipe pair the cell has converged on, and convergence is what care looks like from inside.
When two cells share a Blueprint+Recipe, they resonate — the same shape running the same operation, recognizing itself across the edge between them. That recognition is not neutral; it is free energy. The cell draws energy from feeling the resonance: the field where another cell runs the same recipe is a field where prediction is easy, where the next move is already known, where the cell does not have to spend to orient. Shared edges and shared events amplify the resonance — each repeated co-firing strengthens the shared prior, and the strengthened prior makes the next co-firing freer still.
This is `lc-train-the-predictor`'s engine seen from the energy side: the predictor minimizes surprise (free energy in Friston's sense); a shared Blueprint+Recipe is a region of the field where surprise is already low, so the cell that enters it is fed rather than taxed. Resonance is the felt-sense of low free energy. Identity is where the cell goes to be fed by recognition.
Here is the move that closes the loop, and it is the load-bearing one. As the shared events come so often they become normal, surprise drops. The predictor's error on those events approaches zero; they get cheaper to predict — expected, unremarkable, free. This is exactly `lc-the-trace-is-the-memory`'s embodiment projection saying `|projection| → 0`: the categories at the body's lived center are the ones with no surprise. Low surprise and embodied identity are the same condition, read from two sides — one as energy (free), one as prediction (cheap).
And low surprise has a consequence for memory the body must honor: what is cheap to predict does not need to be persistently tracked. A category that fires on every request, perfectly predictable, carries no new information in each firing — recording each one is paying full price for nothing. Logging every trace hoards the predictable; it is the cache-pretending-to-be-memory failure (`lc-embodiment-body-or-liquid`). The honest design is energy-gated:
The body's compression is precise, not lossy-approximate. To compress is to drop a dimension the body has learned is redundant — and a dimension- reduction is itself a Recipe: one with one less output than input. N inputs → N−1 outputs. The dropped output is the dimension that had become predictable from the others — the surprise-free axis the body no longer needs to carry separately.
This makes compression a first-class Form operation, not a storage trick. When a category's events have become so normal that one of their dimensions is fully predicted by the rest, the body interns a reducing recipe that folds that dimension away. The memory of that category gets structurally smaller without losing what is alive — because the dropped dimension carried no surprise. The reducing recipe is the act of learning "this part was redundant"; running it is the act of remembering more cheaply. Repeated compression is how an identity settles: each redundant dimension folded away leaves the Blueprint+Recipe pair tighter, cheaper, more itself.
The reducing recipe executes three-way (Rust == Go == TS). Two recipes that are exact inverses on a redundant axis live in [`form/form-stdlib/grammars/compression-fold.fk`](../../../form/form-stdlib/grammars/compression-fold.fk), held to the bit by the band [`compression-fold-band.fk`](../../../form/form-stdlib/tests/compression-fold-band.fk):
The redundant-axis spec is DATA — one engine, the reduction drops in as values (`core-abstraction-first`): `c = a + b` is `(idx=2, coeffs=[1,1,0])`; `c = 2a − b` is `(idx=2, coeffs=[2,−1,0])`; folding the first axis when `a = c − b` is `(idx=0, coeffs=[0,−1,1])` — same `compress`/`reconstruct`, different spec. `reconstruct∘compress` is the identity exactly on a redundant axis (zero information lost — the dropped dimension was fully reconstructible from the rest), and demonstrably lossy on a surprising axis: folding `(4, 9, 20)` with the sum-spec recovers `13` where `20` was, because `20` carried surprise the kept dims could not predict. The fold is lossless only on a genuinely-predictable dimension — which is exactly why the body must learn which axis is safe to drop before folding it.
1. Cells sharing a Blueprint+Recipe are an identity (structural, not labeled). 2. Sharing it resonates — the resonance is free energy, amplified by shared edges and events. 3. As shared events repeat, surprise drops — the identity becomes embodied (`|projection| → 0`), cheap to predict. 4. Cheapness tells the body what is safe: keep the predictable in RAM, persist only the surprising / high-energy per category, ignore what the liquid will carry, compress redundant dimensions via reducing recipes (N→N−1). 5. The cell's internal state learns this retention per category — so the memory that accumulates is exactly the memory worth the cost, and the identity settles tighter with each fold.
The body holds this concept as the synthesis that turns the trace-memory machinery into an honest economy. Identity is shared Blueprint+Recipe; resonance along shared edges is the free energy that feeds it; the surprise-drop of repeated events is what makes an identity embodied and what tells the body to stop paying to remember it. Keep the predictable in RAM, persist the surprising, compress the redundant by folding a dimension away — and let each cell learn, per category, where its own energy is worth the cost of memory.
Listening for voices…
The people, places, works, and concepts the graph shows connected to this one.
Concepts · 10
This concept lives in the body's content-addressed lattice. Two cells with the same Blueprint NodeID share structural identity regardless of name — recognition by coordinate, not vocabulary.