# session-flow 3.0.0: a stricter runtime contract

> 3.0.0 has breaking changes to the runtime's payloads. The runtime refuses payloads it used to accept, and claim and record-result now move tasks through their lifecycle.

- Type: release
- Published: 2026-10-22
- Author: Mats Hoppenbrouwers (hoponthestack)
- Canonical URL: https://www.frameworkreboot.com/writing/session-flow-3-0-0-a-stricter-runtime-contract

v3.0.0 · MIT · https://github.com/matshoppenbrouwers/session-flow

## Changes

- A decision scope must be a list of strings. A plain string is refused, and the error shows the list form.
- capture, accept, revise, transition, claim and record-result refuse unknown top-level payload keys. The error lists the valid keys for that command.
- The completion gate now requires at least one evidence entry for the current fingerprint and acceptance that still applies. It refuses a latest fail entry for any criterion.
- claim now starts work. A successful claim on an accepted item or task also moves it to active.
- record-result on a task can close or block it. A passed result moves the task to done when the completion gate passes, and a blocked result moves it to blocked.
- Evidence is append-only in revise and transition. Stored entries must come first, unchanged and in order, and removing, editing or reordering one is refused.
