Governance and Standards
← All revisions
docs(governance): update category landing to reference architecture-decisions
@@ -5,34 +5,27 @@ slug: _index category: governance status: active bcsc_class: public-disclosure-safe last_edited: 2026-04-29 last_edited: 2026-05-15 editor: pointsav-engineering --- ## Governance This category covers the formal decision records, licensing posture, contributor model, and compliance conventions 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. 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. Architecture decision records (ADRs) document specific design choices that carry system-wide consequences — each ADR states the decision, the context, the options considered, and the reasoning. 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. Compliance conventions document the posture required by applicable regulatory instruments, including continuous-disclosure obligations under Canadian securities law. The twelve binding [[architecture-decisions|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. ## Articles in this category - [[architecture-decisions]] — The twelve binding architecture decisions that constrain all future engineering on the platform; grouped by compliance weight, data separation, deployment custody, and operational integrity. - [[contributor-model]] — The three-tier contributor model: open community, paid integrators, and the canonical vendor tier; how work flows between them. - [[canadian-simple-copyright]] — The Canadian-simple copyright posture: licence selection, attribution conventions, and the Canadian legal context. - [[sovereign-replacement-initiative]] — The replacement-initiative governance posture for sovereign AI deployments under the PointSav substrate. <!-- ENGINE: this list is editorial in iteration-1; iteration-2+ generates it from category-directory file listing once PL.7 chunked-migration moves articles into category subdirectories. --> - [[bcsc-disclosure-posture]] — The British Columbia Securities Commission continuous-disclosure posture and how the platform satisfies it by structure. - [[canadian-simple-copyright]] — The Canadian-simple copyright posture: licence selection, attribution requirements, and the Canadian legal context. - [[compliance-and-continuous-disclosure]] — How the platform produces continuous-disclosure-grade records and what that means for regulated buyers. ## See also - [Wiki home](/) - [Architecture](/architecture/) - [Company](/company/) - [Infrastructure](/infrastructure/) - [Reference](/reference/) <!-- EDITORIAL NOTE: PL.7 chunked normalization sweep will migrate root-prefixed TOPICs into this category subdirectory. Until migration lands, the existing root TOPICs render at their current URLs (topic-<slug>.md); this landing references them by current slug. -->