Moonshot initiatives

Moonshot initiatives are long-running engineering programs that replace quarantined third-party dependencies with internally built, formally verifiable equivalents — reducing vendor lock-in and shrinking the platform's external attack surface.

The platform actively tracks third-party engineering debt in a structured ledger. Foreign architectural components are contained in isolated directories, called quarantined component silos, until a moonshot initiative delivers a native replacement. The Sovereign Replacement Initiative is the governance program that coordinates these efforts. Each moonshot initiative is a distinct engineering effort targeting one dependency class; completion is defined as structural parity with the component it replaces, at which point the native implementation physically supersedes the quarantined directory.

Technical debt tracking

The ledger records every identified foreign dependency alongside its isolation status and the associated moonshot initiative, if one has been opened. Entries remain active until replacement is confirmed. This gives auditors and contributors a live picture of the platform's outstanding external exposure.

Quarantine protocol

Until a legacy component can be replaced, it is physically isolated into a quarantined component silo (for example, vendor-azure-auth or vendor-microsoft-graph) — each carrying a "Quarantined Foreign Component" warning banner in its README.md. No foreign code runs inside a capability sandbox behind these banners yet; the directories today are placeholders marking the boundary, not active containment.

Replacement pipeline

For every quarantined dependency, the engineering team opens a corresponding moonshot directory (for example, moonshot-database or moonshot-kernel). Work in these directories targets native, formally verified implementations in Rust. Once a moonshot component reaches structural parity with its quarantined counterpart, it replaces the isolated directory. The ledger entry closes at that point.

Initiative areas and real status

Twenty-three moonshot directories exist as of this writing. The table below tracks the nine initiatives with the most engineering activity or governance visibility to date — three carrying substantial, active engineering, and six that are named directories with a 4-file Cargo scaffold and no implementation yet. The remaining fourteen directories are not yet individually assessed in this article:

Initiative	Target dependency	Status
moonshot-index	External search and index backends	Active — a working trigram substring index plus a planned ranked-search layer, pure std, no external dependency
moonshot-sel4-vmm	Commodity virtual machine monitor	Active — a real seL4 protection-domain runtime with multiple working binaries, including a confirmed HTTP call over VirtIO-net DMA
moonshot-toolkit	External build and CI tooling	Active — a working Rust build orchestrator that produces a bootable system image
moonshot-database	External database engine	Scaffold — directory and Cargo manifest exist, no implementation
moonshot-gpu	Cloud GPU inference services	Scaffold — directory and Cargo manifest exist, no implementation
moonshot-hypervisor	External hypervisor layer	Scaffold — directory and Cargo manifest exist, no implementation
moonshot-kernel	Commodity Linux kernel	Scaffold — directory and Cargo manifest exist, no implementation. The seL4 formally verified microkernel is the intended eventual replacement for the quarantined systemd/Linux dependency recorded in ADR-08, but that replacement work currently lives in moonshot-sel4-vmm, not here
moonshot-network	External network control plane	Scaffold — directory and Cargo manifest exist, no implementation
moonshot-protocol	Proprietary communication protocols	Scaffold — directory and Cargo manifest exist, no implementation

Completion status of each initiative is tracked in the Sovereign Replacement Initiative ledger.

Vendor and customer roles

• The Vendor (PointSav Digital Systems) maintains the moonshot ledgers and engineers the native replacements.
• The Customer (MCorp) audits the pipeline to verify progress toward operational independence.

See also

• Sovereign Replacement Initiative — governance program that coordinates these engineering efforts
• seL4 microkernel substrate — the formally verified microkernel that moonshot-kernel and moonshot-sel4-vmm target
• Architecture decisions — ADR-08 records the systemd quarantine that moonshot-kernel is designed to close
• Ontological Governance — the taxonomy governance that provides nomenclature for quarantined components
• Verification Surveyor — the audit agent that tracks completion status of each initiative