C4 — Context
Helm in its environment. The actors and systems Helm interacts with.
Data flow diagrams
Sequence diagrams for the four most important cross-component flows.
Deployment topology
How Helm is deployed per-shop, how shops are isolated, how this scales from 1 to 50 shops.
Security model
Authentication, authorization, session management, secrets, audit trail.
AI integration
How Helm uses Claude — the Support bubble, RAG against the bible, conversation memory, the budget.
Offline architecture
Store-and-forward POS — what works when the shop's internet drops, how writes queue, how reconnect drains them.
Build versioning
Every build of the Worker has a frozen version string. Every audit row records the build that produced it. Forensic queries answer "which build was running when this happened" from the chain alone.
Global search palette
A single Cmd-K-style overlay that searches across customers, inventory, and service tickets in one query, returning typed + grouped results.
Search engine (FTS5)
Best-in-class text search — SQLite FTS5 per domain, BM25 ranking, synonyms, click telemetry, planned trigram + custom ranker. One portable engine, four domains.
Data-consistency layers
A layered story for "your write didn't collide with someone else's write" + "your screen shows fresh data without you asking." Layer 1 (optimistic locking) and Layer 4 (reactive query framework) live; Layers 2-3 planned.
Integrations
How Helm connects to third-party services — GBP (manual config today, OAuth later), owner-defined custom integrations with five auth types, and the production secret-store pattern.
Process Library
The D1-backed catalogue of shop workflows — three-layer model (Code / Vertical / SME), Store action vs Software process, the Pending/Programmed/Needs-code review pipeline, the Process Map, and the dormant Interpretation Engine.
The Three Scenarios
How the BWS machine produces a new customer in an existing vertical (Scenario 1), a new vertical with maximum reuse (Scenario 2), and a new vertical canon-led before the first client (Scenario 3). Each has its own layer arrangement, gap-worked, and definition-of-done.
Scaffolding chassis
Three-mode help layer (beginner / intermediate / expert) with per-feature decay. Tooltips fade as the operator gets comfortable with a feature and restore on long inactivity. Expertise lives at the feature level, not at the staff level.
Multi-user realtime
How a write on terminal A surfaces on terminal B in sub-second time. parked_sales server-side substrate (migration 062), topic-invalidation broadcasts, the forward-bridge that maps topic events to the legacy custom-event renderers. Shipped v0.6.112.
Conformance suite — off-app QA
How the Hub is QA'd. Code-blind off-app sweep via Cowork plugin; the Process Library canon is the spec the sweep checks against.
Scaffolding (Beginner / Intermediate / Expert)
Chassis-level UI scaffolding system. Three modes that govern help density, with per-feature decay so expertise lives at the feature level, not the user level.
Module — scaffolding
Service surface, route table, schema, and API contracts for the scaffolding subsystem.