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.
Knowledge and editorial
- 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.
GIS and location intelligence
- 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) and pointsav-gis-engine (rendering), with every dataset, algorithm, and rendering decision under customer control.
Input and ingest
- 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.
Domain applications
- 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.
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