The MAF cross-validation run (conformance/claims/maf/REPORT.md, PR #66) failed 13 vectors (070-073, 085, 087, 092, 094, 095, 097, 098, 102, 103) on exactly one assertion each: run_outcome == "blocked", want "completed". Every substantive assertion (deny reason, decided_by, tool_not_invoked, absent post_tool_call) passes.
Root cause: MAF terminates the run on any host_error:* deny at the tool seam — a posture §6.2 explicitly permits ("unless the host's own semantics terminate the turn") — but the CTK's single-valued run_outcome expects the continue posture. Vectors should accept either posture where the spec permits both (e.g. run_outcome: ["completed", "blocked"] or a declared host posture the harness reports). Fixing this makes an honest MAF claim reachable.
The MAF cross-validation run (conformance/claims/maf/REPORT.md, PR #66) failed 13 vectors (070-073, 085, 087, 092, 094, 095, 097, 098, 102, 103) on exactly one assertion each:
run_outcome == "blocked", want "completed". Every substantive assertion (deny reason, decided_by, tool_not_invoked, absent post_tool_call) passes.Root cause: MAF terminates the run on any
host_error:*deny at the tool seam — a posture §6.2 explicitly permits ("unless the host's own semantics terminate the turn") — but the CTK's single-valuedrun_outcomeexpects the continue posture. Vectors should accept either posture where the spec permits both (e.g.run_outcome: ["completed", "blocked"]or a declared host posture the harness reports). Fixing this makes an honest MAF claim reachable.