zara-coding: any current verifier failure must block completion #150

New issue

Closed

opened 2026-09-08 02:03:05 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-08 02:03:05 +00:00

Owner

Problem

After #280, the latest result is authoritative within each verifier kind, but task completion still succeeds if any verifier kind is currently passing. Example: latest test=passed plus latest build=failed can still complete because the passing test kind satisfies passing_evidence/1.

Required behavior

deterministic RED proving a current failure in any verifier kind blocks completion even when another kind passes;
use the latest result per verifier kind;
require at least one verifier result and no current verifier failures for completion;
retain historical evidence for auditability;
preserve verifier-owned evidence trust boundary;
plugin/registry/Nix/package gates green.

This advances #1 and closes the cross-kind false-green left after #280.

## Problem After #280, the latest result is authoritative within each verifier kind, but task completion still succeeds if *any* verifier kind is currently passing. Example: latest `test=passed` plus latest `build=failed` can still complete because the passing test kind satisfies `passing_evidence/1`. ## Required behavior - deterministic RED proving a current failure in any verifier kind blocks completion even when another kind passes; - use the latest result per verifier kind; - require at least one verifier result and no current verifier failures for completion; - retain historical evidence for auditability; - preserve verifier-owned evidence trust boundary; - plugin/registry/Nix/package gates green. This advances #1 and closes the cross-kind false-green left after #280.

nsaspy closed this issue

2026-09-08 02:03:05 +00:00