Goal Evidence Ledger

Goal Evidence Ledger

Contract

Iron law: no AC transitions to pass without a FlowEvidence sidecar whose proves: [<AC.id>] names it, and every non-trivial sidecar declares what it does NOT prove. Invoked by goal-evaluator (Step 2, once per verification command), by /flow:start Phase 4 and /flow:address (verification-evidence sidecars on the FlowRun), and by /flow:goal evaluate for judge reports. Inputs: evidence id, type, proves list, and optional command, exit code, raw-output path, limitations, negative cases. Returns the sidecar path, which the caller sets as the AC's evidence_ref. Permitted skips: limitations on holdout_validation and verdict types; the raw .txt when nothing was captured. The helper is never skipped.

Inputs

1. Evidence id — evidence-<AC.id>-<descriptor>-<turn>; lowercase, digits, _-.
2. Evidence type — one of evidence.schema.json's enum: command_result, test_result, lint_result, runtime_smoke_result, visual_result, git_diff, holdout_validation, verdict, human_approval, review_comment_snapshot, ci_status, llm_judge_report, artifact_check, path_boundary_check.
3. Proves — AC ids this evidence supports.
4. Optional: command, exit_code, raw output path, limitations, negative_cases.

Outputs

1. .flow/runs/<run-id>/evidence/<evidence-id>.evidence.yaml (schema plugins/flow/schemas/v1/evidence.schema.json).
2. .flow/runs/<run-id>/evidence/<evidence-id>.txt — raw stdout/stderr when captured.
3. An evidence-captured journal artifact.
4. One line appended to .flow/runs/<run-id>/events.jsonl.

Workflow

Step 1: Compose

apiVersion: flow.synapti.ai/v1
kind: FlowEvidence
metadata:
  id: <evidence-id>
  goal: <goal-id>
  run_id: <run-id>
  activity_id: <activity-id, if any>
  created_at: <ISO-8601 UTC>
evidence:
  type: <enum-value>
  command: <bash command, if applicable>
  exit_code: <captured, if command type>
  output_ref: <relative path to .txt, if captured>
  proves:
    - <AC.id>
  limitations:
    - <what this evidence does NOT prove>
  negative_cases:
    - <adversarial or boundary cases exercised>

Step 2: Negative space

The schema rejects a command_result without limitations at write time.

Step 3: Write

bin/flow-record-evidence.sh --run-id <run-id> --evidence-file <composed.yaml> [--raw-output <stdout-capture>]

The helper writes atomically (tempfile + rename via _journal_atomic.py), refuses symlinked targets and lockfiles, validates the schema when jsonschema is installed, and copies the raw output next to the sidecar. Surface any non-zero exit with its stderr.

Step 4: Journal

bin/journal-record.sh --issue {N} --type evidence-captured --metadata evidence_id=<id> --metadata goal_id=<goal-id> --metadata proves=<comma-list of AC ids>

Step 5: Link

The caller updates the AC in .flow/goals/<id>.goal.yaml: status: evidence_collected, evidence_ref: .flow/runs/<run-id>/evidence/<evidence-id>.evidence.yaml, last_evaluated_at: <now>.

Rules

• Evidence is append-only: a correction is a new sidecar (evidence-AC1-retest-turn2) and the AC's evidence_ref moves to it; the old sidecar stays as audit trail.
• One run proving two ACs is one sidecar with proves: [AC1, AC2].
• Capture evidence before the verdict; never after the goal is achieved.
• Never write a sidecar with echo >; the helper is the only writer.

References

• plugins/flow/skills/evidence-based-development/SKILL.md — the ASSERTION/EVIDENCE/VERIFIED discipline this ledger materializes.
• plugins/flow/references/evidence-bundle-format.md — the bundle layout the judge consumes.