Table of contents
This text gives the formal mathematical treatment of the captain concept. The three defining properties — scope singularity, anti-override authority, and non-delegable duties — are all answered by the same underlying structure: the captain’s position in the fiber as the unique doubly-stable witness.
Non-delegable duties as unique H* witnesses
A duty is non-delegable when its discharge requires the captain specifically:
and substituting another agent for does not produce under the governing normative system.
Delegation does not transfer accountability because delegating to gives , which is outside RelationalHistoryFixedFiber: it may be σ-settled (recognized as having occurred) but not Δ-settled (forward-stable as having been discharged by the right party). Future extensions of the history can always revisit whether was the correct party, whereas ’s performance is Δ-fixed — no future extension can re-open that question.
Scope singularity as history separation
Scope singularity (no two captains share the same scope simultaneously) is history separation at the command level: no two command positions within the same institutional history have constitutionally identical fibers.
At the ground level this is an imposed condition — the RelationalHistoryFixedPresheafAutomorphismRigidityAxiom requires it as an axiom. At the automorphic directed comonad level (a mature institution at hull level), scope singularity becomes a theorem: the aperiodicity of the quasicrystalline constitutional fiber guarantees that for any two command positions , their fiber algebras at and are non-isomorphic. No permutation of command histories maps one command scope to another. The scope is uniquely the captain’s not by stipulation but because the institution’s constitutional structure is aperiodic.
Anti-override authority as infrastructure dependency direction
The infrastructure spec (Invariant 7): “The only morphisms between P and S are those of π (going from P toward S). There are no morphisms from S into P.”
Applied to the captain’s scope: (the captain’s domain) is the substrate; external normative claims from superiors, commercial principals, and other parties constitute the practice that the scope enables. The anti-override domain is the sub-domain from which no morphisms flow inward from — external parties cannot override decisions within because the dependency direction is outward only.
A superior wishing to exercise authority within must perform a new installation act and assume command — converting themselves from -level into -level. The anti-override protection is the structural consequence of the infrastructure dependency direction: authority flows from the command scope outward, never from outside the scope inward.
| Infrastructure role | Captain reading | Direction |
|---|---|---|
| Substrate | Captain’s operational scope | Defines enabling conditions |
| Practice | External normative claims | Must project onto via ; cannot morphism into |
| Enabling projection | Installation act | The morphism that constitutes command |
| Dependency direction | Anti-override protection | No morphisms from into within |
| Installed-base order | Voyage history order | Past command decisions restrict forward fiber coherence |
Proposition
All three invariants are instances of the same formal condition: the captain’s command section RelationalHistoryFixedFiber at the focal history is:
- Aperiodically unique — no permutation of the institutional history maps to an isomorphic copy at another command position (scope singularity = history separation)
- An infrastructure substrate — external parties are in the practice layer and must project onto via installation to gain authority (anti-override = infrastructure dependency direction)
- The unique H-witness* for each non-delegable duty — the doubly-stable proposition that only ’s occupancy produces (non-delegability = uniqueness of the doubly-stable section)
Source. History separation at automorphic directed comonad level from Relational Universe Automorphic Directed Comonad History Separation §Theorem for . Infrastructure dependency direction from Infrastructure §Seven Invariants, Invariant 7. Non-delegability characterization formalized from existing nuclear machinery.