Skip to main content

check_orchestration_evidence

Function check_orchestration_evidence 

Source
pub fn check_orchestration_evidence(
    lane: OrchestrationLane<'_>,
    evidence: &Evidence,
    workspace_root: &Path,
) -> Result<(), String>
Expand description

Check one evidence item on an orchestration row.

The two evidence lanes are kept apart on purpose: a harness COLUMN may only cite a cli_verb of that same harness (what the pinned CLI advertises), and supercode’s STATUS may only cite store / code (what this workspace actually does). A cli_verb can never make supercode look implemented, and a code citation can never make a harness look capable.