Skip to content
PointSav Digital Systems

Revision as of · f1451e9c

Historical revision — this record as it stood on 20 June 2026, not the current version. View the current record →

Sovereign replacement initiative

The Sovereign Replacement Initiative is the formal program that records every foreign dependency in a structured ledger, enforces quarantine isolation until a native replacement is ready, and retires the dependency once the replacement reaches structural parity.

Any platform that has passed through a digital-transformation phase inherits third-party architectural components it did not design. Reliance on those components — proprietary cloud authentication providers, foreign GPU drivers, commercial graph APIs — creates a structural risk: if a third-party vendor changes its terms of service or deprecates an API, the dependent platform either adapts under pressure or halts. The Sovereign Replacement Initiative is the platform's response to this class of risk. It is a physical ledger of outstanding third-party dependencies and an active engineering pipeline designed to eliminate them systematically.

Technical debt ledger

The initiative maintains a ledger that records each identified third-party dependency alongside its isolation status and the corresponding moonshot initiative, if one has been opened. The ledger is a live document: entries are added when new dependencies are identified and closed when a native replacement achieves structural parity. Auditors and contributors can read the ledger to see the platform's current external exposure.

Quarantine protocol

Until a native replacement is available, a legacy component is physically isolated into a quarantined component silo (for example, vendor-azure-auth or vendor-microsoft-graph). These directories are structural containers that restrict the foreign code to a controlled capability boundary. The isolation prevents coupling from spreading into adjacent platform layers while the replacement is under development.

Moonshot pipeline

For every quarantined dependency, the engineering team opens a corresponding moonshot directory (for example, moonshot-database or moonshot-kernel). These are active development efforts targeting native, formally verifiable implementations. Once a moonshot component achieves structural parity with its quarantined counterpart, it replaces the isolated directory and the ledger entry closes.

Completion criteria

A ledger entry closes when the associated moonshot initiative achieves structural parity with the quarantined component it replaces. Structural parity has three conditions:

  1. Functional coverage. The native implementation covers all platform use-cases currently served by the quarantined component.
  2. Physical supersession. The quarantined vendor-* directory is deleted from the repository. No source references to the replaced component remain.
  3. Formal verification target. For kernel-layer components, the native implementation satisfies the platform's formal verification requirement (seL4-compatible, memory-safe, no buffer overflow). For application-layer components, the platform's standard test coverage and audit-ledger integration requirements are met.

Until all three conditions are satisfied, the quarantine remains active and the ledger entry stays open.

Relationship to ADR-08

Architecture Decision 8 formally records the systemd init system as a quarantined dependency — the dependency the platform accepts while the moonshot-kernel initiative builds toward the seL4 microkernel replacement. The Sovereign Replacement Initiative is the governance mechanism that gives ADR-08 operational force: without the ledger, the quarantine is a statement of intent; with the ledger, it is a tracked commitment with a named completion path.

Vendor and customer roles

The initiative operates across the vendor-customer structure:

  • Vendor (PointSav Digital Systems). Maintains the ledger, engineers the native replacements, and owns the moonshot directories.
  • Customer (MCorp). Audits the pipeline to verify progress toward operational independence from legacy external providers.

See also

Important Information

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is a trade name of Woodfine Capital Projects Inc. ("Woodfine"). PointSav does not itself offer, sell, or solicit any security. Any securities offering associated with Woodfine's real-property direct-hold solutions is made exclusively by Woodfine, and only by means of the applicable Private Placement Memorandum.

No investment advice. This wiki's content is provided for engineering, operational, research, and development purposes. Nothing on this wiki constitutes investment advice or a solicitation to invest in any Woodfine partnership or direct-hold solution.

Intellectual property. The PointSav name, trade name, wordmark, and marks, together with all current and future PointSav- and Totebox-branded products, services, and offerings — and the software, source code, documentation, design system, and all related materials — are proprietary to Woodfine and its affiliates, except for components identified as open source. No rights are granted except as expressly set out in a written license or agreement. See TRADEMARK.md in this repository for the full trademark notice.

Open source components. Portions of the platform are made available under permissive open-source licenses identified in the accompanying repository. Use of those components is governed by their respective license terms.

No warranty; informational use. Content on this wiki is provided for general informational purposes only and does not constitute a representation, warranty, or commitment with respect to product functionality, availability, pricing, or roadmap. Some articles describe planned or intended features, capabilities, and milestones — language such as "planned," "intended," "targeted," "may," and "expected" marks this forward-looking content, which is subject to change and does not constitute a commitment regarding future performance.

Confidentiality. Where an article describes an operational or deployment detail that is not intended for public disclosure, that article is not published on this wiki. Content here is general-purpose engineering documentation, not customer-specific configuration.

Jurisdiction. Woodfine Capital Projects Inc. is organized in British Columbia, Canada. References to the Sovereign Data Foundation on this wiki describe a planned or intended initiative only, not a current equity holder or active governance body.

Changes to this notice. PointSav may update this notice from time to time; the version posted on this page governs.

Not a filing system. This wiki is not a securities filing system, an electronic disclosure repository, or a substitute for SEDAR+ or any other regulatory filing system. Formal securities filings are made through the applicable regulatory filing system, not through this wiki.

Full disclaimer. This notice supplements, and does not replace, the full Disclaimers article. In the event of any conflict, the full Disclaimers article governs.

Read the full disclaimer →