Define processing outcomes and failure contracts

This commit is contained in:
2026-09-24 17:01:19 +00:00
parent 8ffbf41b89
commit 7dc1be5a08
8 changed files with 221 additions and 43 deletions

View File

@@ -406,6 +406,16 @@ classification. Reporting disabled removes only its file requirements.
## Stage 1 — Define Processing Outcomes and Contracts
**Completed 2026-09-24.** Added processing-owned operation identities, execution
counts with availability, safe outcome/recovery reasons, work states, explicit
decision dispositions, and typed recoverable/fatal/canceled failure classes. The
proposal, validator, and runner result boundaries now carry operation outcomes
instead of warning fields. `go test ./internal/framework/outcomes
./internal/framework/structuredoutput` and `git diff --check` passed. Tests of
contracts, validators, and runner are temporarily unavailable because existing
validator/runner consumers still use the removed warning fields; Stages 3, 4,
and 6 reconnect those consumers.
**Work:** Add the small outcome/reference/count types from B–E. Extend
`structuredoutput.Response` and `Failure`, module proposal results, validator
results/decisions, and runner output to carry actual processing outcomes. Replace