# Eve charter-completeness gate preparation — 2026-09

Task 12.8 now has a fail-closed composition gate over the ratified Task 0.8
charter inventory and the Task 0.6 gap/task/evidence/exit matrix. The production
candidate binds those records by content hash, indexes all 205 task rows in
matrix order, indexes any execution manifest found at each task's exact required
path, recomputes the separate Task 12.7 family-release report, and admits only
canonical workflow acceptance receipts from the 6,626-workflow denominator.

The gate does not infer delivery from a checked box or from source coverage.
Every completed ledger task needs a current, semantically valid evidence
manifest; every admission dependency must itself be complete; and every required
workflow owned by a task must pass the existing signed-runtime receipt verifier.
That verifier checks real outputs, negative and recovery cases, runtime
provenance, content-hashed artifacts, scorecard measurements, accountable human
decisions, and an execution-independent review against the host-admin trust
policy. The charter gate separately requires a current 17-outcome result record
with the exact preregistered targets and floors, complete strata, sufficient
independent units, content-hashed measurement evidence, and current validation
for every judge actually used.

Statuses are derived upward from the admitted evidence. The report carries the
exact blocked workflow IDs and invalid task-manifest diagnostics, derives all
205 task statuses, all 19 phase statuses, V1–V10 release status, G1–G18 status,
and then initiative and charter status. A gap closes only when it has explicit
closed evidence and every task owning it is complete; an open, blocked,
accepted, deferred, or successor gap remains a blocker. Charter completion also
requires a freshly recomputed passing Task 12.7 decision, every scorecard target
and floor, every task, every workflow, every phase and every release, with zero
refusals or limitations.

Gate capability is deliberately reported separately from charter status. The
real CLI's isolated `--contract-test` mode is restricted to release IDs prefixed
`contract-fixture-` and is the only mode that permits an alternate evidence
root. Through that CLI, the focused suite proves one complete green fixture and
observes red for a missing workflow, an unadmitted workflow, stale source, stale
execution evidence, weak workflow proof, incomplete strata, a blocked
dependency, an unvalidated judge, a failed target, a stale content digest, and
accepted/deferred/successor gaps. These ephemeral fixtures exercise gate
composition; they are never written into the production evidence tree and cannot
become charter admission.

The retained production report is honestly blocked. It derives 0 of 205 tasks, 0
of 19 phases, 0 of 10 releases, 0 of 6,626 required workflows, and 0 of 18 gaps
complete. Task 12.7 is blocked, no 17-outcome result artifact exists, 13
completed ledger tasks have no manifest at their required path, and 34 supplied
completed-task manifests are stale because one or more retained artifact hashes
no longer match the current tree. The report preserves every stale-artifact
diagnostic and all exact blocked workflow IDs. No production receipt, scorecard
measurement, human decision, or completion claim was synthesized.

Run the current production decision with:

```bash
node tools/eve-everywhere/evaluate-charter-completeness-gate.mjs \
  --output=docs/audits/eve-sota-charter-completeness-gate/2026-09-13.report.json
```

The command exits nonzero while blocked. Recompute and compare the retained
report with:

```bash
node tools/eve-everywhere/verify-charter-completeness-report.mjs
```