The Doctrine
Doctrine provides the decision rules that govern all operations. When facing uncertainty, doctrine resolves it. When resources are constrained, doctrine prioritizes. When success criteria are ambiguous, doctrine defines them.
Core Doctrine
Decision Rules for Operations
Interfaces Before Implementation
Define how systems connect before building systems. Interface specifications take precedence over component design. Integration points are standardized across all domains.
Implication
Components can be replaced without system disruption. Third-party systems can integrate through published interfaces. Scaling occurs at interface boundaries.
Measure or Abandon
Every operation must have defined KPIs. If an activity cannot be measured, it cannot be managed and should not be undertaken. Measurement precedes expansion.
Implication
Decisions are data-driven. Emotional attachment to failing projects is eliminated. Resources flow toward measurable success.
Stop/Scale Logic
Every initiative has predetermined stop conditions and scale triggers. Stop conditions halt operations before catastrophic resource expenditure. Scale triggers authorize expansion only upon demonstrated success.
Implication
Failure is bounded. Success is rewarded with resources. Middle states—neither failing nor succeeding—are resolved through predetermined timelines.
Ethical Constraints
Operations must maintain planetary stability and responsible expansion. Debris generation is minimized. Environmental impact is monitored. Human safety is non-negotiable.
Implication
Short-term gains that create long-term liabilities are rejected. Sustainability is a hard constraint, not an optimization target.
Key Performance Indicators
What Gets Measured
Manufacturing
- Tons produced per month
- Unit cost vs. Earth equivalent
- Uptime percentage
- Feedstock utilization rate
Logistics
- Cargo throughput (kg/month)
- Transit time reliability
- Propellant efficiency
- Route utilization
Debris Recovery
- Tons recovered per year
- Capture success rate
- Feedstock yield percentage
- Corridor clearance rate
Lunar Operations
- Water ice extracted (kg/month)
- Regolith processed
- Local material utilization
- Crew sustainment days
Safety
- Incident rate
- Near-miss frequency
- System redundancy level
- Emergency response time
Financial
- Revenue per domain
- Cost per kg delivered
- ROI by initiative
- Cash runway months
Interface Rules
How Systems Connect
All interfaces are documented in public specifications before implementation begins.
Interface changes require version increments and backward compatibility for minimum two versions.
Cross-domain interfaces are standardized. Domain-specific interfaces may vary within published constraints.
Physical interfaces use standard connectors and protocols. Custom interfaces require explicit exception approval.
Data interfaces follow published schemas. Schema evolution follows semantic versioning.
Hard Constraints
Non-Negotiable Boundaries
Manufacturing platforms are never sited in high-debris orbits.
Human safety systems maintain minimum redundancy levels regardless of cost.
Debris-generating activities are prohibited without capture and remediation plans.
Financial obligations to crew (compensation, evacuation, medical) are pre-funded.
Environmental monitoring continues even when operations are paused.
Doctrine Requires Principles
Doctrine provides decision rules. Principles provide the underlying logic. Systems architecture shows how doctrine and principles manifest in operational infrastructure.