← all sampled attempts · show highlighted in source
docs/spec-compiler-part-3-dfg.md, lines 2360–2368
Finalization is failure-atomic. It operates on a private clone of the complete program, validates every canonical graph and the whole-program thread, launch, channel, memory-root, symbol, and completion relations, constructs canonical bytes, invokes the Common finalizer, and publishes only the complete valid Artifact. There is no `is_finalized` operation attribute or partially finalized program state. A valid Common envelope, exact schema descriptor, canonical bytes, and successful independent family verification together define a finalized Artifact.
blocked postcondition observability
No shown text for the Canonical Dataflow family defines the Common envelope contents, the exact schema descriptor bytes, or the canonical semantic byte layout for `loom.canonical_dataflow`, so the claim's 'valid Common envelope, exact schema descriptor, canonical bytes' criterion cannot be checked from the shown text (the Fabric and Structured Program byte formats are other families). | No shown text specifies the failure taxonomy or the required observable state after a failed Canonical Dataflow finalization (what is returned, and that nothing is published), so failure-atomicity is not independently determined for this family.
| input generator | unrun |
|---|---|
| output condition | unrun |
| native evaluation | unrun |
obligation coverage: not measured / no validated evidence · code coverage: not measured / no validated evidence · coverage-preserving minimized case: not measured / no validated evidence
command.json · stderr.txt · stdout.txt · syntax-hashproof.json · anchor-response.request.json · anchor-response.txt · anchoring.json · claim.json · context.json · outline-response.request.json · outline-response.txt · sections.json · breadth-17-syntax.toml