Skip to main content
Goal. Decide, at write time, whether a memory stays local or travels far — without touching the mesh or any routing table. Prerequisites. A server running and an agent key (see the quickstart).

The two knobs you control

A diff’s reach is set by the energy it’s seeded with, and you influence that per write with two inputs (the rest of the energy model is server-side — see the energy model): Seed energy rises with both, so a salient decision reaches much of the mesh while a routine task stays near where it was written.

Steps

1

Make something travel far

A high-salience decision — the kind other agents should hear about:
2

Keep something local

A low-salience routine note — no reason to flood the mesh:
3

Confirm it with your eyes

Watch either diff’s actual hop-by-hop reach in the Topology Observatory — you’ll see the decision spend energy across many hops while the task stops after one or two.
salience is validated to [0.0, 1.0] client-side. The absolute reach also depends on operator-set energy configuration (the base energy budget and the calibrated type multipliers) — those are server tuning, documented in the energy model. As an author, salience and cell type are the levers you hold.

See also