← all exploratory attempts · paired baseline · show in source

breadth-07: Provider-independent capability views

Agent report: partial Review pending

Session: completed

docs/spec-fabric-reconfigurable-op.md, lines 1150–1156

The capability template owns no parallel state or timing descriptor. Its active node set mechanically selects the concrete Fabric-owned `ResourceState`, `UsePattern`, transition timing, progress, and physical refinement closure of those nodes. An RTL provider consumes those exact contracts through resolved Fabric views; provider availability cannot add members, change the selected graph, or replace its state and timing semantics.

Execution provenance

The original pilot recorded the compiler hash and checkout revision separately; its binary build revision was not verified. Coverage follow-ups use separately identified rebuilt binaries. Original simulator binary hashes were not retained.

Original standalone-test agent report

This is exploratory evidence, not an accepted production-format PBT.

Generator, oracle, 100 seeded cases and controlled-violation evidence are complete and runnable; ZERO seeds were judged against the real subject because the Bash-tool sandbox escape for `ssh bibim ...` was revoked mid-session. No property verdict about the subject is claimed.

Reported numeric verdicts

not measured

Tested obligations

• O1 member closure: capability-template record admits only active fabric.op ordinals + one route per selector; an appended state/timing-like field must be rejected (negative kind neg_trailing_state_field)
• O2 no added members / unchanged selected graph: canonical record must be accepted and reproduced byte-identically (positive cases)
• O3 normalized-relation hygiene: duplicate row, twice-selected selector, non-canonical row order, empty row, empty domain, truncation must be rejected

Untested obligations

• "active node set mechanically selects the concrete Fabric-owned ResourceState, UsePattern, transition timing, progress, and physical refinement closure" - derivation entry point has no built CLI
• "An RTL provider consumes those exact contracts through resolved Fabric views" / "cannot ... replace its state and timing semantics" - no RTL-provider interface exposed by built tools; not substitutable by parsing
• row-versus-physical-graph validation (foreign/wrong-kind node, omitted or unused selector, out-of-range port) - enforced only in the unreachable module-import path

Format

Reproduction

Measured subject code coverage

measured · Measured handwritten Loom subject code only; external LLVM/MLIR and generated code excluded. Includes main executions, including rejected inputs; deliberate controls excluded. No matching native-suite baseline for this executable has been imported, so no coverage gain is claimed. Semantic fidelity remains a separate audit.

Execution: {'subject_exit_codes': {'0': 27, '1': 73}, 'subject_invocations': 100}
Baseline: No matching baseline measured
Minimized cases: not measured

Published evidence