Skip to content

Diff: governance/moonshot-initiatives.es

From 3cabaa1 to 3cabaa1

+0 / −0 lines
BeforeAfter
--- ---
schema: foundry-doc-v1 schema: foundry-doc-v1
title: "Moonshot Initiatives" title: "Moonshot Initiatives"
slug: moonshot-initiatives slug: moonshot-initiatives
category: governance category: governance
type: topic type: topic
quality: stub quality: stub
short_description: "Moonshot initiatives are active engineering programs that build native replacements for quarantined third-party dependencies, with the goal of eliminating vendor lock-in and reducing the platform's external attack surface over time." short_description: "Moonshot initiatives are active engineering programs that build native replacements for quarantined third-party dependencies, with the goal of eliminating vendor lock-in and reducing the platform's external attack surface over time."
status: pre-build status: pre-build
last_edited: 2026-04-30 last_edited: 2026-04-30
editor: pointsav-engineering editor: pointsav-engineering
cites: [] cites: []
paired_with: moonshot-initiatives.es.md paired_with: moonshot-initiatives.es.md
--- ---
# Moonshot Initiatives # 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. > 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 Foundry platform actively tracks third-party engineering debt in The Foundry platform actively tracks third-party engineering debt in
a structured ledger. Foreign architectural components are contained a structured ledger. Foreign architectural components are contained
in isolated directories, called quarantined component silos, until in isolated directories, called quarantined component silos, until
a **moonshot initiative** delivers a native replacement. The a **moonshot initiative** delivers a native replacement. The
[[sovereign-replacement-initiative|Sovereign Replacement Initiative]] [[sovereign-replacement-initiative|Sovereign Replacement Initiative]]
is the governance program that coordinates these efforts. Each is the governance program that coordinates these efforts. Each
moonshot initiative is a distinct engineering effort targeting one moonshot initiative is a distinct engineering effort targeting one
dependency class; completion is defined as structural parity with dependency class; completion is defined as structural parity with
the component it replaces, at which point the native implementation the component it replaces, at which point the native implementation
physically supersedes the quarantined directory. physically supersedes the quarantined directory.
## Technical debt tracking ## Technical debt tracking
The ledger records every identified foreign dependency alongside its The ledger records every identified foreign dependency alongside its
isolation status and the associated moonshot initiative, if one has isolation status and the associated moonshot initiative, if one has
been opened. Entries remain active until replacement is confirmed. been opened. Entries remain active until replacement is confirmed.
This gives auditors and contributors a live picture of the This gives auditors and contributors a live picture of the
platform's outstanding external exposure. platform's outstanding external exposure.
## Quarantine protocol ## Quarantine protocol
Until a legacy component can be replaced, it is physically isolated Until a legacy component can be replaced, it is physically isolated
into a quarantined component silo (for example, `vendor-azure-auth` into a quarantined component silo (for example, `vendor-azure-auth`
or `vendor-microsoft-graph`). These directories act as structural or `vendor-microsoft-graph`). These directories act as structural
boundaries. The foreign code may not execute outside a tightly boundaries. The foreign code may not execute outside a tightly
controlled capability sandbox. Isolation prevents a dependency from controlled capability sandbox. Isolation prevents a dependency from
spreading coupling into adjacent platform layers. spreading coupling into adjacent platform layers.
## Replacement pipeline ## Replacement pipeline
For every quarantined dependency, the engineering team opens a For every quarantined dependency, the engineering team opens a
corresponding moonshot directory (for example, `moonshot-database` corresponding moonshot directory (for example, `moonshot-database`
or `moonshot-kernel`). Work in these directories targets native, or `moonshot-kernel`). Work in these directories targets native,
formally verified implementations in Rust. Once a moonshot component formally verified implementations in Rust. Once a moonshot component
reaches structural parity with its quarantined counterpart, it reaches structural parity with its quarantined counterpart, it
replaces the isolated directory. The ledger entry closes at that replaces the isolated directory. The ledger entry closes at that
point. point.
## Vendor and customer roles ## Vendor and customer roles
- The Vendor (PointSav Digital Systems) maintains the moonshot - The Vendor (PointSav Digital Systems) maintains the moonshot
ledgers and engineers the native replacements. ledgers and engineers the native replacements.
- The Customer (Woodfine Management Corp.) audits the pipeline to - The Customer (Woodfine Management Corp.) audits the pipeline to
verify progress toward operational independence. verify progress toward operational independence.
## See Also ## See Also
- [[sovereign-replacement-initiative|Sovereign Replacement Initiative]] - [[sovereign-replacement-initiative|Sovereign Replacement Initiative]]
- [[ontological-governance|Ontological Governance]] - [[ontological-governance|Ontological Governance]]
- [[verification-surveyor|Verification Surveyor]] - [[verification-surveyor|Verification Surveyor]]
## References ## References
--- ---
*Copyright © 2026 Woodfine Capital Projects Inc. Licensed under [Creative Commons Attribution 4.0 International](https://creativecommons.org/licenses/by/4.0/).* *Copyright © 2026 Woodfine Capital Projects Inc. Licensed under [Creative Commons Attribution 4.0 International](https://creativecommons.org/licenses/by/4.0/).*
*Woodfine Capital Projects™, Woodfine Management Corp™, PointSav Digital Systems™, Totebox Orchestration™, and Totebox Archive™ are trademarks of Woodfine Capital Projects Inc., used in Canada, the United States, Latin America, and Europe. All other trademarks are the property of their respective owners.* *Woodfine Capital Projects™, Woodfine Management Corp™, PointSav Digital Systems™, Totebox Orchestration™, and Totebox Archive™ are trademarks of Woodfine Capital Projects Inc., used in Canada, the United States, Latin America, and Europe. All other trademarks are the property of their respective owners.*