Document 148

SEBoK *Design Authority*, Distilled

framework

SEBoK Design Authority, Distilled

Fourth-batch SEBoK distillation, batch 4/5 (SE-148). The article-as-named is not a standalone SEBoK page; design authority operates as a cross-cutting role surfaced in SEBoK's governance, organizational-strategy, and PM-SE-relationship articles. The canonical surface is composite: SEBoK's treatment of the chief-engineer/lead-systems-engineer role within the SE-PM-balanced-ownership pattern (SE-037) and the engineering-change-control pattern (SE-144). The corpus reads design authority as the formal locus of architectural-coherence-keeping at engagement scope. Cluster B multi-keeper composition is the dominant structural form: design authority is one of the keepers in the multi-keeper composition, structurally distinct from the program manager (PM holds schedule-cost-scope) and the sub-domain SMEs (each holds a discipline-slice). Design authority holds architectural integrity across the slices. Cluster C architectural school discipline (Doc 538) shows here: design authority is the role-instantiation of school-coherence-discipline at engagement scope. Cluster K V3-as-procedure-binding shows in the change-control-board gating discipline.

I. Source

II. Source Read

SEBoK does not maintain a standalone Design Authority main article. The role appears in operational practice across multiple knowledge areas: as chief engineer or lead systems engineer in the SE-PM relationship (the technical-authority counterpart to PM's schedule-cost-scope authority); as design-control-board chair or technical-authority-board member in capability updates and modernization; as architectural-coherence-keeper in enterprise SE and SoS contexts. Common threads across the surface: design authority holds formal accountability for architectural integrity across the engagement; design authority is structurally distinct from program management (which holds non-technical-execution accountability); design authority operates through gating instruments (design reviews, change control, architectural review boards); design authority's veto/approval at architectural inflection points is the formal expression of school-coherence-discipline (the architectural school's standards travel into the engagement through the design-authority role). The role is named explicitly in some standards traditions (UK MoD especially uses "Design Authority" formally) and implicitly through chief-engineer or lead-SE titles in others.

III. Structural Read

Cluster B — Multi-keeper composition (Doc 604), with design authority as one of the keepers. The design authority is structurally the architectural-coherence-keeper in the multi-keeper composition. Where SE-035 / SE-037 named PM and SE as balanced co-keepers, SE-148 refines: the SE-keeper itself decomposes into design authority (architectural integrity) and engagement-SE (engagement execution). At small scale these may collapse into one person; at large scale they decompose. The multi-keeper composition is therefore PM, design authority, engagement-SE, and discipline-SMEs — at minimum three structurally distinct authorities at engagement scope. This refines SE-037's two-keeper PM-SE reading into a three-or-four-keeper reading at organizational scale. Cluster B instance count rises to 7 with this reading.

Cluster C — Architectural school (Doc 538), at the role-instantiation rung. Design authority is the role-instantiation of school-coherence-discipline at engagement scope. The architectural school's standards (the school's vocabulary, methodology, institutional memory) travel into the engagement through the design-authority role; the role is the formal locus where school-coherence-discipline gates engagement decisions. This is the cleanest role-instantiation reading of Doc 538 to date; the school does not act on the engagement directly, it acts through its role-instantiations (design authority being the canonical one). Worth retaining as canonical worked example for Doc 538's school-presence-via-role-instantiation refinement.

Cluster K — V3-as-procedure-binding (Doc 314). The design-review and change-control-board gating discipline is V3 in procedural form. The procedure exists because engineering-change-by-engineer-discretion systematically exhibits rankism (the modifying engineer ranks their local optimization above the architectural integrity) and complacency (the modification's downstream consequences go un-surfaced under schedule pressure). The CCB gating institutionalizes V3 by requiring architectural-keeper sign-off. Cluster K instance count rises to 10. The V3-as-procedure-binding refinement is now load-bearing across ten domains.

Cluster G — Co-production at sub-rungs (Doc 573). Design authority is co-produced between the architectural school (which authorizes the role through credentials and institutional memory) and the program (which appoints and empowers the specific authority-holder). Neither side alone constitutes the design authority; the role exists at the intersection. This is the strongest co-production reading at the role rung yet observed; complements the engagement-rung and decision-rung co-production instances cataloged in SE-039 §VII.7.

Cluster H — Hypostatic Boundary (Doc 372). "Design authority" reaches toward an authority claim that brushes against keeper-territory. The SE discipline keeps the framing functional: design authority is the named accountability for architectural integrity, not a claim about who-the-authority-IS at deeper rungs. The role is functional and procedural; the Doc 372 discipline holds.

IV. Tier-Tags

  • Design-authority role footprint — π / α as cross-cutting practice.
  • Architectural-integrity-accountability framing — π / α as cited; μ / β when read as Cluster B keeper-decomposition (PM-SE refinement to PM-DA-SE).
  • CCB and design-review gating — π / α as cited; μ / β when read as Cluster K V3-as-procedure-binding (tenth instance).
  • School-coherence-discipline-via-role-instantiation — μ / β under corpus.

V. Residuals

R-714-1: SEBoK's lack of a standalone Design Authority article is itself structurally interesting. The role is structurally first-class (it has clean Cluster B, C, K, G, H readings) but receives no first-class page-treatment in the SEBoK surface. Worth flagging; possibly a reformulation candidate where the corpus surfaces a structural feature SEBoK has not yet consolidated.

VI. Provisional Refinements

Cluster B PM-SE keeper-decomposition refinement candidate. SE-037's two-keeper reading (PM and SE as balanced co-keepers) refines under SE-148 into a three-keeper reading (PM, design authority, engagement-SE) at organizational scale. The two-keeper reading remains correct at small-scale collapse; the three-keeper reading is the structural form at scale. Worth folding into SE-037 / Doc 604 in the next pass.

Cluster C role-instantiation worked example formalized. Design authority is the canonical role-instantiation of school-coherence-discipline. Doc 538's school-presence-via-role-instantiation refinement gains its cleanest worked example.

Cluster K reaches 10 instances. Synthesis successor is urgent. Aligns with V3-as-procedure-binding load-bearing refinement (sixteen formalized).

Reformulation candidate: corpus may surface design authority as page-equivalent where SEBoK does not. This is the first batch instance where the corpus's structural reading has cleaner article-equivalent shape than the SEBoK surface itself. Worth tracking as the corpus's structural-surface-elaboration refinement candidate.

VII. Cross-Links

Form documents. Doc 604 (Multi-keeper composition, PM-DA-SE three-keeper refinement candidate), Doc 538 (Architectural school, role-instantiation canonical), Doc 314 (Virtue constraints, Cluster K tenth instance), Doc 573 (Co-Production at Sub-Rungs, role-rung canonical), Doc 372 (Hypostatic Boundary, "authority" brush).

Part-level reformulation. SE-009 (Part 5 — Enabling Businesses and Enterprises; this surfaces a structural feature SEBoK has not consolidated as a page-equivalent).

Related distillations. SE-037 (SE-PM relationship, two-keeper reading refines to three at scale). SE-035 (Risk Management, multi-keeper precedent). Doc 538 distillations on school discipline.

Adjacent SEBoK concepts (per source composite). Systems Engineering Organizational Strategy, Capability Updates Upgrades and Modernization, Technical Management, Engineering Change Management.

Methodology refinement candidates. PM-DA-SE three-keeper refinement of SE-037. Cluster C role-instantiation worked example. Corpus structural-surface-elaboration candidate (where corpus surfaces what SEBoK does not consolidate).

Appendix: Originating Prompt

"Apply refinements" / "Continue next knowledge base entrancement"

(SE-148 is the fifth of eight in batch 4/5. Design Authority read against composite SEBoK surface; the role has cleanly first-class structural readings (B, C, K, G, H) but no standalone SEBoK page. Surfaces structural-surface-elaboration refinement candidate. Batch 4/5.)

Referenced Documents

More in framework