Finalize digital-twin scope as two ACL-based patterns

Plan's digital-twin scope is now exactly (1) environment-lifecycle
promotion via ACL flip on write authority and (2) safe read-only
consumption for KPI / monitoring systems — both delivered by
already-committed architecture. Removes the meeting-prep brief and the
management-delivered use-cases source document; canonical model and
state vocabulary stand as pillar-2 work on their own.

outputs/DESIGN.md

@@ -31,7 +31,7 @@ Together these reduce "what Claude has to decide" to **text phrasing inside a fi
 ```
 plan/
 ├── current-state.md, goal-state.md, roadmap.md, status.md    (existing, unchanged)
-├── current-state/, goal-state/                                (existing, unchanged)
+├── current-state/                                             (existing, unchanged)
 └── outputs/                                                    (NEW)
     ├── README.md                 — trigger phrases + numbered regeneration checklist
     ├── DESIGN.md                 — this document
@@ -112,7 +112,7 @@ Slide-by-slide mapping (full detail lives in `outputs/presentation-spec.md`):
 
 **Page setup:** Letter, 1" margins, chapter-name running header, page-number + as-of-date footer. `document-skills:theme-factory` default serif.
 
-**Excluded from PDF:** `status.md`, `CLAUDE.md`, `goal-state/digital-twin-management-brief.md`, `outputs/*` (all meta, working, or prep content — not plan content).
+**Excluded from PDF:** `status.md`, `CLAUDE.md`, `outputs/*` (all meta, working, or prep content — not plan content).
 
 ## Section 5 — Diagrams