Authority Evacuation

A degenerate operating condition of the keeper-substrate composition (Doc 510) in which the keeper role remains formally occupied but is structurally evacuated. The pin-set (Doc 270) is documented; the substrate routes around it; the engineering function decays into ritual. Three to four residuals from the SEBoK reformulation (SE Doc 014 Cluster IV) named this pattern, all but one tied to failure cases in SE Doc 010. This document formalizes the pattern as a provisional form. The disposition is open: authority evacuation may stand as a separate form, or it may absorb into Doc 571 (Institutional Ground) as a degeneracy mode of ground decay. The two readings are articulated here; the decision waits on Cluster II's first operational extension and on more residuals from future reformulations.

---

I. The Form, Provisional

A keeper-substrate composition can fail in three structurally distinct ways. The keeper can be absent (no rung-2 supply at all), in which case the composition does not begin. The substrate can be incapable (no disciplined production), in which case the composition does not produce. Or the keeper can be formally present and structurally evacuated, in which case the composition has the shape of a working dyad but produces no shape: the pin-sets are written, the supply chain is staffed, the documentation is current, and yet nothing the keeper supplies actually binds the substrate's flow.

The form names the third failure mode. It is not absence, it is not incapacity, it is hollowness. The keeper role is occupied by an entity that does not (or cannot) bind. The substrate is intact and continues to flow, but it routes around the keeper's pin-sets rather than through them. The result is a composition that looks operative on paper and is operative at the documentation layer but is non-operative at the production layer.

