Repository navigation
spec(t27os): labs.t27 -- the SETTLE run-state law, the sequence pin, step_name() (Closes #11858) - #11918
Conversation
Summary by t27-beesChecked by the t27 compilert27c parse, parse-complete and typecheck on each changed .t27 file at
Read by the modelThe PR implements the SETTLE step's run-state law ( Worth a look
Read: 2 files, +147 -20, the whole diff. Head |
The SETTLE step's run-state law on top of #11861's wiring:
settle_run_state(BridgeAnswer) -> u8— RUN_OK iff PAY_NORMAL and verified; everything else RUN_FAILED (refusals, coordinator slashes, credited-but-unverified jobs — the ledger's OUT_* alone never decides). The actor reads only the BridgeAnswer.Plus the honest hardening: the sequence pin covers all ten names in order, STEP_FETCH < STEP_PUBLISH < STEP_SETTLE, STEP_SETTLE + 1 == STEP_COUNT, STEP_NAMES.len == 84;
step_name()rewritten from a stub (it named no step) to the per-step pattern.The self-caught defect: the first STEP_NAMES.len pin asserted 82 (miscounted
build-t27c/build-t27bas 9 bytes; they are 10) — the test failed and caught it, fixed to 84. The pin working as designed.10/10 tests, 0 FAIL, 0 vacuous; sealed (spec_hash sha256:859ec30c…, all hashes MATCH). Imports: SB_REFUSE_VERIFICATIONS, V_WRONG_RESULT, PAY_SLASH_ONLY. NOT CLAIMED: no mTRI moved, the amounts are the payout law's, the receipt signing is t27c corpus-receipt's.
phi^2 + 1/phi^2 = 3 | TRINITY