Files
acdl/.ciagent/AUDIT.md
T
Jon Chery 9897df04b2 fix(P52): add regression-class VERIFY (D-091) — catches capability decay
The prior VERIFY stage was diff-scoped: it checked the phase diff only
and never re-ran underlying platform capability. This structural defect
(D-091) let 8 NFR-patch phases (v1.9.1-v1.9.8, deck rework) pass VERIFY
while the platform they described decayed underneath.

Phase 52 remediation:
- core/regression_verify.py: regression-class VERIFY with 10 seeded
  local-tier capability checks (CAP-001..CAP-010). Tags each
  Verified/Decayed/Broken; fails closed on any non-Verified.
- scripts/run_regression.sh: shell wrapper; writes
  .ciagent/REGRESSION_REPORT.{md,json}; exits non-zero on decay.
- tests/test_verify_regression_mode.py: 11 tests (8 fast + 3 slow).
  Confirms the gate catches decay (fails closed) and that regression
  mode is additive (diff-scoped VERIFY behavior preserved).
- pyproject.toml: slow marker registered; run_ci.sh excludes slow
  tests to avoid recursion.

Verified: 502 fast tests pass (was 493 at v1.9; +9 new). 3 slow
integration tests pass. run_regression.sh reports all 10 seeded
local-tier capabilities Verified against current code. The
decay-surfacing test injects a broken cloud-backed check and confirms
the run tags it Broken and fails closed.

Cloud-backed capability re-verification (live ECS, DynamoDB writes,
Lambda invocation) lands in Phase 54 (D-093).

---ci---
project: acdl
phase: 52
milestone: v1.10
status: verify
requirements:
  covered: [REQ-112]
  partial: []
decisions: [D-091]
regression:
  - { capability: CAP-001, status: Verified }
  - { capability: CAP-002, status: Verified }
  - { capability: CAP-003, status: Verified }
  - { capability: CAP-004, status: Verified }
  - { capability: CAP-005, status: Verified }
  - { capability: CAP-006, status: Verified }
  - { capability: CAP-007, status: Verified }
  - { capability: CAP-008, status: Verified }
  - { capability: CAP-009, status: Verified }
  - { capability: CAP-010, status: Verified }
---/ci---
2026-07-27 17:29:52 +00:00

4.5 KiB
Raw Blame History

ACDL v1.9 — Audit Report

Audit date: 2026-07-23. Auditor: ci-debugger. Milestone: v1.9. Result: PASS.

Step 1: Reconstruction Test

  • 16 v1.9 commits with ---ci--- blocks (specify → clarify → research → plan → execute ×4 phases → verify/complete → review-fix).
  • Reconstructed state: milestone v1.9, phase 43, status complete.
  • Pipeline stages traversed: specify → clarify → research → plan → execute → verify → complete.
  • Decisions D-080..D-089 all present in git log + .ciagent/ files.
  • config.json (v1.9 complete), PROJECT.md (v1.9 complete), REQUIREMENTS.md (v1.9 complete, 12 reqs), ROADMAP.md (v1.9 complete, phases 3943), REVIEW.md (READY TO SHIP), PERSONAS.md (v1.9), VERIFY.md, AUDIT.md. PASS.

Step 2: File Discipline

  • .ciagent/config.json: valid JSON; mode, projects[] present. PASS.
  • .ciagent/PROJECT.md: Vision/Core Value (≡ "What This Is"), Key Decisions (v1.9 D-080..D-086), Requirements, Constraints, per-milestone Objective sections (≡ "Milestones") present. Section names follow the v1.0 established conventions (not the generic audit template). PASS.
  • .ciagent/ROADMAP.md: phases 3943 present; all marked complete. PASS.
  • .ciagent/REQUIREMENTS.md: v1.9 traceability table complete (12/12 REQ-100..111 marked complete (v1.9.0)). PASS.
  • .ciagent/ARCHITECTURE.md: fixed during audit — v1.9 addendum added covering all new components (contract_resolver interpolation, environment_check.load, hitl_gates, attestation_matrix, separation_of_duties.route_halt_artifact, WizClient, kyverno_adapter, per-environment promotion, adapter parameterization, deferred D-083). All 9 v1.9 code components now referenced. PASS (after fix).

Step 3: Branch Hygiene

  • Local: main only. Remote: origin/main only.
  • No phase or milestone branches remain (all 5 v1.9 phase branches merged
    • pruned during the run/ship workflow).
  • No orphan branches. PASS.

Step 4: Commit Discipline

  • 16/16 v1.9 commits have ---ci--- blocks with project/phase/milestone/ status fields.
  • No stale implementation decisions (D-081..D-085, D-087..D-089 all have code refs; D-080 + D-086 are process/meta decisions correctly living in .ciagent/ files).
  • No unresolved v1.9 escalations (the 3 audit(...) commits in history are from prior milestones v1.0/v1.6/v1.7). PASS.

Issues fixed during audit

  1. ARCHITECTURE.md missing v1.9 addendum — the architecture doc had no coverage of the v1.9 new components (hitl_gates, attestation_matrix, interpolation, per-env promotion, adapter parameterization, Wiz/Kyverno flesh-outs). Fixed: added a v1.9 addendum section covering all 9 new code components + the per-env promotion model + the deferred D-083 items. Verified all 9 components now referenced.

Audit result: PASS


ACDL v1.10 Phase 52 — Audit Addendum

Audit date: 2026-07-27. Auditor: ci-debugger. Phase: 52 (pipeline regression-VERIFY fix). Result: PASS.

Process defect recorded (D-091)

The prior VERIFY stage was diff-scoped: it checked the phase diff only and never re-ran underlying platform capability. This structural defect let 8 NFR-patch phases (v1.9.1→v1.9.8, deck rework) pass VERIFY while the platform they described decayed underneath. The defect is recorded as D-091 and remediated in Phase 52 by core/regression_verify.py + scripts/run_regression.sh.

Phase 52 audit

  • Reconstruction: Phase 52 commits present with ---ci--- blocks (plan + execute + verify). Decisions D-090..D-094 recorded in PROJECT.md. Requirements REQ-112..REQ-115 recorded in REQUIREMENTS.md. PASS.
  • File discipline: core/regression_verify.py, scripts/run_regression.sh, tests/test_verify_regression_mode.py present. .ciagent/PLAN.md, ROADMAP.md, PROJECT.md, REQUIREMENTS.md, VERIFY.md updated for v1.10. PASS.
  • Behavioral: 502 fast tests pass (was 493; +9 new). 3 slow integration tests pass. run_regression.sh runs and reports honestly. PASS.
  • Commit discipline: Phase 52 commits carry ---ci--- blocks with project/phase/milestone/status. PASS.

Note on prior "audit CLEAN" claims

The v1.1v1.9 "audit CLEAN" claims were point-in-time true (the capabilities ran at the time of tagging). They do not assert current reproducibility. The capability decay surfaced in the 2026-07-27 CLARIFY/RESEARCH stages is being re-verified in Phase 54 (D-093). The v1.10 audit will re-assert current reproducibility after the sweep.

Phase 52 audit result: PASS