Example
Bounded Interleaving Verification for Bosatsu State Machines
Declare a state machine's properties first, then read the checker's verdict for every interleaving of your handlers. How to read the versioned evidence.
Every verdict below is regenerated from the sources shown on each deploy. The three scenarios follow one submission lifecycle, and every property bottoms out in its can_transition.
submission.bosatsu: the domain FSM (can_transition, is_terminal)
loading…
How to read a verdict
| Verdict | Meaning within the declared model and bound |
|---|---|
| holds | True at every step of every explored interleaving, with 0 truncated. |
| violated | Some interleaving makes it false. A trace is attached. |
| inconclusive | The checker refused to answer, and says why. |
In headings, mixed means the cards disagree and the command exits nonzero, and interactive marks the section you can run.
Trace steps print in run order, but each #N is the operation's place in the program, so numbers can appear out of sequence.
The bound counts every operation on the cell, and reads count too. Past it, cases are truncated and the verdict is inconclusive. --max-ops N changes it, up to 8.
A stale-read: card appears only when a property survives atomic steps but breaks under read capture, so only-legal-steps has one and terminal-is-final does not.
A violated declared property always exits nonzero. The built-in causal-consistency and race-free:<cell> cards never gate.
1. Day 0: spec first, no handlers yet (inconclusive)
The spec declares two operations and two step-properties before any handler exists.
yichus spec domain/submission.bosatsu specs/submission.spec.bosatsu --output verdicts.jsonsubmission.spec.bosatsu: the spec (guarded model + properties)
loading…
Loading verdicts…
2. Unguarded handlers: violated, with a trace
Three handlers write their target state unconditionally. The second trace resurrects an Archived submission.
yichus spec domain/submission.bosatsu specs/submission_unchecked.spec.bosatsu fixtures/intake_handlers_unchecked.bosatsu --output verdicts.json
# exit 1intake_handlers_unchecked.bosatsu: the handlers
loading…
submission_unchecked.spec.bosatsu: the spec (models the handlers as written, as constant setters)
loading…
Loading verdicts…
3. Guarded handlers: mixed result, declared properties hold, a stale read still gates
The guarded handlers make both declared properties hold, yet the command still exits nonzero: stale-read:only-legal-steps is violated.
yichus spec domain/submission.bosatsu specs/submission.spec.bosatsu fixtures/intake_handlers_guarded.bosatsu --output verdicts.json --require-holds only-legal-steps,terminal-is-final
# exit 1 — only-legal-steps and terminal-is-final hold, but stale-read:only-legal-steps is violatedintake_handlers_guarded.bosatsu: the handlers
loading…
Loading verdicts…
race-free card still flags the race on submission_state; generic races and property violations are different questions.Run the checker in your browser (interactive)
A door must be unlocked before it opens, and force_open skips the check. Check it, then edit and check again.
- Guard
force_openand its model step, and the verdict flips to holds. - A stale-read:only-legal-moves card stays violated.
- Delete a handler or a
Transitionrow to see inconclusive.
door_spec.bosatsu: the spec
Work with your agent
WebMCP connects your agent to this page. Connection and tool instructions. Use yichus_page_feedback to read the current editor and displayed feedback. The agent can use yichus_page_edit to update the current source and yichus_page_action to run a listed button, then read feedback for completion and diagnostics. Autocomplete suggestions remain available for you to accept with Tab.
door_handlers.bosatsu: the handlers
door.bosatsu: the domain FSM
These editors support agent autocomplete over WebMCP: pause typing or press Ctrl+Space, then Tab to accept the suggestion.
Typed-IR extraction, declared transition binding, and soundness limits
The checker reads IO operations and their order from typed IR, but the link from an operation to its Transition row is declared, not yet verified (modelBinding: declared-only).
Raw artifacts: day 0, unguarded violation, guarded mixed result.
Ask your agent about anything here; it has the detail.
Where this fits
What this is about: Checks and Proofs