Warden plan
tier: hermetic requires: []
Pending stub — GATED criterion. The precondition below is not built; this plan reports the criterion as pending (skip, never fail) until it lands. When it does, replace this stub with a real plan in the shape of
25-cr-18/26-cr-25/27-cr-20.
Register: ~/.studio/master.withrobin.ai/project/rfc.one/criteria-register.md (status there: PENDING OWNER ACCEPTANCE; accepted by the 2026-08-31 proxy screen).
### CR-26 — Live-artifact staleness and stamp coverage - Statement: The stamp-and-lazy-re-render machinery keeps live artifacts within one batch interval of the knowledge they project. - Metric: Staleness rate — fraction of live-artifact reads serving a version that cites a Claim whose standing dropped, or a Signal whose support dropped, more than Δ plus one render time earlier without re-rendering. Stamp coverage — fraction of wikis and live artifacts citing a changed object that carry the stamp within Δ plus the batch's processing time, computed separately for the four sources: propagation (injected contradictions), user rejection, supersession, cited-Signal support withdrawal. Re-renders per artifact per checkpoint (the thrash measure the debounce bounds); mean re-render cost as a new ledger line (rendering stages only — a re-render runs no derivation, so the line is disjoint from the anchor's W(m) and adds no writes). - Dataset/inputs: The anchor's §10.5 injected replay series, extended: 10 pinned live artifacts per workspace at m = 10, each citing ≥5 accepted Claims and ≥3 Signals that justify no Claim (the deployed norm the §3.2 Signal hook exists for); contradiction set constructed to include targets cited by pinned artifacts; reads of pinned artifacts replayed between checkpoints; an added checkpoint at m = 15 — for ten pinned-artifact citation targets per workspace, 5 user rejections and 5 explicit supersessions through ordinary write paths, plus withdrawal of the source Entries behind 10 cited Signals per workspace that justify no Claim (a support drop with no Claim standing moving). Artifact requests run the anchor's full slow path unchanged; the experiment adds rendering-side machinery only. - Threshold: Staleness below 2% at every measurable checkpoint (mirroring the anchor's bar); stamp coverage 100% on each of the four sources (construction guarantee — the stamp rides standing and support writes; a miss names the write path that skipped the hook); re-renders ≤1 per artifact per interval (debounce guarantee). - Drop condition: If staleness cannot be held under lazy or eager (stamp-time re-render for artifacts above a read-frequency threshold, cost difference charged to the ledger) policy, the live family is cut to terminal — artifacts regenerated on demand and never advertised as current. - Source: Companion §11.4 (mechanism in §3.2 and §7; falsifier pointer at §7's close). - Tier: gated — requires the artifact engine, the Claim layer, and the replay harness.
Precondition: requires the artifact engine, the Claim layer, and the replay harness. Not built at HEAD 7f379974 (verified 2026-08-31: no 'claims', 'dimensions', or 'initiatives' tables in server/src/db/schema.ts, and no conflicts_with edges anywhere in server/src or packages/). The artifact engine and the replay harness have no code marker to probe.
set -uo pipefail
source "$WARDEN_LIB/assert.sh"
cd "${PROJECT_ROOT:-$(git rev-parse --show-toplevel)}"
SCHEMA=server/src/db/schema.ts
MISSING=""
grep -q "'claims'" "$SCHEMA" || MISSING="$MISSING claims-tables"
if [ -n "$MISSING" ]; then
warden_skip "CR-26 — Live-artifact staleness and stamp coverage" "pending: requires the artifact engine, the Claim layer, and the replay harness — gated criterion, precondition not built (probes missing:$MISSING)"
else
warden_skip "CR-26 — Live-artifact staleness and stamp coverage" "schema probes now pass — upgrade this pending stub to a real plan before CR-26 can bind (probes are heuristic, not proof)"
fiPending stub, hermetic on purpose: the guard reads the checkout only and emits skip in every branch, so this plan can never red a run — the criterion surfaces in every summary as pending with its precondition named. The probes are heuristic activation bells, not proof: quoted table names (and conflicts_with where the contradiction check is a precondition) flip the detail text when the machinery lands. The real plan must quote the criterion verbatim, turn its thresholds into warden_pass/warden_fail gates, and follow the conventions the three runnable plans set: machine-local fixtures (25-cr-18), NLI probe and versioned judge prompts (26-cr-25), data-keyed guard activation (27-cr-20).