Skip to content
PointSav Digital Systems

Three-ring architecture

← All revisions

9d8533d5 · PointSav Digital Systems ·

chore(architecture): convert bare concept references to wikilinks

View the full record as of this revision →

@@ -45,14 +45,14 @@ This separation is a structural choice, not a design preference. A regulated buy
| Ring | Service | Purpose | Required at all tiers? |
|---|---|---|---|
| 1 | service-fs | Immutable Ledger (WORM append-only) | Required |
| 1 | service-people | Identity Ledger | Optional |
| 1 | service-email | Communications Ledger | Optional |
| 1 | [[service-people]] | Identity Ledger | Optional |
| 1 | [[service-email]] | Communications Ledger | Optional |
| 1 | service-input | Generic document ingestion | Optional |
| 2 | service-extraction | Deterministic parser (no AI, per SYS-ADR-07) | Required |
| 2 | service-content | Taxonomy Ledger and knowledge graph | Required |
| 2 | service-search | Search index (Tantivy, DARP-compliant) | Required |
| 2 | service-egress | Physical release valve | Required for output |
| 3 | service-slm | AI Gateway — the Doorman | Optional |
| 2 | [[service-extraction]] | Deterministic parser (no AI, per SYS-ADR-07) | Required |
| 2 | [[service-content]] | Taxonomy Ledger and knowledge graph | Required |
| 2 | [[service-search]] | Search index (Tantivy, DARP-compliant) | Required |
| 2 | [[service-egress]] | Physical release valve | Required for output |
| 3 | [[service-slm]] | AI Gateway — the Doorman | Optional |
| 3 | (slm-yoyo) | Multi-cloud GPU burst orchestrator | Optional |

## Ring 1 — Boundary Ingest
@@ -65,7 +65,7 @@ Because Ring 1 is per-tenant, each tenant's data lives in a separate service ins

## Ring 2 — Knowledge and Processing

Ring 2 reads from Ring 1 and produces structured knowledge: parsed records, knowledge graphs, classified entities, search indexes. All Ring 2 processing is deterministic. SYS-ADR-07 prohibits AI from writing to the knowledge graph or the structured record stores; those paths are exclusively Ring 2's.
Ring 2 reads from Ring 1 and produces structured knowledge: parsed records, knowledge graphs, classified entities, search indexes. All Ring 2 processing is deterministic. [[sys-adr-07|SYS-ADR-07]] prohibits AI from writing to the knowledge graph or the structured record stores; those paths are exclusively Ring 2's.

The practical effect: Ring 2 output is reproducible given the same Ring 1 input. An audit that questions a classification can replay the deterministic parse against the unchanged Ring 1 ledger and get the same result. No AI variance enters the authoritative record.

@@ -110,4 +110,4 @@ For deployments that include Ring 3, the read-only constraint means the determin
1. PointSav Doctrine §XIV, The Compounding Substrate — claims #14–#18; Three-Ring composition as the structural basis for Optional Intelligence Layer (claim #16).
2. `conventions/three-ring-architecture.md` — workspace canonical specification.
3. `conventions/compounding-substrate.md` — meta-pattern the rings implement.
4. SYS-ADR-07 — structured data never routes through AI; enforces the Ring 2 / Ring 3 boundary.
4. [[sys-adr-07|SYS-ADR-07]] — structured data never routes through AI; enforces the Ring 2 / Ring 3 boundary.
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 →