whetstone_DSL/sprint159_plan.md

Sprint 159 Plan: Determinism, Transactions, and Replay Runtimeization

Context

This sprint replaces placeholder logic in replay and transaction tools with stateful deterministic behavior tied to representative language operations.

---

Goals

1. Implement replay suite execution against stored constructive traces
2. Add transaction begin/resume/rollback runtime semantics
3. Compute deterministic gate status from replay and transaction outcomes
4. Emit structured artifacts for divergence and recovery analysis

---

Steps

Step 1829: Multi-language replay corpus runtime index model (10 tests)

Step 1830: Replay comparison and divergence classification runtime model (10 tests)

Step 1831: Constructive transaction ledger runtime model (10 tests)

Step 1832: Resume and rollback policy runtime model (10 tests)

Step 1833: whetstone_run_constructive_replay_suite runtime implementation (8 tests)

Step 1834: whetstone_compare_constructive_replays runtime implementation (8 tests)

Step 1835: whetstone_begin/resume/rollback_constructive_transaction runtime implementation (8 tests)

Step 1836: Determinism and recovery qualification packet model (8 tests)

Step 1837: Replay/transaction reliability report artifact (8 tests)

Step 1838: Sprint 159 integration summary + regression (8 tests)

---

Architecture Gate

• Replay and transaction decisions must be deterministic and auditable
• Rollback must preserve prior consistent state per transaction id
• Divergence output must include machine-readable root-cause classification
• Max 600 lines per header