Detailed Architecture Coverage Matrix

1. The problem

Broad architecture maps are good orientation aids and poor accountability systems. The same idea is often labeled differently in lifecycle, runtime, security, and operations diagrams. Gaps hide behind overlapping labels while attractive visuals make partial coverage look complete.

This matrix is the normalization layer. Detailed chapters own specifications; the matrix owns traceability among capability, lifecycle, plane, role, risk, maturity, evidence boundary, and validation.

2. Canonical coverage matrix

3. Canonical relationships

The lifecycle is Intent -> Plan -> Select -> Execute -> Verify -> Evidence -> Decide -> Deliver -> Observe -> Learn. Logical planes are responsibility boundaries, not mandated services. The governed inventory points to—but never duplicates—the service, capability, model, policy, and evidence registries. Architecture patterns select the minimum sufficient autonomy; maturity labels describe documentation or scoped evidence, not how impressive a pattern is.

4. Classification rules

1. A new label must map to an existing capability or justify a new owner.
2. Product and vendor names are examples, never canonical components.
3. General AI background is supporting material unless it changes a factory architecture decision.
4. A diagram without a text or table equivalent is incomplete.
5. Review-ready documentation never advances a capability to operationally proven status.
6. A shared concern may cross planes, but one role owns the decision and one record is authoritative.

5. Standards baseline

6. Review exercise

Choose one production change and one failure. Trace both across the matrix. For each transition name the actor, identity, authoritative record, policy, evidence, stop condition, recovery action, and human decision. Record any responsibility with two owners or no owner as a taxonomy defect.

7. Explicit nonclaims

This matrix does not certify implementations, prescribe an organization chart, or require separate deployments for each plane. It is a review-ready ownership map awaiting external architecture, security, operations, and usability review.