← all sampled attempts · show highlighted in source

breadth-10

not activated — no runnable PBT

docs/spec-fabric-boundary.md, lines 14–27

## Direction predicate Every `fabric.boundary` op carries a mandatory `direction` attribute printed/parsed as a bracketed predicate, mirroring `fabric.pe`'s `[spatial|temporal]` style: ```mlir fabric.boundary [s2t] ... fabric.boundary [t2t] ... fabric.boundary [t2s] ... ``` The keyword between `[` and `]` is one of `s2t`, `t2t`, `t2s`. The parser rejects any other keyword.

source passage artifact

Baseline outcome

anchoring schema failed

Production anchoring rejected response: expected passages array. Raw response retained; no exposed anchoring repair or retry.

input generatorunrun
output conditionunrun
native evaluationunrun

Coverage and minimized cases

obligation coverage: not measured / no validated evidence · code coverage: not measured / no validated evidence · coverage-preserving minimized case: not measured / no validated evidence

Retained evidence

evidence (20)

command.json · stderr.txt · stdout.txt · input.mlir · receipt.json · stderr.txt · stdout.mlir · input.mlir · receipt.json · stderr.txt · stdout.mlir · syntax-hashproof.json · anchor-response.request.json · anchor-response.txt · claim.json · context.json · outline-response.request.json · outline-response.txt · sections.json · breadth-10-syntax.toml

execution report (1)

exit.json