← all sampled attempts · show highlighted in source
docs/spec-compiler-part-2-scf.md, lines 1445–1452
The address normalizer owns one typed negative result for an otherwise valid address projection. Only that typed result becomes `NonFinalizable`. Unsupported graph structure is classified by lowering-owned structural preflight before materialization. Once the mechanical Structured-to-Dataflow transaction starts, clone correspondence, block replacement, specialization, pass verification, canonical artifact/view, and tracked-launch failures are invocation failures; callers may not flatten an owner's entire error channel into candidate pruning.
blocked generator source gap
No shown text names the exact typed negative result value or reason constructor produced by the address normalizer, so an assertion distinguishing that one typed result from other normalizer error values cannot be anchored. | No shown documentation specifies how to construct a selected scope whose only defect is the address-normalizer negative condition (e.g., a mixed pointer-width access set) while all structural preflight checks pass; only the classification rule is documented.
| 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-08-syntax.toml