ApplicationsIndex

Applications sit above the three-ring service layer. They consume deterministic data and optional AI output from the rings and present it through a defined interface. An application holds no canonical data — it is a view over the service layer, and can be re-provisioned without data loss by pointing a fresh instance at the immutable data underneath. The articles in this category cover both the named applications themselves and the design-intent material that explains how each surface is composed.

Each application here corresponds to an app-* directory in the monorepo and inherits the Three-ring architecture separation; none holds the authoritative record. Reader-facing chrome and design rationale articles are gathered alongside the application articles so that operators evaluating a surface can move from the engineering article to the design intent without leaving the category.

Start here: MediaKit knowledge application — the wiki engine rendering the very documentation you're reading now, and the clearest example of this category's core pattern: an application as a throwaway view over canonical, git-committed data.

Knowledge and editorial applications

The wiki engine, the marketing surface, and the design-intent articles that describe their reader-facing chrome.

• MediaKit knowledge application — The single-binary Rust wiki engine that renders PointSav's engineering documentation; a view over a Markdown tree where the git commits are canonical and every running binary is throwaway derived state.
• app-mediakit-marketing — agent-authored marketing landing server — Multi-tenant marketing landing pages from a single statically-compiled Rust binary; WordPress.org muscle memory at the operator-facing URL, sovereign infrastructure underneath.
• Knowledge wiki home page — design intent — How the documentation home page inherits Wikipedia's structural conventions and extends them for engineering and financial-community readers.
• Wikipedia leapfrog design — muscle memory and 5% headroom — What the wiki engine inherits from Wikipedia, what it adds beyond it, and what the five-percent leapfrog headroom means for readers and engineers.
• documentation.pointsav.com goes live — 2026-04-27 — The April 2026 TLS launch of documentation.pointsav.com: serving stack, placeholder posture, and verification commands.
• Proofreader console — The operator console for the service-proofreader editorial pipeline: review structured findings, accept or reject rewrites, and record the verdicts that feed the platform's apprenticeship corpus.

Location intelligence applications

The GIS analytics engine, the platform article that frames it alongside the rendering layer, and the user-experience design intent.

• GIS orchestration application — The stateless spatial analytics engine for linear-geometry calculations and co-location ranking; a pure function that holds no canonical data and can be re-provisioned by pointing a fresh instance at the data layer.
• Location intelligence platform — The full location intelligence platform: app-orchestration-gis (analytics) paired with the rendering engine; every dataset, algorithm, and rendering decision under customer control.
• Location intelligence UX design philosophy — The Conclusion-First design philosophy: ranked tier conclusions rather than individual data points, so users see the most defensible commercial nodes at national zoom before drilling into individual operators.

Input and developer surfaces

The structured-input gate that admits external files to a Totebox, and the browser workbench for working with archive files outside a terminal.

• Console input application — The F12 surface in os-console: the structured input gate through which raw external files enter a Totebox before being sealed into the verified ledger.
• Browser developer workbench — A browser-based three-column file editor included in os-privategit; for working with archive files without a terminal session.
• app-console-keys — console chassis and F-key framework — The always-installed base chassis of os-console: defines the Cartridge trait every F-key module implements, the F-key navigation strip, the status bar, and the machine-based-authorization client the other cartridges connect through.
• app-console-email — communications cartridge — The F3 communications cartridge for os-console: inbox, message reading, and compose-and-send through service-email's Comm Diode egress path.
• app-console-slm — inference infrastructure monitoring console — The F9 terminal cartridge showing live AI inference infrastructure state — model health, GPU node fleet, queue depth, and daily spend — for the operator running a Totebox.

Domain applications

Surfaces dedicated to a specific operational domain — Building Information Modelling and real-property workflows.

• BIM and real property surfaces — How PointSav treats Building Information Modelling as a first-class operational domain, with dedicated design-system tooling and ISO 19650 record-keeping discipline.

Additional planned articles for this domain — design-system tooling for BIM, the flat-file ISO 19650 approach, AEC interface conventions, and the gap between BIM authoring tools and property-manager workflows — are not yet written.

See also

• Services — the service layer that applications build on
• Systems — the operating systems that host applications
• Architecture — the three-ring model and the customer-ownership principles
• Design system — the token and component vocabulary the application chrome inherits