GovernanceIndex
Governance
This category covers the formal decision records, licensing posture, contributor model, and compliance requirements that govern how the PointSav platform is built, licensed, and changed over time. Governance articles are the written record of decisions that have been made and the rationale behind them; they are not aspirational statements.
The twelve binding architecture decisions are the most important entries in this category for technical due diligence and regulatory review: they define where automated processing stops and human authority begins, how data is separated, and where cryptographic keys must reside. Licensing articles explain the licence matrix that governs each repository and its contents. The contributor model article describes the three-tier structure through which code and content flow from contributors to the canonical platform. The BCSC disclosure posture article documents the requirements of Canadian securities continuous-disclosure obligations as they apply to the platform and its public documentation.
Start here for procurement, security, and compliance evaluation: Procurement overview — what a regulated buyer acquires, and the compliance properties enforced by architecture rather than contractual promise.
Institutional due diligence
Start here for procurement, security, and compliance evaluation.
- Procurement overview — What a regulated buyer acquires: customer-owned hardware deployment, no vendor-held data, no minimum-spend commitment, and the compliance properties enforced by architecture rather than contractual promise.
- Security overview — The platform's security posture: capability-based isolation, the Diode unidirectional command-flow standard, the Doorman AI boundary, the WORM audit ledger, and how each property is enforced by architecture.
- Compliance and continuous disclosure — How the platform produces continuous-disclosure-grade records and what that means for regulated buyers.
- bcsc-disclosure-posture — The BCSC continuous-disclosure posture and how the platform satisfies it by structure.
Formal decision records
- Architecture decisions — The twelve binding architecture decisions that constrain all future engineering; grouped by compliance weight, data separation, deployment custody, and operational integrity.
- SYS-ADR-07: zero AI in Ring 1 — Why the four Ring 1 boundary-ingest services are restricted to deterministic-only operations, and where AI inference is permitted to begin.
Licensing and contribution
- Three-tier contributor model — The three-tier contributor model: open community, paid integrators, and the canonical vendor tier; how work flows between them.
- Canadian-simple copyright posture — The Canadian-simple copyright posture: licence selection, attribution requirements, and the Canadian legal context.
- Legal and IP structure — The three-corporation IP topology: how intellectual property transfers from contributors to vendor to customer, with squash-and-merge as the atomic IP-transfer event.
Engineering sovereignty
- Sovereign replacement initiative — The formal program that records every third-party dependency in a structured ledger, enforces quarantine isolation, and retires each dependency when a native replacement reaches structural parity.
- Moonshot initiatives — The nine active engineering programs building native replacements for quarantined third-party dependencies, from the kernel layer up through the build toolchain.
- Sovereign airlock — The staged-commit protocol that enforces a structural separation between staging identities (commit authors) and canonical push identities, with no direct path between them.
Platform disciplines
- Ontological governance — The four throttled control ledgers and human-verification loop that prevent automated classification drift from undermining the integrity of long-lived institutional data.
- Anti-homogenization discipline — The architectural posture that resists AI writing assistants pulling contributors toward a single voice, defaulting to flagging rather than silent rewriting.
- API key boundary discipline — The rule that all external LLM API credentials belong exclusively at the gateway service and never at inference engines or downstream consumers.
- Favicon matrix and tab identity — The icon matrix governing visual identity across all platform surfaces: one distinct glyph per service, OS, and application, enforced at the asset-pipeline layer.
- Doctrine invention #7 — the integrity anchor — How the platform posts a monthly signed ledger checkpoint to the public Sigstore Rekor transparency log, giving auditors independently verifiable evidence outside the platform's own infrastructure.