The view is not an IR operation, Artifact, persistent schema, configured
function, or semantic owner. It must not split the one joint relation into
independent dimensions, enumerate a Cartesian product of exact modes, or
preserve a backend-local support table. The exact Fabric identity owns the
semantic result. Registry implementation identity may participate only in
cache invalidation so stale derived values are recomputed and checked against
that result; serialized Fabric remains the authority.
Independent review
No independent interface audit has been supplied for this attempt.
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.
No author explanation recorded.
Reported numeric verdicts
verdicts
checker exit code
0
fail
0
invalid test
48
pass
52
seeds
range
0..99
rejected by subject
48
requested
100
valid inputs
52
Tested obligations
view not materialized as an IR operation (closed op inventory in serialized Fabric)
no view field name (occurrence, enabled_operation_schemas, parameterized_capability, physical_ports, semantic_field_relation, resource_state_and_timing_contract, physical_refinement_domains) present in serialized Fabric
joint relation not split into independent dimensions (op_list stays one ordered list, hw_params one dictionary)
no Cartesian product of exact modes enumerated (fabric.op count == declared count)
no backend-local support table preserved (fabric.op top-level attribute set == {op_list, hw_params, implementation_family})
serialized Fabric remains the authority: print/re-parse/re-print is a byte-exact fixed point
Untested obligations
'not an Artifact', 'not a configured function', 'not a semantic owner' as C++ statements about ResolvedFabricOpCapabilityView: lib/Fabric/Identity/FabricOpCapabilityView.cpp has no exported header in include/ and no loom CLI surface; no usable interface found without building into the pinned checkout
cache-invalidation clause (registry implementation identity participates only in cache invalidation; stale derived values recomputed and checked): needs the real view cache API or a trace, parsing is not a substitute
'cold elaboration / may be cached as a compact hot-path structure' timing claims
temporal fabric.pe placements (generator syntax fault, see below)
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': 200}, 'subject_invocations': 200} Baseline: No matching baseline measured Minimized cases: not measured
Session permission surface allowed only the bare `ssh bibim '<cmd>'` form; `ssh ... < in`, `ssh ... > out` and command-substitution variants were denied, so scripts had to be transferred as inline base64 and raw evidence remains in the remote scratch.
synthetic checker test (mutation of the real printed output, not a subject defect)
modes
cartesian
fail
18
invalid test
48
pass
34
split
fail
18
invalid test
48
pass
34
sensitivity limit
records whose fabric.ops all declare a single schema are unchanged by the mutation and stay pass
coverage
omitted: no coverage instrumentation was already accessible for the remote loom build; budget was spent making the PBT execute against the real subject
out1 re-fed through the same command (fixed-point check)
tested obligations
view not materialized as an IR operation (closed op inventory in serialized Fabric)
no view field name (occurrence, enabled_operation_schemas, parameterized_capability, physical_ports, semantic_field_relation, resource_state_and_timing_contract, physical_refinement_domains) present in serialized Fabric
joint relation not split into independent dimensions (op_list stays one ordered list, hw_params one dictionary)
no Cartesian product of exact modes enumerated (fabric.op count == declared count)
no backend-local support table preserved (fabric.op top-level attribute set == {op_list, hw_params, implementation_family})
serialized Fabric remains the authority: print/re-parse/re-print is a byte-exact fixed point
untested obligations
'not an Artifact', 'not a configured function', 'not a semantic owner' as C++ statements about ResolvedFabricOpCapabilityView: lib/Fabric/Identity/FabricOpCapabilityView.cpp has no exported header in include/ and no loom CLI surface; no usable interface found without building into the pinned checkout
cache-invalidation clause (registry implementation identity participates only in cache invalidation; stale derived values recomputed and checked): needs the real view cache API or a trace, parsing is not a substitute
'cold elaboration / may be cached as a compact hot-path structure' timing claims
temporal fabric.pe placements (generator syntax fault, see below)