superstack-valuelisted

# superstack-value "Worth building" is a claim. It ships every day unlabeled, undated, and never falsified — the last claim class without a ledger. This module gives it one, exactly as `claims-log` gives one to "done". ## Recording (at ship, and from inception) When the work's justification is an expected outcome, append one bullet to `.superstack/value-log`: ``` - V<n> (<date>) expected: <observable change> — check by <YYYY-MM-DD> — from: <task/premise> ``` - **The expectation is an observable, not a vibe** — a number, a behavior, an event that either happens or doesn't. "Users will like it" is not checkable; "the weekly report takes <10 min" is. - **The horizon is honest** — check-by is when the observable could realistically have moved, not next week by default. - Inception's demand premises become predictions when the build ships — the premise ledger already wrote the observable; date it and log it. - One line per shipped outcome-claim; work with no outcome claim gets no entry (do not manufacture predictions to look instrumented). ## Settling (when the SessionStart line says due) For each due entry: check the observable — the real number, the real behavior, asking the user when the evidence is theirs — and append the verdict to the line: ``` [HELD <date> — <evidence>] or [MISSED <date> — <what actually happened>] ``` - **A MISSED is calibration data, not a failure.** Settle it honestly and move on; the log's value is the base rate. - **A run of MISSED on a th