Governance and Standards

• About PointSav Knowledge

  PointSav Knowledge is the engineering documentation wiki for the PointSav platform, serving engineers, architects, and institutional readers.

• Anti-homogenization discipline

  Anti-homogenization discipline is the architectural posture that resists AI writing assistants pulling contributors toward a single voice, by defaulting to flagging potential issues rather than silently rewriting text.

• API key boundary discipline

  The rule that all external LLM API credentials belong exclusively at the gateway service and never at inference engines.

• Architecture decisions

  Twelve binding architecture decisions — recorded commitments that govern how the PointSav platform is built and constrain all future engineering work on data handling, human oversight, system separation, and deployment custody.

• BCSC continuous-disclosure posture

  The operating discipline that treats every published artifact as potentially reviewable under Canadian securities continuous-disclosure obligations.

• Canadian-simple copyright posture

  The platform's intellectual property vests in a single Canadian parent holding company by operation of Canadian Copyright Act § 13(3), without inter-company assignment, and is designed to be evolved incrementally as the corporate structure matures.

• Compliance and continuous disclosure

  Compliance and continuous disclosure describes the regulatory frameworks the PointSav architecture addresses and the structural approach it takes to expose audit evidence continuously rather than through annual point-in-time certification cycles.

• Contact

  Contact information for PointSav Digital Systems and Woodfine Capital Projects Inc.

• Contributing to PointSav Knowledge

  How to propose additions, corrections, and new articles for PointSav Knowledge.

• Disclaimers

  Disclaimer and terms of use for PointSav Knowledge, the engineering documentation wiki for the PointSav platform.

• Doctrine Invention #7 — The Integrity Anchor

  How Foundry's anchor-emitter binary posts a signed ledger checkpoint to Sigstore Rekor each month, providing independently verifiable, third-party evidence of workspace state.

• Favicon matrix and tab identity

  The platform uses inline SVG data URIs for browser-tab favicons — eliminating a network call, scaling without pixelation on every display, and assigning two distinct vendor and customer marks to make the entity behind every tab unambiguous at a glance.

• Legal and IP structure

  The three-corporation topology governing intellectual property transfer from contributors to vendor to customer, with squash-and-merge as the atomic IP-transfer event and strict separation preventing unaudited code or operational-record exposure.

• Moonshot initiatives

  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.

• Ontological governance

  Ontological governance describes the four self-healing control ledgers that govern how service-content classifies and accumulates knowledge, and the human-verification loop that keeps extracted identity data accurate before it is permanently committed.

• PointSav Media Kit

  PointSav Digital Systems builds operating systems and services for regulated businesses

• Procurement overview

  What a regulated buyer acquires when deploying PointSav: hardware the customer owns outright, data the vendor never holds, no minimum-spend commitment, and compliance properties enforced by architecture rather than contractual promise.

• Security overview

  The platform's security posture: capability-based hardware isolation, the Diode unidirectional command-flow standard, the Doorman AI boundary, the WORM audit ledger, and how each property is enforced by architecture rather than by policy controls that can be misconfigured.

• Sovereign airlock

  The sovereign airlock is the staged-commit protocol that enforces a hard separation between work-in-progress staging identities and canonical repository identities — two staging authors for all commits, two admin identities for canonical pushes, with no direct path between them.

• Sovereign replacement initiative

  The Sovereign Replacement Initiative is the engineering governance program that tracks third-party dependencies, isolates them in quarantined component directories, and coordinates the active moonshot programs that build native replacements.

• SYS-ADR-07: Zero AI in Ring 1

  SYS-ADR-07 prohibits AI inference from all Ring 1 boundary-ingest services, enforcing deterministic-only operations at the WORM write path to guarantee auditability and composability.

• Three-tier contributor model

  The Three-Tier Contributor Model organises PointSav substrate contributors into Core (4–7 salaried engineers), Paid (50–100 contracted project contributors), and Open (10,000-plus public participants), with explicit mobility paths between tiers.