Document 582

SEBoK Subsumption — Trajectory

framework

SEBoK Subsumption — Trajectory

The living vector for the SEBoK subsumption engagement, applying the Resume Vector pattern (Doc 581) to a corpus engagement that already has a stable seed (Doc 570 — the canonical synthesis) but lacked a trajectory until now. This document carries what is done, what is queued in priority order, what is deferred with explicit re-open conditions, and a four-step resume protocol so any future session can pick the engagement up without re-deriving from the thirteen-document subsumption series. Updated as work advances; pairs with Doc 570 (the seed) and the Resume Vector form (Doc 581).

I. Current State as of 2026-04-30

What is the engagement

The SEBoK subsumption is the corpus's reformulation of the Systems Engineering Body of Knowledge through the corpus's structural forms. Began 2026-04-28 with Doc 557; closed Phase 5 on 2026-04-29 with Doc 569; subsumed into canonical Doc 570; produced four cluster formalizations (Docs 571 through 574); produced the SEBoK seed at Doc 577; ran three per-article pilot distillations consolidated at Doc 578.

What stable kernel governs

Doc 570 — SEBoK Through the Corpus — Canonical — is the engagement's seed. It carries the conjecture, the methodology, the result (verified operationally, partially refuted theoretically), the four named extension surfaces, the per-part findings, and the discipline for future moves. Read Doc 570 first when resuming.

What was last shipped

Doc 578's pilot distillation methodology validated across three SEBoK pages (Engineered System Context, Sequential Development Approach, Hubble Space Telescope Case Study). The seven-section per-article template stabilized. Doc 571 gained Section X (the four-state ground taxonomy: stable / conflicted / decayed / evacuated, with Doc 574 absorbed as the evacuated-state articulation). Doc 572 gained Appendix A (the development-approach lattice worked example). The hypostatic-boundary-versus-virtue-constraint reading sharpened: out-of-scope residuals must be tested against Doc 314's virtue-constraint apparatus before being logged as out-of-scope.

What is the actively-open question

Whether to scale per-article distillation across SEBoK's full ~800-page surface, or to apply Doc 576's hybrid recommendation (Mode 1 reference-only for most pages, Mode 4 hosted import only for the ~30-60 editorial-dense pages, Mode 2 reformulation companions already in place). The pilots demonstrated that per-article distillation produces yield even on pages that aren't editorial-dense at the structural level. Decision pending.

II. Trajectory

Done

