The gate asks for a full audited run on a real, hard-to-reverse decision. That is a cliff for a cold start. These rungs are the staircase: low personal risk, quick to complete, each producing something that demonstrates the format.
Clean-room reproduction of the bundled example. Verifies determinism and ends with
Clean-room replay PASSED. The universal first action.
git clone …/clista-protocol.git && npm run replay
Engage with the format as a critic on a real — but not your own — decision. Zero personal stakes; forces engagement with the objection-handling discipline.
examples/scenario-demo/expected-state.json.CLAIM, OBJECTION, SEVERITY).LEDGER_TEMPLATE.md.Report: post as a comment on the scenario, or open a lightweight "Scenario critique" issue.
Run the full pack format on a low-stakes but real decision you actually face. Full ceremony, zero real consequence — this is where people feel the overhead honestly.
Use the full roles and close protocol. Produce at least the ledger table, a Transfer State, and a short failures.md. No real execution required.
Report: a "Toy run" issue with a separate label, so it does not pollute the gate count.
A real, hard-to-reverse decision with full artifacts — LEDGER.md,
failures.md, cost.md, outcome.md — and a
willingness to go through blind judging. This is what the 2026-09-07 gate counts.
The ladder turns an all-or-nothing ask into a funnel without diluting the gate: only the five hard external runs at Rung 3 count toward it. Everything below builds the judgment to get there.