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 — Single-binary Rust wiki engine serving documentation.pointsav.com — a view over a markdown tree where git commits are canonical and the running binary is disposable.
• app-mediakit-marketing — agent-authored marketing landing server — Rust web server delivering marketing landing sites from typed page manifests — AI authors via MCP, a human approves before anything publishes. Serves home.woodfinegroup.com and home.pointsav.com.
• Knowledge wiki home page — design intent — How the documentation.pointsav.com 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, BCSC disclosure rationale, and verification commands.
• Proofreader console — Terminal content cartridge for the service-proofreader pipeline — operators submit text, review findings, and record a binary accept/reject verdict that feeds the 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 Python data pipeline that produces the Woodfine co-location rankings and interactive map — cluster geometry rebuilt on a nightly schedule from source datasets, published as static map tiles.
• Location intelligence platform — The full location intelligence platform: a nightly app-orchestration-gis pipeline paired with an interactive rendering layer; 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 distinct operational domain — a separate customer-tier design system, a real Chart of Accounts placement, and BIM-specific console surfaces still at the research stage.

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

Financial and construction tools

A family of owner-held ledger tools sharing one double-entry design: accounting, construction cost/schedule/quality control, and payroll. All three now have real, running code — tool-accounting's ledger engine, tool-construction's cost/schedule/reporting engine, and tool-payroll's first report — though the depth of what's built varies widely across the three.

• The financial and construction tool family — a shared design across three products — How the three tools relate as one product family: the shared double-entry design, the one-way data feeds between them, and the shared free/paid architecture boundary.
• tool-accounting — double-entry ledger and audit-ready financial statements — A flat-file, owner-held double-entry ledger producing audit-ready financial statements; core engine and a real CLI toolchain of report binaries, verified against real historical multi-entity data.
• tool-construction — construction cost, schedule, and quality ledger — A flat-file, owner-held ledger for construction cost, schedule, and quality control; the core engine now runs as a real CLI, producing cost estimate and schedule reports for a live pilot — estimate-stage only, no console yet.
• tool-payroll — jurisdiction-aware payroll and statutory remittance — A jurisdiction-aware payroll and statutory-remittance engine; its first real report (a division-level Payroll Register) is built and running, but gross-to-net pay, pay frequency, and remittance remain design-only.

See also

• Platform Services — the service layer that applications build on
• Operating Systems — the operating systems that host applications
• How It's Built — the three-ring model and the customer-ownership principles
• Design and Brand — the token and component vocabulary the application chrome inherits