Needs-Input Register

Cross-document backlog of gaps, MISSING items, and standing-feedback status

Published

April 25, 2026

1. Cross-cutting items

These items affect multiple phase documents simultaneously and should be resolved at the program level rather than per-doc.

ID Item Affected docs Action owner Notes
X-01 Classification markings retired All eight docs Program Office Resolved in this consolidation pass — the Controlled markings were removed and replaced with the public-release disclaimer. Verify no further references survive prior to formal release.
X-02 Sample-vs-actual OrgTree framing Phase 1, Phase 0 Assessment Phase team Phase 1 Rev 0.x feedback called this out; the merged Phase 1 now carries the sample framing. The authoritative production OrgTree is an Assessment-Phase deliverable.
X-03 AD→Entra sync as baseline assumption ✓ Resolved Phase 1 (§5 Identity), Phase 0 (§2.1 Identity Plane) Identity Team Per Rev 0x feedback #2: agencies operating M365 / Azure already have AD→Entra sync. Resolved in both the merged Phase 1 (Editorial Note) and Phase 0 §2.1 (now carries an explicit “Baseline assumption — AD→Entra ID synchronization is already operational” callout).
X-04 Customer-doc series — registry allocation ✓ Resolved by design Phase 0–5 + appendices Canon Steward Decision: no allocation in src/uiao/canon/document-registry.yaml is required. The eight chapters were placed under docs/customer-documents/modernization/uiao-modernization-program/ as a customer-document series, which is the DERIVED authority tier per src/uiao/schemas/metadata-schema.json (classification: DERIVED), not the CANONICAL tier. The existing registry is scoped to canonical documents under src/uiao/canon/. If a future governance decision elevates any of these chapters to canon, allocate UIAO_NNN IDs at that time and move the source from docs/customer-documents/ to src/uiao/canon/ per ADR process. The customer-doc series itself does not need IDs; chapters reference their canon sources via the canon-source frontmatter field.
X-05 Lifecycle-state extension in registry Phase 5 §3.1 / 3.2 Canon Steward + governance review Phase 5 proposes DRAFT / ACTIVE / DEPRECATED / ARCHIVED states with superseded_by pointers. The current registry only carries status: Current\|Draft. Schema extension required.
X-06 Diagram backlog Phase 1 (DIAG-001..006), Phase 3 (P3-D-001..004), Phase 4 (multiple), Phase 5 (P5_DIA_001..004) Visual production All inline [PLACEHOLDER --- DIAG / P3-D / P5_DIA] blocks need PlantUML/Quarto authoring under docs/figures/. Estimated: 18+ diagrams across the corpus.
X-07 Tables marked MISSING Phase 5 (P5_TBL_001 — Artifact Consolidation Status Matrix), Phase 3 (multiple risk-table cells) Phase 5 / Phase 3 leads The Phase 5 P5_TBL_001 Artifact Consolidation Status Matrix requires a canon/ directory scan to populate. Several Phase 3 risk-register cells flag [MISSING — drift threshold], [MISSING — SLA value] etc. — see §3 below for full list.

2. Per-document needs-input (cross-reference)

Program Overview (UIAO_010)

  • No internal MISSING / PLACEHOLDER markers. Document is ready for release pending program-level cross-reference verification.

Phase 0 — Master Plan (UIAO_020)

  • No internal MISSING / PLACEHOLDER markers.
  • ✓ §2.1 Identity Plane updated to acknowledge AD→Entra sync as baseline assumption (cross-cutting item X-03 resolved).
  • §6c Compliance and ATO Plan references a “3PAO engagement plan” that is not yet drafted — this is an external dependency, not a doc gap.

Phase 1 — Modernization Mechanics (UIAO_021, merged)

  • 6 explicit needs-input items in the document’s own Appendix F (Production OrgTree values, per-wave durations, diagrams, identity translation table fill-in, network-visibility tool selection, RACI customization).

Phase 2 — Governance OS Deployment (UIAO_022)

  • No MISSING markers found in the cleaned text, but the original carried multiple [NEW (Proposed)] proposals (e.g., OSCAL component generation cadence, Sentinel correlation rule pack) that need governance review before being treated as canonical.
  • Specific gap: target engagement channels (cisagov/ScubaGear, FedRAMP RFCs, FSCAC/CISA) listed in §1 are aspirational — no formal agency outreach commitments documented.

Phase 3 — Optimization & Continuous ATO (UIAO_023)

  • 48 gap markers including:
    • [PLACEHOLDER --- P3-D-001..004] (4 PlantUML diagrams)
    • [MISSING — drift threshold values] for multiple drift classes
    • [MISSING — SLA threshold values] for multiple control families
    • [MISSING — AO-specific acceptance criteria] for cATO Acceptance Package
    • [NEW (Proposed)] Adapter Doctrine, Cost Optimization, RMM Stage 3–5
    • [MISSING — drift threshold] cells in P3-R-001 .. P3-R-008
    • [MISSING — SLA threshold] cells in P3-R-005

Phase 4 — Cooperative Multi-Agent Governance (UIAO_024)

  • 37 gap markers, predominantly [NEW (Proposed)] for the multi-agent topology that does not yet have a canonical implementation. Specific items:
    • Agent-to-agent message bus protocol (proposed, not specified)
    • Drift-intelligence aggregator data model (proposed)
    • Multi-agent SLA hand-off contracts (proposed)
    • Conflict-resolution arbitration logic (proposed)

Phase 5 — Canon Integration (UIAO_025)

  • 62 gap markers — the highest in the corpus. Phase 5 is structurally forward-looking and most of its concepts are flagged [NEW (Proposed)]:
    • Canon Integration Index (CII) manifest format
    • DRAFT / ACTIVE / DEPRECATED / ARCHIVED lifecycle state machine
    • Baseline branching model with governance-merge workflow
    • Hot / warm / cold archival storage tiers
    • Baseline compatibility matrix
    • P5_TBL_001 — Artifact Consolidation Status Matrix (MISSING — needs canon/ scan)
    • P5_DIA_001..004 (4 diagrams placeholder)

Client-Server to Hybrid-Cloud Reference (UIAO_030)

  • No internal MISSING / PLACEHOLDER markers found. Document is reference material; cross-reference verification recommended before release.

3. Standing-feedback items (status)

Feedback source Item Status
Phase 0 feedback.docx (target: Phase 1 Rev 0.x) Drop classification markings Resolved in this consolidation pass.
Phase 1 feedback.docx Sample vs. actual OrgTree framing Applied in merged Phase 1 (UIAO_021); Phase 0 inherits via shared OrgTree references.
Phase 1 Rev 0x feedback Drop classification markings Resolved.
Phase 1 Rev 0x feedback Acknowledge AD→Entra sync as already-required baseline Applied in merged Phase 1 Editorial Note and Phase 0 §2.1 (“Baseline assumption” callout).
Back to top