S07.1 — Orchestrate the full CPU validation suite

Planning / historicaltaskdelivery

Historical

Planning material. It summarizes and links to the authoritative specification and the current measured state — it does not replace either, and it is not current engineering truth.

Migration identity#

Canonical identifier: S07.1 (GitHub issue type: subtask).
Legacy identifier: C07.1 (retained as old_identifier).
Parent epic: E07.
Milestone: M1 — IntentGuard Weekend MVP.

Objective#

Run deterministic CPU-compatible unit, contract, integration, lint, type, manifest, compile, and acceptance checks with reproducible setup.

Rationale#

One reliable validation entry point turns individual implementation evidence into a maintainable repository gate.

Parent identifier#

E07.

Source task#

T-007.

Traceability#

Primary: T-007, NFR-002, NFR-009. Secondary: all AC identifiers as verification consumers.

Prerequisites#

U01–U06 implemented; all tests and validation scripts exist; CPU-safe fixtures/artifacts are declared.

Likely files#

Makefile, scripts/validate_acceptance.py, tests/, .github/workflows/ci.yml, reports/acceptance.json.

Implementation boundary#

Orchestration and evidence collection only; no feature implementation or requirement relaxation.

MUST scope#

Locked setup, CPU suite, lint/type/compile checks, manifest/traceability checks, deterministic rerun checks, CI alignment, classified results.

Explicit non-goals#

GPU claims, load testing, Docker, deployment, optional feature validation, or silently skipped MUST tests.

Acceptance criteria#

Required CPU checks pass locally and in CI; skips/unavailable checks are explicit and justified; outputs identify artifact/data versions; repeated contract results are stable.

Validation commands#

make setup && make lint && make test && uv run python scripts/validate_acceptance.py.

Expected evidence#

Command transcript, CPU CI run, test summary, static-check output, environment identity, and machine-readable acceptance report.

Fallback and status consequence#

CPU-only is valid; unavailable or skipped required evidence cannot be marked passed and blocks strict completion.

Stop condition#

Stop for flaky required checks, hidden network dependence, unclassified skips, secret/generated-artifact findings, or CI/local divergence.

Definition of ready#

All feature umbrellas report implementation complete with stable validation commands.

Definition of done#

NFR-002/NFR-009 have executed local and CI evidence and validation is reproducible.

Labels#

type:subtask, priority:MUST, area:quality

Estimate#

0.75 hour.