# CI release-evidence manifests `docs/evidence/ci//manifest.json` is generated by `tools/ci/release_evidence.py` (schema `marqdo.release-gates.v1`) and uploaded by the `release-evidence` CI job. Do not hand-edit a manifest into `PASS`. Rules: * every gate records its own `tested_sha`; it must equal `target_sha`; * skipped, cancelled, queued, timed-out, missing or older-SHA jobs are `UNVERIFIED`/`FAIL`, never `PASS`; * `strict_vm` needs a real disposable-VM `strict-evidence.json` (schema `marqdo.strict-evidence.v1`) with `outcome: PASS`, non-root `uid` and the same SHA; a URL alone is not enough; * `performance` needs a `MEASURED` report from the fixed node; TCG/QEMU or development-container numbers are not a baseline; * `release_decision` is `RELEASE_CANDIDATE` only when every required gate is PASS with the same SHA and performance is PASS/WARN. Anything else is `DO_NOT_RELEASE`. The manifest is evidence, not permission to tag; owner approval is separate.