The Bespoke Web System
KVICK is a machine that builds bespoke commercial systems. The Hub is the first thing the machine built. One per-customer stack exposes two surfaces — operator + public — both fed by the same Worker, D1, and R2. No standalone static site, no second pipeline.
The Doctrine
Generic SaaS sells you a tool. Customizable SaaS sells you a tool with knobs. PSaaS sells you a tool that becomes yours.
The Substrate Line
The Doctrine commits the Hub to per-shop reprogrammability. Without a clear line between what reprograms and what doesn't, "reprogrammable" becomes "anything goes" and the platform dissolves into a thousand forks.
The Customer Compact
The Doctrine promises reprogrammable software. The Substrate Line draws what is open versus canonical. This page answers the question both raise: what does the shop have to bring to make this work?
The KVICK Engine
The big picture of how KVICK software gets built and kept working — in plain terms. A team of AI assistants build it side by side, a shared map keeps them honest, and an automatic tester uses the software the way a shop staffer would. Written for James. 2026-07-18.
Three strata — Kernel · Meta · Modules
How the system is organized. Three strata, one Worker. Kernel knows nothing about business; modules know nothing about each other.
Three Sessions
Why KVICK.BIKE drops from thirteen AI sessions to three, and exactly where the software stands at v0.6.954. Handoff from the retiring Codex (Command) session, 2026-07-23. Every figure verified against the repository and the running Worker at the time of writing.