docs(P21): normalize vision.md L1/L2/L3A/L3B labels (VERIFY fix)

---ci---
project: acdl
phase: 21
milestone: v1.6
status: verify
---/ci---

VERIFY caught a residual L1/L2/L3A/L3B nomenclature in docs/vision.md
('the four-layer model (L1 Terraform primitives, L2 composed stacks, L3A
developer surface, L3B agentic surface)'). Normalized to (primitives,
modules, developer surface, agentic surface) to match the consumer-facing
terminology.

Verification summary:
- REQ-52: 0 .ciagent/.gitea refs in docs/ README.md modules/ contracts/.
- REQ-53: 0 acdl_platform refs in code (excl .ciagent/demo/.git).
- REQ-54: docs/ Jekyll structure complete; 0 .ciagent links in docs/.
- REQ-55: 0 L1/L2/L3A/L3B labels in consumer docs; composition->pattern
  in prose (composition.json files kept); composition roadmap entry kept.
- REQ-56: 0 forge refs in consumer docs.
- REQ-57: README repository roles restated (app code + contracts + CI
  definitions).
- REQ-58: Features + Roadmap sections present; no version changelog.
- REQ-59: mermaid has security-checks + infrastructure-plan + policy-
  checks + infrastructure-apply; no tool names in diagram.
- REQ-60: 0 go-gitea/waiver/D-039/D-047 in README; daily/out-of-band
  rotation retained.
- REQ-61: core/environments/ + dev.json + environment_check.py +
  run_platform.sh wire-in + 12 tests.

Tests: 166 pass. run_ci.sh green.
This commit is contained in:
Jon Chery
2026-07-22 18:27:01 +00:00
parent 553caf8f1d
commit df7b40b435
+1 -1
View File
@@ -68,4 +68,4 @@ The vision is realized when:
## What this vision is, and what it isn't
* **It is:** A principles document. The North Star, the tenets, the strategic bets, the anti-goals. It's intended to be the page that orients a new team, a new stakeholder, or a new architectural decision. It should not need to be rewritten when a tool changes.
* **It isn't:** An architecture. The four-layer model (L1 Terraform primitives, L2 composed stacks, L3A developer surface, L3B agentic surface), the central pipeline template model, the schema location, the dual HITL mechanics, the enterprise evidence stream integration — all of that belongs in the architecture document, where it can be specific and evolve independently.
* **It isn't:** An architecture. The four-layer model (primitives, modules, developer surface, agentic surface), the central pipeline template model, the schema location, the dual HITL mechanics, the enterprise evidence stream integration — all of that belongs in the architecture document, where it can be specific and evolve independently.