Phase Scope Doc(s)
Phase 1 — Form Inventory Nine corpus forms catalogued with five-field operational summaries Doc 558
Phase 2 — Macro-Map Eight one-paragraph macro-mappings, one per SEBoK part Doc 559
Phase 3 — Per-Part Reformulation Eight per-part reformulations against the macro-map's hypotheses Docs 560-567
Phase 4 — Falsifier Audit 30 residuals classified into (a)/(b)/(c); class (c) refined into named clusters Doc 568
Phase 5 — Synthesis Conjecture verified operationally, partially refuted theoretically; four extension surfaces named Doc 569
Subsumption Canonical synthesis subsumes Phases 1-5; originals demoted to appendices Doc 570
Cluster II Institutional Ground formalized (six conditions, four states added later) Doc 571
Cluster III Lattice Extension of the Ladder (with Appendix A worked example) Doc 572
Cluster I Co-Production at Sub-Rungs (interdependent with Doc 571) Doc 573
Cluster IV Authority Evacuation, provisional (later absorbed as Doc 571's evacuated state) Doc 574
Import Plan Original full hosted-import plan in six phases Doc 575
Subsumption Modes Seven-mode taxonomy, hybrid recommendation for SEBoK Doc 576
SEBoK Seed Mode 3 distillation: portable kernel for the apparatus Doc 577
Pilot Distillations Three pilots with consolidated seven-section template; methodology validates Doc 578
Methodology Formalization Five-phase reformulation methodology articulated as its own corpus form (closes Q2) Doc 583
Top-10 Distillations Ten per-article distillations selected for corpus-form composition density and refinement potential. Surfaces multiple Doc 571 / Doc 572 / Doc 573 / Doc 445 / Doc 490 refinement candidates. Docs 584-593
Form Refinements (A-D) Doc 571 §X.5 (organization-vs-enterprise sub-form) + §X.6 (Absent state question). Doc 572 Appendices B/C/D (independent dyads, temporal concurrency, universal-sibling lattice). Doc 573 Appendices A/B/C (requirements as canonical co-production, push/pull as proposal-direction taxonomy, service systems as canonical instances). Doc 445 Refinements A/B (paired V&V pulverization with two anchors, six-level rigor calibration). All amended in place. Docs 571, 572, 573, 445
Top-20 Distillations Ten more per-article distillations (System Validation, Stakeholder Needs, Architecture Design, Integration, Roles & Competencies, SE Performance Assessment, Risk, Decision Management, SE-PM, HSI). Confirms Doc 572 Appendix D at six instances; Doc 510 multi-keeper cluster reaches five instances; Doc 591 school-composition refinement candidate gets second instance (SE-PM); Doc 565 R23 (HSI seven-domain) closed as Appendix D instance; new candidates surfaced including forward-pulverization (Doc 445), school-maturity SIPE (Doc 541), Doc 1 ENTRACE generalization, Doc 314 worked example at engineering-decision layer. Docs 594-603

Queued (priority order)

Q1. Decide on the scaling path for per-article distillations. Two viable strategies:

  • (a) Full coverage: ~800 docs at the per-article granularity, fan-out via parallel agents per the Phase 3 pattern. Wall-clock estimate: a few hours of agent-minutes. Yields a complete corpus mirror at structural depth.
  • (b) Hybrid per Doc 576: Mode 1 reference-only for ~740 pages, Mode 4 hosted import + per-article distillation only for the ~30-60 editorial-dense pages identified by audit. Cheaper to maintain; less complete.

Recommendation pending keeper choice. If (a), the queued plan is Q1.a below. If (b), Q1.b below.

Q1.a. Full per-article distillation rollout (if path (a) chosen). Spawn parallel agents grouped by SEBoK part. Each agent produces ~20-100 distillations per part. Output: Docs 583 through approximately Doc 1300, organized by SEBoK part. Verify 100% template compliance and cross-link integrity at the end.

Q1.b. Editorial-dense audit pass (if path (b) chosen). Walk the existing Phase 3 docs (560-567) and the falsifier audit (Doc 568) and produce a list of the specific SEBoK pages cited by tier-tag, residual, or form-mapping. That list is the Mode 4 import candidate set. Stand up the hosted import for those pages only.

Q2. ~~Articulate the five-phase reformulation methodology as its own corpus form.~~ CLOSED 2026-04-30. Doc 583 — The Reformulation Methodology — formalizes the five phases (form inventory, macro-map, per-division reformulation, falsifier audit, synthesis), the three refinements absorbed from the SEBoK engagement (class-(c) clustering, per-article granularity, virtue-constraint reading on out-of-scope residuals), nine binding disciplines, and a refinement-discipline for absorbing future-deployment yields. The form is now deployable against other bodies of knowledge.

Q3. Practitioner-facing companion volume. Refine the Phase 3 reformulations (Docs 560-567) and the cluster formalizations (Docs 571-574) into a single short volume — Reading SEBoK Through the Corpus — that the practicing systems engineer can use alongside SEBoK. Output: one consolidated corpus document (or a small series) shaped for read-along use.

Q4. Resolve Doc 574's disposition definitively. Doc 571 Section X absorbed Cluster IV as the evacuated state of institutional ground; the substrate-consent residual (Doc 560 R4) is the surviving open question. Either reformulate substrate-consent as a degenerate ground state, articulate it as a separate form, or accept it as a residual the corpus does not yet reach. Decision unblocks Doc 574's status (currently "provisional").

Q5. Inverse direction reformulation. Which corpus forms does SEBoK have that the corpus does not? The forward direction (corpus reads SEBoK) is closed. The reverse direction would surface a symmetric set of residuals naming what SEBoK formalizes that the corpus has not yet articulated. Worth running once Q1's scaling path is decided and the apparatus is exercised at depth.

Q6. Apply the methodology to a second body of knowledge. Doc 576 named cybernetics (Mode 2 + Mode 3 + Mode 6), the INCOSE Handbook (Mode 2 + Mode 1, Mode 4 foreclosed by licensing), and the Pearl framework (Mode 3 + Mode 7) as candidates. Pick one and exercise the methodology against it as the second deployment after SEBoK. Validates the form's generalizability.

Deferred (with re-open conditions)

D1. Doc 575's full six-phase hosted import. Superseded by Doc 576's hybrid recommendation. Re-open when: keeper decides the hybrid is insufficient and full hosted import is warranted across most or all SEBoK pages.

D2. CMS-related Webflow App registration changes. Out of v0 scope per webflow-nexus deferral. Re-open when: CMS reformulation enters the engagement (either SEBoK-side, if SEBoK has CMS-relevant content, or webflow-nexus-side, when CMS becomes a v1+ requirement there).

D3. Marketplace / discovery surface for the SEBoK companion. Re-open when: the practitioner-facing companion (Q3) is mature enough to publish, and the keeper decides public distribution is the goal.

D4. Three-level Resume Vector hierarchy. Doc 581 §X.1 flagged the open question of whether RESOLVE itself should adopt one Resume Vector at the corpus root plus per-series Resume Vectors. Re-open when: a second corpus engagement adopts the Resume Vector pattern and the question of nested vectors becomes concrete.

D5. Multi-keeper trajectory authorship. Doc 581 §X.3 deferred. Re-open when: the SEBoK subsumption gains a co-keeper or external contributor who needs to read or write the trajectory.

III. Resume Protocol

To pick the SEBoK subsumption engagement back up in a future session:

  1. Read Doc 570 — SEBoK Through the Corpus — Canonical. The seed. Carries the conjecture, methodology, result, four extension surfaces, per-part findings.
  2. Read this document (Doc 582) — the trajectory. See where the work last stopped and what is queued.
  3. Read Doc 581 — The Resume Vector — if the apparatus is unfamiliar, to understand the pattern this trajectory inhabits.
  4. Pick the highest-priority queued item (currently Q1: scaling path decision). Don't reorder without a stated reason.
  5. Update this trajectory as work advances. Append to Done (commit-style, append-only, never edit backward). Re-prioritize Queued only with a stated reason. Move items to Deferred with explicit re-open conditions. The trajectory advances; the seed stays stable.

IV. Quick-Reference Map

Seed (canonical entry point): Doc 570 — SEBoK Through the Corpus — Canonical

Phase 1-5 derivation (now appendices of Doc 570 but preserved verbatim):

Cluster Formalizations (extension surfaces named by the engagement):

  • Doc 571 — Institutional Ground (with Section X four-state taxonomy)
  • Doc 572 — Lattice Extension of the Ladder (with Appendix A worked example)
  • Doc 573 — Co-Production at Sub-Rungs
  • Doc 574 — Authority Evacuation (provisional; absorbed as Doc 571's evacuated state)

Subsumption-Pattern Documents:

  • Doc 575 — Plan: Importing SEBoK Into the Corpus (superseded by Doc 576)
  • Doc 576 — Subsumption Modes for the Corpus (seven modes, hybrid recommendation)
  • Doc 577 — SEBoK Seed: Systems Engineering Through the Corpus (Mode 3 deployment)
  • Doc 578 — Three SEBoK Pilot Distillations (per-article granularity validation)

Form References this engagement composes with:

  • Doc 1 — ENTRACE Stack
  • Doc 314 — Virtue Constraints V1-V4 (apparatus addition during pilot work)
  • Doc 372 — Hypostatic Boundary
  • Doc 445 — Pulverization
  • Doc 490 — Novelty Calculus
  • Doc 510 — Substrate-and-Keeper Composition
  • Doc 530 — Rung-2 Affordance Gap
  • Doc 538 — Architectural School
  • Doc 541 — SIPE with Threshold
  • Doc 548 — Ontological Ladder of Participation (extended by Doc 572)
  • Doc 581 — The Resume Vector (the pattern this document instantiates)

V. Notes on the Engagement's Shape

The SEBoK subsumption is structurally distinct from a typical corpus engagement in three ways. The notes are recorded here so a future session reading the trajectory has the operational context:

(a) The engagement's substrate is external. Most corpus work has the corpus reading itself or reading something the keeper has produced. SEBoK is an external body of knowledge with its own authors, its own school, its own formalizing tradition. The reformulation discipline (Doc 557 C1-C7) was specifically tightened to honor this: form must do the work, no paraphrase, residuals first-class.

(b) The engagement produced corpus extensions. Most engagements apply existing forms. This one surfaced four new forms (Docs 571-574) plus refinements to Doc 548 (Lattice extension) and Doc 571 (state taxonomy added after pilot work). The trajectory should preserve the empirical link: each extension is anchored in specific SEBoK residuals, not invented in advance.

(c) The engagement produced a methodology candidate. The five-phase reformulation protocol is itself a candidate corpus form (Q2 above). Naming it would close the loop: the SEBoK subsumption produced both content (the reformulation) and method (the procedure). Future engagements with other bodies of knowledge can pick up the method without re-deriving.

Appendix: Originating Prompt

"Now let's prep for continuity with the SEBoK subsumption. Nailing down a trajectory will be helpful. I think we have a plan for this, but I don't think we have a trajectory."

(Doc 582 applies the Resume Vector pattern (Doc 581) to the SEBoK subsumption engagement. Doc 570 already serves as the engagement's seed; this trajectory and its embedded resume protocol complete the Resume Vector composition. The webflow-nexus engagement was the form's first deployment; this is the form's second.)

Referenced Documents

More in framework