User Manual — learn by doing
Interactive, use-case-based guides — “I want to make the bus announce the next stop”, “fix a mispronounced stop name”, “prove what passengers heard” — each walking the real screens step by step, with progress you can tick off and links straight into the apps.
The Handbook — consolidated documentation
Every source document stitched into one continuous document, from the product overview down to architecture, security, licensing and the test report. Assembled live from the repo's sources on every request, so it is always current.
Presentations & leave-behinds
Product Deck
The 28-slide product story — problem, platform, architecture, innovation, trust. Arrow keys to present, O for the slide grid, N for presenter notes, ?print to export a PDF.
Stakeholder Master Deck
One presentation for every audience — Executive, Operators, Architecture, Software and Commercial chapters.
Showcase Presentation
Product demo deck with screenshots and the animated architecture build-up.
System Overview & Architecture
Context diagram, components, engine pipeline, MQTT contract and deployment models.
Product Leaflet
Printable A4 marketing leaflet — value proposition, how it works, license packages.
One-Pager Slide
Single 16:9 leave-behind — capabilities, runtime path, MQTT topics and modules.
Software Team Briefing
Engineering what/how deck — scope, runtime path, contracts, code map and workstreams.
Built with AI — By the Numbers
The measured record of the AI-assisted build: 31 days, ~194 AI hours, 13B tokens, ≈$10.4k of compute — with charts, per-model cost and the measurement method.
Product & delivery
Product Backlog — descriptions & acceptance criteria
Every one of the 96 features as a ready-to-paste work item: user-story description plus numbered, testable acceptance criteria, grouped into 15 epics and traceable to the PRD requirement IDs. Written to be the source for ADO tickets and the test cases derived from them (one criterion → at least one test case).
How it fits together
PRD says what the product must
do (numbered requirements). The backlog restates each as a
ticket with acceptance criteria. The
Functional Specification holds the
deeper baseline criteria and the defect register, and the
Test Report is the measured verification behind
the claims. Backlog IDs mirror PRD IDs — F-LED-03
is PRD-LED-03.
Source documents (raw Markdown)
The handbook is generated — edit the sources, never the built output. Each chapter above is one
of these files at the repo root; npm run docs
regenerates the distributable copies.
OVERVIEW.md SCREENS.md FUNCTIONAL-SPEC.md ARCHITECTURE.md SCALING.md ON-VEHICLE.md HANOVER-SIGNS.md SECURITY.md LICENSE-PACKAGING.md TEST-REPORT.md README.md
Where things live
Source docs sit at the repo root and are indexed in docs/README.md.
Screenshots live under docs/media/; the
presentation HTML files under docs/showcase/;
internal notes under docs/notes/.
This is the only place the docs are published — the engine dashboard's Documentation link
comes straight back here.