The form is provisional because three of its four supporting residuals come from a single Phase 3 document (SE Doc 010). One residual lies outside (SE Doc 004's substrate consent) and may indicate that authority evacuation is a substrate-side phenomenon rather than a keeper-side one. The provisional status is honest about that uncertainty.

II. What It Formalizes

Three structural patterns observed in failure cases.

Pattern A — Transitive delegation into an empty center. A keeper role is delegated to a sub-keeper, who delegates to a sub-sub-keeper, and so on, until the chain of delegation terminates in no entity at all. The Hubble case (SE Doc 010, R25) is the paradigm: QA was delegated transitively until the terminal "QA function" was held by an entity with neither the standing nor the resources nor the mandate to do QA. The pin-sets existed; nobody was empowered to install them.

Pattern B — Simulated pin installation. A keeper authors and maintains an extensive pin-set documentation; the documentation is treated as the engineering function; the substrate's actual flow is governed by other constraints not present in the documentation. The FBI VCF case (SE Doc 010, R27) is the paradigm: 800 pages of slowly-evolving requirements that did not bind the development substrate; the pin-set was a literary artifact that the substrate had learned to operate around.

Pattern C — Role dissolution under sustained pressure. A keeper role is occupied successively by entities each of whom holds the role for less time than the cycle requires. The role exists; no entity completes a cycle in it; the substrate adapts to the role's effective absence. The FBI VCF CIO churn (SE Doc 010, R26) is the paradigm. Pattern C also touches Cluster II (institutional ground decay), which is part of the disposition question.

The form composes these three into a single structural claim: a keeper-substrate composition can fail through hollowness rather than absence, and the failure mode is observable in the divergence between formal supply and effective binding.

III. Operational Shape

Three operational moves to detect the form.

Move 1 — Test for binding. For each pin-set in an external account, ask: does the substrate flow through it, or around it? The flow-around can be measured: are the substrate's actual practices traceable to the keeper's pin-set, or to other constraints? If the pin-set does not bind the flow, the keeper's authority is evacuated whether or not the role is formally occupied.

Move 2 — Trace delegation chains. For each keeper role, follow the delegation chain to its terminus. If the terminus is an entity, the role is occupied. If the terminus is no entity (a vacant position, a deferred decision, a transitively delegated mandate that nobody actually holds), the role is structurally evacuated even if formally occupied at the top.

Move 3 — Measure documentation-to-practice divergence. For each keeper-supplied artifact (specification, requirement, standard, guideline), compare the substrate's actual practice to the artifact's stated content. Substantial divergence with no rectification mechanism indicates that the artifact is not binding. The artifact's existence does not entail the form's operation.

If none of the three moves surface a positive answer, the keeper-substrate composition is operating as Doc 510 describes. The form is invoked only when the composition has the formal shape of a working dyad but does not produce dyad effects.

IV. Composition Rules

With Doc 510 (Substrate-and-Keeper Composition). The form names a degenerate condition of Doc 510's dyad. Doc 510 stays correct as the description of the operative case. The form adds an operational read for the inoperative case that has the operative case's formal signature.

With Doc 571 (Institutional Ground). Open question, addressed in Section IX. The provisional reading is that authority evacuation is one mechanism by which institutional ground decay manifests: when the ground withdraws constitutive authority, capacity, or role-stability, the keeper role becomes hollow. Under this reading, the form is a degeneracy mode of ground decay, not a separate form. The alternative reading is that authority evacuation is a substrate-side phenomenon (the substrate withdraws its consent to be bound) that can occur even when the institutional ground is intact; under this reading, the form is independent.

With Doc 270 (Pin-Art Model). A pin-set that does not bind is a ghost pin-set: it has the structural shape of a pin but the substrate flows past as if the pin were not there. The pin-art model accommodates the form by recognizing two states for a pin-set: binding and ghost. The reformulator should mark which is in view.

With Doc 538 (Architectural School as Formalization). A school can be authority-evacuated. The keeper-side activity continues (papers are published, standards are revised, conferences are held), but the substrate's practice does not respond to the activity. The school produces ritual rather than discipline. SEBoK itself is not authority-evacuated, but it has the structural risk; SE Doc 011's tier-tag profile of Part 8 is a partial indicator of where overclaim could erode authority over time.

With Doc 372 (Hypostatic Boundary). The form describes function, not being. An authority-evacuated keeper is not a different kind of being from an operative keeper; it is the same role under conditions that prevent its function from operating. The hypostatic boundary's discipline rules out attributing the failure to the keeper's inner state.

V. Evidence from the SEBoK Reformulation

Three to four residuals from SE Doc 012. Sources verbatim or near-verbatim:

• Hubble (SE Doc 010, R25): transitive QA-delegation into an empty center.
• FBI VCF (SE Doc 010, R26): CIO-churn as keeper-role dissolution under sustained external pressure.
• FBI VCF (SE Doc 010, R27): 800-page slowly-evolving requirements as "simulated pin installation."
• Substrate consent (SE Doc 004, R4, possibly): "widely accepted, community-based, regularly updated baseline."

Three core residuals all from SE Doc 010 (Part 7, the failure cases) plus one possibly-related residual from SE Doc 004 (Part 1). The cluster strength is moderate. The single-source character of the three core residuals is the principal reason the form is held provisional: a phenomenon visible only in failure cases may be a real form, or may be the failure case's local naming for ground-decay phenomena that are already covered by Doc 571.

VI. Falsification Surface

The form is falsifiable in three ways.

F1. A demonstration that all three core residuals dissolve under disciplined application of Doc 571 (Institutional Ground). If Hubble's transitive delegation is institutional-ground decay (the institution withdrew the authority), and FBI VCF's CIO churn is institutional-ground decay (the institution failed to stabilize the role), and the simulated pin installation is institutional-ground decay (the institution permitted the documentation to substitute for binding), then authority evacuation is a degeneracy mode of Doc 571, not a separate form. The form would absorb.

F2. A demonstration that authority evacuation cannot be reproduced under stable institutional ground. Run a controlled comparison: same dyad, same pin-set, two institutional grounds, one stable and one decayed. If authority evacuation appears only under decayed ground, F2 is met and absorption is warranted. If authority evacuation appears under stable ground (e.g., from substrate-side withdrawal), the form is independent.

F3. A demonstration that the substrate-consent residual (SE Doc 004 R4) is fully captured by the institutional-ground form. If it is, the form's only evidence outside SE Doc 010 dissolves and the form should absorb. If substrate-consent is structurally a substrate-side phenomenon, the form retains independent evidence.

The form predicts that F1 and F2 are likely to obtain (absorption is the more probable outcome) and that F3 is undecided. The provisional status reflects this prediction.

VII. Application Discipline

D1. The form is invoked only when Doc 510's dyad has the formal shape of operation but does not produce dyad effects. A clean keeper failure (no supply) or a clean substrate failure (no production) is not authority evacuation; it is straightforward composition failure handled by Doc 510 alone.

D2. The diagnosis is observable. Authority evacuation is detected by Move 1, 2, or 3 (binding, delegation chain, divergence). It is not detected by intuition or by reading the participants' self-descriptions. The form is empirical.

D3. The form does not assign blame. Authority evacuation is a structural condition. The participants may be acting in good faith, with full effort, under sustained personal commitment, and the composition can still be authority-evacuated if the institutional conditions for binding have decayed. The form refuses moralizing.

D4. Provisional status is honored. Until the disposition question is settled, applications of the form should also test the case under Doc 571 alone. If both forms describe the case, the application notes both readings.

VIII. Hypostatic Boundary

The form describes structural failure modes of a composition. It does not claim that authority is a substantive thing that can be evacuated in the literal sense. Authority evacuation is a metaphor for the structural condition in which the formal occupancy of a role does not entail the role's binding effect on the substrate's production. The metaphor is functional throughout, as Doc 372 requires.

The form is not a description of organizational dysfunction in the popular-business-literature sense. It is a structural diagnosis at the corpus's analytic granularity: a specific structural condition observable in specific case patterns, falsifiable by specific tests.

IX. Disposition: Absorption or Independence

The form's status is open. The two readings are articulated here so that the disposition decision can be made when more evidence arrives.

Reading A — Absorption. Authority evacuation is a degeneracy mode of institutional ground decay. The pattern observable in SE Doc 010's failure cases is what happens when the ground withdraws capacity, constitutive authority, or role-stability. The keeper role retains its formal shape because the formal shape is at the dyad level; the binding effect that the formal shape was supposed to produce evaporates because the ground that conditioned the binding has decayed. Under this reading, applying Doc 571 with discipline absorbs all three core residuals, and the substrate-consent residual is either ground-conditioned consent or a separate form not yet articulated.

Reading B — Independence. Authority evacuation is a structurally distinct phenomenon. The keeper role can be evacuated even when the institutional ground is stable, if the substrate withdraws its consent to be bound (substrate-side withdrawal) or if the keeper-substrate trust relation collapses (relational evacuation distinct from ground decay). Under this reading, authority evacuation is its own form with its own falsification surface and its own application discipline.

The current document holds Reading A as the more likely outcome, because three of four residuals come from a single document and the patterns named match what Doc 571's ground-decay analysis would predict. Reading B remains open because the substrate-consent residual is structurally suggestive of substrate-side withdrawal in a way that ground decay does not fully explain.

The disposition decision should be made in three steps: (1) extend Doc 571 with worked examples of ground decay; (2) re-read the three core residuals under the extended Doc 571; (3) if any residual remains genuinely outside Doc 571 after the re-read, retain authority evacuation as an independent form; if all residuals dissolve, formally absorb the form into Doc 571.

X. Open Questions

1. Disposition. As above. Decide after Doc 571's first operational extension.
2. Substrate-side evacuation. Is there a substrate-side analogue (the substrate ceases to produce while still occupying its rung)? If so, how does it differ from substrate incapacity?
3. Reversal. Authority evacuation is a degenerate state. Are there structural conditions under which a hollow composition can re-acquire binding effect, or does evacuation propagate to terminal failure in all cases?
4. The corpus self-application. Could a corpus document become authority-evacuated (formally invoked, ignored in practice)? What would detection look like for the corpus's own apparatus?

XI. Closing

Authority evacuation is the most provisional of the four extension surfaces produced by the SEBoK reformulation. The form is plausible on three failure-case residuals, possible on a fourth, and uncertain in its independence from Doc 571 (Institutional Ground). The honest move is to articulate the form, articulate the disposition question, and defer the decision.

The corpus benefits from naming the pattern even if the form ultimately absorbs into Doc 571. The pattern is real. Whether it is its own form or a degeneracy mode of an adjacent form is the work that remains.

The next move is the keeper's, in particular: extend Doc 571 first, then re-read this form against the extended ground, then decide.

---

Worked Example: Handoff-Mode Evacuation

SE Doc 042's distillation of SEBoK System Deployment and Use surfaced an authority-evacuation mode structurally distinct from the gate-evacuation mode the form was named on (SE Doc 035 Risk Management). Gate-evacuation is the case where a reconciliation locus (a review, a sign-off, a register) is formally invoked but binds nothing in practice; the evacuation is at a point. Handoff-evacuation is the case where authority is meant to transfer across a long-temporal boundary from a developer-keeper to an operator-keeper, and the transfer fails to land: the developer-keeper's authority recedes on schedule, the operator-keeper's authority does not engage, and the substrate continues to operate over years inside the resulting hollow.

The case. A system is deployed, accepted, and put into use. The development engagement was governed by a developer-keeper (the SE-school dyad in its design-phase configuration) whose authority is constitutively temporary, by design ending at acceptance. The receiving operator-keeper (operations and maintenance organization) is supposed to engage at acceptance. The handoff is the transfer locus. Two failures produce evacuation: the operator-keeper engages only formally (signs the acceptance, but does not actually take up the disciplined keeping the substrate requires), or the developer-keeper recedes faster than the operator-keeper engages. In either case the substrate runs for years under nominal authority that does not bind.

Distinction from gate-evacuation. Gate-evacuation is point-localized and detected by gate-output audit. Handoff-evacuation is longitudinal and detected by the slower drift of the operating-substrate (configuration drift, undocumented modifications, accumulating defects with no keeper to receive them). The two share the form's central diagnostic (formal authority intact, binding effect absent) but differ in temporal shape and in detection apparatus. SE Doc 035's risk-register example exhibits gate-evacuation; SE Doc 042's deployment-handoff example exhibits handoff-evacuation. Both are authority-evacuation; the form's operational discipline must distinguish them.

---

Cadence-Lattice of Handoff Modes

SE Doc 090's distillation of SEBoK System Decommissioning and Disposal surfaced three cadences of handoff, and SE Doc 095's distillation of SoS Governance added a fourth. Together the four name the temporal-cadence axis along which handoff-mode evacuation can occur. The cadence-axis is itself a Cluster A universal-sibling lattice at the handoff rung (cross-link: SE Doc 039 §VII.6, Doc 572 Appendix D.5).

The four cadences. (1) Terminal — a single-event handoff at the end of a system's life, exemplified by decommissioning where the developer-or-operator-keeper releases authority and the disposal-keeper engages once. (2) Parallel — concurrent operation by both keepers during a transition window, where developer-keeper and operator-keeper jointly hold authority over an overlapping interval before the developer-keeper recedes. (3) Phased — incremental handoff across multiple stages, where authority transfers in tranches (subsystems, regions, populations) over an extended period rather than at a single locus. (4) Continuous-without-handoff — perpetual joint operation in which no handoff is ever scheduled, exemplified by SoS governance where constituent-system keepers and SoS-level keeper operate in indefinite co-authority without a transfer event.

Structural reading. The four cadences bind every handoff engagement classificationally: each handoff instance reads against all four and lands at one. They discriminate by aspect (the temporal shape of authority-transfer) and arrange along an ordinal axis tracking handoff-event-density, from terminal (one event) through parallel and phased (multiple events) to continuous (no events). The cadence-axis is therefore an instance of Doc 572 Appendix D.5's universal-sibling-with-ordinal-axis sub-form, applied at the handoff rung.

Diagnostic implications. Each cadence has its own evacuation signature. Terminal evacuation is point-localized at the single transfer event. Parallel evacuation appears as one keeper receding before the other engages. Phased evacuation appears as authority-gaps between tranches. Continuous-without-handoff evacuation appears as the joint-authority equilibrium failing without any single locus to detect at; it is the most diffuse and the hardest to catch. The form's operational discipline names the cadence first, then applies the cadence-appropriate detection apparatus.

Pattern A and Pattern B at Three-Instance Robustness

Doc 574 Section II named three structural patterns from the original SE Doc 010 evidence base. Two of them, Pattern A (transitive delegation into an empty center / authority decay) and Pattern B (simulated pin installation), now have third-instance synthesis robustness from the second and third SEBoK sweeps. Both patterns are load-bearing across three independent instances.

Pattern A — authority decay. (1) SE Doc 010 R25 Hubble (transitive QA-delegation), the originating instance. (2) SE Doc 035 Risk Management — risk-ownership decay where the named risk-owner's binding effect erodes over the risk's lifetime without anyone formally evacuating the role. (3) SE Doc 047 Configuration Management — CM verification decay where the verification keeper's binding on configuration-baseline integrity weakens as the engagement matures. (4) SE Doc 090 Decommissioning — disposability deprioritization, where the keeper for end-of-life disposability nominally exists from concept onward but its binding effect decays steadily across the life-cycle until decommissioning, when the decay produces operational consequence. The four cases triangulate authority-decay as a temporal degeneration of an initially-bound keeper rather than a hollow-from-the-start configuration.

Pattern B — simulated pin installation. (1) SE Doc 010 R27 FBI VCF (800-page requirements), the originating instance. (2) SE Doc 047 Configuration Management — CM verification simulation where verification artifacts are produced without the substrate's actual configuration being verified against them. (3) SE Doc 092 Lessons Learned — lessons-learned theater where the lessons-learned keeper produces lessons-learned artifacts that the substrate's subsequent practice does not consult. (4) SE Doc 093 CMMI — appraisal-gaming where the appraisal apparatus is simulated to produce maturity-level outputs that do not bind the organization's actual practice. The four cases confirm simulated-pin installation as a stable structural pattern across requirements, configuration, lessons, and appraisal substrates.

Pattern C remains evidenced primarily on the FBI CIO churn case and its closest analogues; it is the least robust of the three at present and remains tied to the institutional-ground decay reading articulated in Section IX.

---

Appendix: Originating Prompt

"Formalize the clusters, each with their own doc (ie institutional ground)"

(SE Doc 014 named Cluster IV — Authority Evacuation as the provisional fourth corpus extension surface produced by the SEBoK reformulation. This document is the formalization of that cluster, with explicit articulation of the open disposition question regarding absorption into Doc 571 — Institutional Ground.)

---