Applications
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.
Knowledge and editorial applications
The wiki engine, the marketing surface, and the design-intent articles that describe their reader-facing chrome.
- app-mediakit-knowledge — 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 — 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 — How the documentation home page inherits Wikipedia's structural conventions and extends them for engineering and financial-community readers.
- wikipedia-leapfrog-design — 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-launch-2026-04-27 — The April 2026 TLS launch of
documentation.pointsav.com: serving stack, placeholder posture, and verification commands.
Location intelligence applications
The GIS analytics engine, the platform article that frames it alongside the rendering layer, and the user-experience design intent.
- app-orchestration-gis — 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 — 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.
- app-console-input — 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.
- app-privategit-workbench — A browser-based three-column file editor included in os-privategit; for working with archive files without a terminal session.
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.
- building-design-system-bim — Design-system tooling adapted for BIM and real-property workflows.
- flat-file-bim-leapfrog — How Building Information Modelling is handled as flat-file ISO 19650 records rather than hosted database instances.
- aec-interface-conventions — Interface conventions for AEC surfaces that BIM applications inherit and extend.
- property-manager-bim-gap — The gap between BIM authoring tools and property-manager workflows, and how the application surfaces close it.
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
All 14 articles in this area, A–Z
- app-console-email — communications cartridge2026-06-14
app-console-email is the F3 communications cartridge for os-console. It provides inbox listing, message reading, and compose-and-send, operating through service-email as the Comm Diode between the operator and external correspondents.
- applications/app-console-input
- app-console-keys — console chassis and F-key framework2026-06-14
app-console-keys is the always-installed base chassis of os-console. It provides the Cartridge trait that all console modules implement, the F-key navigation strip, the status bar, and the machine-based authorization client.
- app-console-slm — inference infrastructure monitoring console2026-06-09
A terminal user interface cartridge for the operator console that displays the live state of the AI inference infrastructure — model health, remote GPU node status, priority queue depth, organizational graph entity count, and daily spend — with keyboard controls for routing policy and per-tier kill switches.
- applications/app-mediakit-knowledge
- app-mediakit-marketing — WordPress-leapfrog marketing landing server2026-06-01
app-mediakit-marketing is a Rust web server that delivers marketing landing sites using the WordPress vocabulary over a sovereign, flat-file architecture. Two live deployments serve home.woodfinegroup.com and home.pointsav.com.
- GIS orchestration application2026-05-08
app-orchestration-gis is the stateless spatial analytics engine that performs linear-geometry calculations and coordinate mapping to produce the Woodfine co-location rankings and the interactive map at gis.woodfinegroup.com — a pure function that holds no canonical data and can be re-provisioned by pointing a fresh instance at the immutable data layer.
- Browser developer workbench2026-05-29
app-privategit-workbench is a browser-based file editor included in the os-privategit host operating system, presenting a three-column interface — file tree, viewer, and editor — for working with plain-text and source files across the cluster archive tree without a terminal session.
- applications/bim-and-real-property-surfaces
- documentation.pointsav.com goes live — 2026-04-272026-05-25
The April 2026 TLS launch of documentation.pointsav.com: serving stack, placeholder posture, BCSC disclosure rationale, and verification commands.
- Knowledge wiki home page — design intent2026-05-25
How the documentation.pointsav.com home page inherits Wikipedia's structural conventions and extends them for engineering and financial-community readers.
- Location intelligence platform2026-05-08
The PointSav Location Intelligence platform is a customer-owned flat-file GIS application designed for retail cluster analysis and strategic site selection — composed of app-orchestration-gis (the analytics engine) and pointsav-gis-engine (the rendering layer), with every dataset, algorithm, and rendering decision under the customer's direct control.
- Location intelligence UX design philosophy2026-05-19
The PointSav Location Intelligence interface is engineered for decision-maker clarity, using a Conclusion-First design philosophy that communicates site-selection confidence through visual hierarchy and structural grading rather than raw data volume.
- Wikipedia leapfrog design — muscle memory and 5% headroom2026-05-25
What the app-mediakit-knowledge wiki engine inherits from Wikipedia, what it adds beyond it, and what the 5% leapfrog headroom means for readers and engineers.