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.
This commit is contained in:
Joseph Doherty
@@ -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
|
||||
|
||||
|
||||
@@ -88,7 +88,7 @@ Expected: `DESIGN.md IMPLEMENTATION-PLAN.md diagrams generated` (README, spec
|
||||
- Appendix A: `current-state/legacy-integrations.md`
|
||||
- Appendix B: `current-state/equipment-protocol-survey.md`
|
||||
- Transformation rules (numbered heading, link normalization, `_TBD_` highlight, ASCII diagram preservation, table handling)
|
||||
- Exclusion list (`status.md`, `CLAUDE.md`, `goal-state/digital-twin-management-brief.md`, `outputs/*`)
|
||||
- Exclusion list (`status.md`, `CLAUDE.md`, `outputs/*`)
|
||||
|
||||
**Verification:**
|
||||
- File exists
|
||||
|
||||
@@ -47,7 +47,6 @@ These files are **not** part of the PDF — do not include them even if they see
|
||||
|---|---|
|
||||
| [`../CLAUDE.md`](../CLAUDE.md) | Repo meta — instructions for Claude, not plan content. |
|
||||
| [`../status.md`](../status.md) | Working bookmark — a session-state artifact, not authoritative plan content. |
|
||||
| [`../goal-state/digital-twin-management-brief.md`](../goal-state/digital-twin-management-brief.md) | Meeting prep artifact. Its own header explicitly says it is not plan content. |
|
||||
| [`./README.md`](README.md), [`./DESIGN.md`](DESIGN.md), [`./presentation-spec.md`](presentation-spec.md), [`./longform-spec.md`](longform-spec.md), [`./IMPLEMENTATION-PLAN.md`](IMPLEMENTATION-PLAN.md), [`./run-log.md`](run-log.md) | Output pipeline files — the pipeline does not document itself inside its own output. |
|
||||
| [`./diagrams/*`](diagrams/), [`./generated/*`](generated/) | Output pipeline artifacts. |
|
||||
|
||||
@@ -85,7 +84,7 @@ Markdown links between plan files are resolved to section references in the rend
|
||||
| `[legacy-integrations.md](current-state/legacy-integrations.md)` | "see Appendix A — Legacy Integrations Inventory" |
|
||||
| `[equipment-protocol-survey.md](current-state/equipment-protocol-survey.md)` | Render as **plain text** — file removed. Log as warning. |
|
||||
| Intra-file anchor links like `[X](#section-name)` | Rendered as internal PDF cross-reference to the numbered section (e.g., "see §1.2") |
|
||||
| Links to excluded files (e.g., `status.md`, `digital-twin-management-brief.md`) | Rendered as **plain text** — the link target is dropped, the link text stays. Logged as a warning in the run log. |
|
||||
| Links to excluded files (e.g., `status.md`) | Rendered as **plain text** — the link target is dropped, the link text stays. Logged as a warning in the run log. |
|
||||
| External links (http://, https://) | Rendered as clickable external links, unchanged. |
|
||||
| Unresolvable links (file not found) | Rendered as plain text, logged as a warning in the run log. **Do not silently drop.** |
|
||||
|
||||
|
||||
@@ -172,7 +172,7 @@ If `document-skills:pptx` cannot render a requested layout:
|
||||
|---|---|
|
||||
| **Layout** | 2-column content (fallback: single column with horizontal rule) |
|
||||
| **Source** | [`../goal-state.md`](../goal-state.md) → **Strategic Considerations (Adjacent Asks)** |
|
||||
| **Population** | **Left column — Digital Twin:** 4 bullets: (1) Management ask, not a committed workstream; (2) Plan shaped to serve if it materializes (OtOpcUa, Redpanda, Snowflake); (3) 8 clarification questions + 4-bucket decision framework ready; (4) Next: schedule management conversation — brief at `goal-state/digital-twin-management-brief.md`. **Right column — BOBJ → Power BI:** 4 bullets: (1) In-flight reporting initiative, not owned by this plan; (2) Three consumption paths analyzed (Snowflake dbt / Historian direct / both); (3) Recommended position: Path C — hybrid, with Path A as strategic direction; (4) Next: schedule coordination conversation with reporting team — 8 questions ready in `goal-state.md`. |
|
||||
| **Population** | **Left column — Digital twin (scope: two access-control patterns):** 4 bullets: (1) Scope is definitive — not a committed workstream, not a new component; (2) Pattern 1 — environment-lifecycle promotion without reconfiguration (ACL flip on write authority); (3) Pattern 2 — safe read-only consumption for KPI / monitoring systems (structural zero-write-path guarantee); (4) Both patterns are delivered by already-committed architecture (OtOpcUa ACL model + canonical model + single-connection-per-equipment). **Right column — BOBJ → Power BI:** 4 bullets: (1) In-flight reporting initiative, not owned by this plan; (2) Three consumption paths analyzed (Snowflake dbt / Historian direct / both); (3) Recommended position: Path C — hybrid, with Path A as strategic direction; (4) Next: schedule coordination conversation with reporting team — 8 questions ready in `goal-state.md`. |
|
||||
|
||||
## Slide 17 — Non-Goals
|
||||
|
||||
@@ -189,7 +189,7 @@ If `document-skills:pptx` cannot render a requested layout:
|
||||
|---|---|
|
||||
| **Layout** | Content (bulleted) |
|
||||
| **Source** | [`../status.md`](../status.md) → **Top pending items** + inferred from [`../roadmap.md`](../roadmap.md) → Year 1 |
|
||||
| **Population** | 5 bullets: (1) Sponsor confirmation + Year 1 funding commitment; (2) Named owners for each of the 7 workstreams (build team alignment); (3) Digital Twin management conversation — schedule (see brief); (4) Power BI coordination conversation with reporting team — schedule; (5) Equipment protocol survey owner named (Q1 Year 1 prerequisite for OtOpcUa core driver library). |
|
||||
| **Population** | 4 bullets: (1) Sponsor confirmation + Year 1 funding commitment; (2) Named owners for each of the 7 workstreams (build team alignment); (3) Power BI coordination conversation with reporting team — schedule; (4) UNS hierarchy snapshot walk owner named (Q1–Q2 Year 1 prerequisite for canonical model v1 publication). |
|
||||
| **Notes** | This is the closer slide. Each bullet should be a discrete ask with a clear "who needs to do what" so the audience leaves with action. |
|
||||
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user