Diff: infrastructure/edge-deployment
From e6d5f15 to e6d5f15
+0 / −0 lines
| Before | After |
|---|---|
| --- | --- |
| schema: foundry-topic-v1 | schema: foundry-topic-v1 |
| title: "Edge Deployment and Boundary Ingest" | title: "Edge Deployment and Boundary Ingest" |
| slug: edge-deployment | slug: edge-deployment |
| category: infrastructure | category: infrastructure |
| status: published | status: published |
| bcsc_class: public-disclosure-safe | bcsc_class: public-disclosure-safe |
| last_edited: 2026-04-30 | last_edited: 2026-04-30 |
| editor: pointsav-engineering | editor: pointsav-engineering |
| --- | --- |
| The platform moves all external network connections to the outermost boundary of the system before any data reaches the core processing rings. This architecture prevents common network-based attacks from reaching the financial ledgers and structured records held in Ring 2. | The platform moves all external network connections to the outermost boundary of the system before any data reaches the core processing rings. This architecture prevents common network-based attacks from reaching the financial ledgers and structured records held in Ring 2. |
| ## The problem with deep ingest | ## The problem with deep ingest |
| Standard server configurations process incoming internet traffic — email, HTTP, external API calls — inside the same execution environment that holds core data. A vulnerability in any ingest pathway grants an attacker access to the same memory space as the core records. Isolation cannot be added retroactively once a process has shared-memory access to another. | Standard server configurations process incoming internet traffic — email, HTTP, external API calls — inside the same execution environment that holds core data. A vulnerability in any ingest pathway grants an attacker access to the same memory space as the core records. Isolation cannot be added retroactively once a process has shared-memory access to another. |
| ## Boundary placement | ## Boundary placement |
| The platform positions all ingest processes at the physical and logical edge of the system. No inbound internet payload crosses into Ring 2 until it has passed through the Ring 1 boundary layer. Ring 1 is implemented as a set of Model Context Protocol (MCP) server processes, one per ingest channel (email, filesystem, people records, external input). | The platform positions all ingest processes at the physical and logical edge of the system. No inbound internet payload crosses into Ring 2 until it has passed through the Ring 1 boundary layer. Ring 1 is implemented as a set of Model Context Protocol (MCP) server processes, one per ingest channel (email, filesystem, people records, external input). |
| Each Ring 1 process: | Each Ring 1 process: |
| 1. Accepts the inbound payload from the external source. | 1. Accepts the inbound payload from the external source. |
| 2. Sanitizes the payload — removes transport metadata, validates structure, discards malformed input. | 2. Sanitizes the payload — removes transport metadata, validates structure, discards malformed input. |
| 3. Passes only the cleaned, structured record inward to Ring 2. | 3. Passes only the cleaned, structured record inward to Ring 2. |
| The public internet is never in direct contact with Ring 2 or Ring 3. Ring 2 has no outbound internet path except through service-egress. | The public internet is never in direct contact with Ring 2 or Ring 3. Ring 2 has no outbound internet path except through service-egress. |
| ## Effect on audit integrity | ## Effect on audit integrity |
| Because raw payloads are sanitized at the boundary and the cleaned records are what Ring 2 processes, the audit ledger in Ring 2 reflects what the system acted on — not what arrived at the wire. This separation is a precondition of the WORM ledger design: the ledger records clean, validated events, not raw network traffic. | Because raw payloads are sanitized at the boundary and the cleaned records are what Ring 2 processes, the audit ledger in Ring 2 reflects what the system acted on — not what arrived at the wire. This separation is a precondition of the WORM ledger design: the ledger records clean, validated events, not raw network traffic. |
| ## See also | ## See also |
| - [[worm-ledger-architecture]] — the WORM ledger that stores the sanitized records | - [[worm-ledger-architecture]] — the WORM ledger that stores the sanitized records |
| - [[service-email]] — Ring 1 ingest for email | - [[service-email]] — Ring 1 ingest for email |
| - [[compounding-substrate]] — the three-ring architecture in context | - [[compounding-substrate]] — the three-ring architecture in context |
| --- | --- |
| *Copyright © 2026 Woodfine Capital Projects Inc. Licensed under [Creative Commons Attribution 4.0 International](https://creativecommons.org/licenses/by/4.0/).* | *Copyright © 2026 Woodfine Capital Projects Inc. Licensed under [Creative Commons Attribution 4.0 International](https://creativecommons.org/licenses/by/4.0/).* |
| *Woodfine Capital Projects™, Woodfine Management Corp™, PointSav Digital Systems™, Totebox Orchestration™, and Totebox Archive™ are trademarks of Woodfine Capital Projects Inc., used in Canada, the United States, Latin America, and Europe. All other trademarks are the property of their respective owners.* | *Woodfine Capital Projects™, Woodfine Management Corp™, PointSav Digital Systems™, Totebox Orchestration™, and Totebox Archive™ are trademarks of Woodfine Capital Projects Inc., used in Canada, the United States, Latin America, and Europe. All other trademarks are the property of their respective owners.* |