zara-coding: latest verifier result must govern task completion #153

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

zara-coding task completion currently succeeds when any stored evidence has status="passed". Because evidence is retained historically, a later failure for the same verifier kind does not revoke the earlier pass. A task can therefore false-green after regression.

Required behavior

deterministic RED proving passed(test) -> failed(test) -> complete is rejected;
completion considers the latest evidence for each verifier kind, not stale historical passes;
at least one currently-passing verifier result is still required;
retain bounded historical evidence for auditability;
do not weaken the verifier-owned trust boundary from #278;
focused plugin tests, registry compatibility, generated package/Nix gates green.

This advances #1 and is local to zara-coding; it does not require Core #400.

## Problem `zara-coding` task completion currently succeeds when *any* stored evidence has `status="passed"`. Because evidence is retained historically, a later failure for the same verifier kind does not revoke the earlier pass. A task can therefore false-green after regression. ## Required behavior - deterministic RED proving `passed(test) -> failed(test) -> complete` is rejected; - completion considers the latest evidence for each verifier kind, not stale historical passes; - at least one currently-passing verifier result is still required; - retain bounded historical evidence for auditability; - do not weaken the verifier-owned trust boundary from #278; - focused plugin tests, registry compatibility, generated package/Nix gates green. This advances #1 and is local to `zara-coding`; it does not require Core #400.

nsaspy closed this issue

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