Platform Services

@@ -11,7 +11,7 @@ index_type: thematic
index_scope: services
status: active
bcsc_class: public-disclosure-safe
last_edited: 2026-08-06
last_edited: 2026-08-22
editor: pointsav-engineering
paired_with: _index.es.md
---
@@ -34,7 +34,7 @@ Per-tenant boundary services. Each runs as a separate process per tenant and exp
<!-- AUTO-GENERATED MEMBERSHIP: DO NOT EDIT BELOW — regenerate from index_group: ring-1-boundary-ingest -->
- [[service-fs]] — The filesystem service: append-only WORM ledger, per-tenant storage root, the foundation every other Ring 1 service writes to — architecture, durability, and the SEC 17a-4(f)/eIDAS/SOC 2 compliance posture it enables by construction.
- [[service-email]] — Email ingest: SMTP and IMAP, sanitised payloads, append-only Maildir on local block storage.
- [[service-people]] — Identity ledger: person records, role assignments, and the Anchor-Claim-Socket data model that never overwrites state.
- [[service-people]] — Identity ledger: an F2 os-console surface exposing append, lookup, and regex-based email-scan tools over MCP, backed by a store that rejects conflicting identities.
- [[service-input]] — Document intake at the Ring 1 boundary: parses PDF, Markdown, DOCX, and XLSX by format detection, normalizes to a `ParsedDocument`, and hands off to service-fs for WORM ledger commit.
<!-- END AUTO-GENERATED -->

@@ -45,7 +45,7 @@ Deterministic processing services. Each reads from Ring 1 and produces structure
<!-- AUTO-GENERATED MEMBERSHIP: DO NOT EDIT BELOW — regenerate from index_group: ring-2-knowledge-and-processing -->
- [[service-extraction]] — The central Ring 2 traffic controller: strips proprietary formatting, constructs Entity Bundles, assigns transaction IDs, routes to deterministic services or to service-slm.
- [[service-content]] — The Gravity Engine: reads raw payloads from a Totebox, runs them against an institutional taxonomy, generates the structured documents an organisation publishes.
- [[service-search]] — Full-text search on Tantivy: per-tenant sharding, microsecond retrieval, no active database process required.
- [[service-search]] — Full-text search on Tantivy: a designed but not yet built inverted-index service — only a description exists today, no source code.
- [[service-egress]] — Physical release valve: structured records leave the platform only through this service.
- [[archetypes-and-chart-of-accounts]] — The institutional taxonomy: eleven archetypes and a Chart of Accounts that classify personnel and documents by structural position and functional role.
<!-- END AUTO-GENERATED -->
@@ -57,9 +57,9 @@ One service spans Ring 3. It reads from Ring 2 and produces proposals a human re
<!-- AUTO-GENERATED MEMBERSHIP: DO NOT EDIT BELOW — regenerate from index_group: ring-3-ai-gateway -->
- [[service-slm]] — The Doorman: AI routing across local, burst, and external compute tiers; audit ledger on every call; every API key held at this boundary.
- [[service-slm-yoyo-operational]] — Operational state of service-slm and the Yo-Yo GPU burst VM: Tier A/B configuration, apprenticeship brief queue, idle-shutdown cost ceiling.
- [[service-slm-totebox-sysadmin]] — How service-slm becomes the operational assistant for Totebox deployments: ten operational task families, four-stage pipeline from corpus capture to per-tenant LoRA adapters.
- [[service-slm-graph-store-migration]] — The DataGraph's live property graph: nightly LadybugDB rebuild via grammar-constrained entity extraction through the Doorman, gated by human approval before any write.
- [[yoyo-daily-enrichment-cycle]] — The Yo-Yo GPU burst VM's daily batch window: enriches the DataGraph and accumulates DPO training pairs under a fixed schedule and hard cost cap.
- [[service-slm-totebox-sysadmin]] — A planned direction for service-slm as a Totebox sysadmin assistant, built on the real, already-operational apprenticeship training pipeline — the specific task taxonomy is proposed, not yet registered.
- [[service-slm-graph-store-migration]] — The DataGraph's live property graph: nightly LadybugDB rebuild via grammar-constrained entity extraction through the Doorman, writing directly with no review step of its own.
- [[yoyo-daily-enrichment-cycle]] — The Yo-Yo GPU burst VM's daily batch window: two phases, DataGraph rebuild and (once fully enabled) adapter training — training currently runs in marker-only mode.
<!-- END AUTO-GENERATED -->

## Specialist and domain services
@@ -69,14 +69,14 @@ Services built for specific platform capabilities.
<!-- AUTO-GENERATED MEMBERSHIP: DO NOT EDIT BELOW — regenerate from index_group: specialist-and-domain-services -->
- [[service-business-clustering]] — Turns raw retail data into commercial clusters: parent-child spatial schema, one commercial entity per site.
- [[service-places-filtering]] — Filters civic and institutional infrastructure to retain only regional-grade facilities for GIS tier rankings.
- [[service-wallet-settlement]] — Wallet and direct payment settlement infrastructure.
- [[service-wallet-settlement]] — Wallet and direct payment settlement: a planned per-tenant accounting ledger design, not yet built.
- [[message-courier]] — Headless web-automation engine bridging internal identity ledgers with external web portals.
- [[fs-anchor-emitter]] — Signed WORM ledger checkpoints at hourly cadence, anchored to Sigstore Rekor on a monthly schedule for external auditability.
- [[service-fs-data-lake]] — Flat-file data lake for the GIS pipeline: raw geospatial points from open sources, no ETL step.
- [[template-ledger]] — Distributes approved email templates to the operator's mail environment; eliminates version drift between template design and execution.
- [[editorial-pipeline-three-stages]] — Three-stage proofreading pipeline ordered by cost: deterministic banned-vocabulary scan, LanguageTool mechanical pass, then a generative rewrite routed through the inference layer.
- [[private-git-paid-customer-endpoint]] — The binary release server behind software.pointsav.com: verifies Ed25519 license tokens and streams compiled binaries, holding no payment records or signing keys.
- [[service-pointsav-link]] — The hot-pluggable adapter connecting an os-* Subject node to a PointSav fleet: not installed by default, with a clean-severance failure mode.
- [[service-pointsav-link]] — A named but unbuilt design concept for a fleet-connecting adapter; no corresponding package exists in the monorepo today.
- [[service-vm-fleet]] — The placement and registry service for the PPN VM resource pool: two-pass placement algorithm and heartbeat-driven node state.
- [[service-vm-tenant]] — The customer-facing tenant proxy for the PPN VM resource pool: authentication, namespace isolation, quota enforcement, and an immutable audit trail.
<!-- END AUTO-GENERATED -->