Developer Guide Index
The Developer Guide Index lists the task-oriented how-to guides for the PointSav platform, organised by developer concern. Each guide covers a specific task a developer performs when building with or deploying the platform. For the underlying architecture that each guide draws on, follow the article wikilinks within each guide.
Internal operator runbooks for the Woodfine fleet deployment are not listed here — they are operational documents for provisioning and maintenance, not public developer guides.
Getting started
These guides cover the first steps for a developer new to the platform — setting up device authorization and opening a working session.
- Pair a new device — register a new device and assign it a pairing tier (INPUT, USER, or INTERFACE)
- Open your first Totebox session — open a scoped working session in a Totebox Archive and navigate the session lifecycle
Machine authorization
These guides cover the cryptographic device pairing that controls platform access.
- Pair a new device — the core pairing workflow; covers all four pairing types (ADMIN, INPUT, USER, INTERFACE) and how to verify and revoke
For the authorization model that underpins pairing, see Machine-based authorization and Pairing as permission.
Integration & data
These guides cover consuming platform data and connecting external applications.
- Build a co-location map — authenticate against the GIS tile API and render tier-coloured cluster markers in MapLibre
- Authenticate binary downloads — verify Ed25519-signed binary releases from the private distribution endpoint
- Federate archives via content mounts — declare a secondary content mount in
knowledge.tomland access federated articles across instances
Self-hosting
These guides cover deploying and running platform components on operator-controlled infrastructure.
- Self-host a deployment — provision a named deployment instance, start the gateway, and connect it to the upstream platform
- Run local SLM inference — start the local SLM service, verify the Doorman health endpoint, and submit inference requests from os-console
See also
- Machine-based authorization — the machine-based authorization model underlying all platform access
- Totebox orchestration as the development environment — the session orchestration model that governs how Totebox Archives are used
- MediaKit knowledge application — the wiki engine serving this documentation instance