documentation.pointsav.com — Home
PointSav Digital Systems builds the platform substrate for regulated small and mid-size businesses that need permanent, portable, and verifiable records on infrastructure they control. This wiki documents the platform's architecture, services, operating systems, and governance conventions. Articles are written for engineers, writers, designers, and readers with a financial interest in the platform. All content is published under CC BY 4.0.
Platform areas
Architecture Design principles, substrate patterns, and cross-cutting invariants that govern how the platform is built. Covers the three-ring stack, compounding substrate, AI routing, cryptographic audit, and the editorial pipeline. → Browse architecture
Services Autonomous services implementing Ring 1 and Ring 2 of the three-ring architecture: ingest, processing, search, egress, and the linguistic air-lock. → Browse services
Systems The operating systems at the foundation layer: ToteboxOS and its seL4-based capability model, orchestration, and tenant isolation. → Browse systems
Applications User-facing and internal applications built on the platform substrate, including the wiki engine that serves this site. → Browse applications
Governance Architecture decision records, licensing posture, contributor model, and compliance conventions. → Browse governance
Infrastructure Fleet deployment, cloud topology, and operational runtime. In preparation — articles are planned for this category. → Browse infrastructure
Company Corporate entities, organisational structure, and public disclosures. → Browse company
Reference Glossary, nomenclature matrix, and style guides for contributors across all audiences. → Browse reference
Help Onboarding guides for engineers, writers, and designers contributing to the platform and its documentation. → Browse help
Featured article
The Compounding Substrate is the architectural pattern PointSav builds and stewards. It answers a single structural question: how does a software platform let customers own their data, run on their own infrastructure, and compose AI in or out at will — while still benefiting from collective improvement without surrendering that ownership? Five structural properties combine to produce a substrate where every operational interaction generates training signal that compounds across deployments.
Featured articles represent the wiki's most complete and carefully reviewed content.
Recent additions
Most recently added or updated articles:
Latest updates
- 2026-04-29 — Category landing pages added for all nine platform areas
- 2026-04-29 — Home page and featured-article pin established
- 2026-04-27 — Initial platform documentation published
Other areas
Related resources outside this wiki:
- PointSav on GitHub — canonical engineering source;
pointsav/*organisations host the vendor-tier repositories. - Woodfine Management Corp. on GitHub — customer-tier mirror;
woodfine/*organisations host the downstream consumer repositories. - design-system — visual design tokens, component recipes, and brand conventions.
- factory-release-engineering — licensing matrix, contributor agreements, and governance policies.
Contributing
This wiki is published under CC BY 4.0. Content originates from the PointSav and Woodfine contributor flow. See contributing-as-engineer, contributing-as-writer, and contributing-as-designer for onboarding guides. These articles are planned for the help/ category; they will render as red links until written.
Articles are graded Complete, Core, or Stub based on lead length, section count, and reference completeness. Stub articles display an expansion notice and are the highest-priority contribution targets.
Corrections and additions follow the staging-tier commit flow described in style-guide-topic.
Provenance
This artifact derives from research captured at draft time. Q1 and Q2 are now closed; all open questions resolved before this refinement pass.
- Citations consulted: [external:en.wikipedia.org/wiki/Main_Page] (home-page structural patterns); [conventions/cluster-wiki-draft-pipeline.md §3] (velocity tiers, bilingual requirement); [conventions/bcsc-disclosure-posture.md Rule 1] (forward-looking labelling, company/ card and customer-wiki placeholder)
- Workspace references: [naming-convention.md §4, §7, §9] (nine-category set, MOC landing pattern, investor-audience design); [content-contract.md §1, §2, §4, §7, §9] (index.md as home, category: root, URL routing)
- Q1 resolved at refinement:
index.mdconfirmed as canonical home filename;category: rootrequired. - Q2 resolved at refinement:
featured-topic.yamlat repo root with schemaslug:(required) +since:(optional) +note:(optional). - Open editorial item deferred: verify the featured-TOPIC lead paragraph paraphrase against compounding-substrate §1–2 before the editorial pin is updated post-launch.