01Pattern
Interview the workflow. Build the thin system.
Measure what changed, then decide what to automate next. The map exists to drive the build, not decorate a PDF.
Proof
Proof is working software, not a slide deck.
KJS is built around shipped systems: explicit handoffs, low dependency count, human approval gates, and operator-facing tools that can survive real use.
02Bias
Readable code. Explicit handoffs.
Low dependency count, no hidden third-party tracking, and human review before critical actions become automatic.
Operator console
Real systems have queues, owners, states, and gates.
01Sourced
Territory, business, workflow, and scoring records are persisted in SQLite.
02Reviewed
Automation candidates move through approval states before anything gets sent or changed.
03Shipped
The first version is small enough to understand and useful enough to replace a manual loop.
SSRNuxt / Nitro app
SQLitePersistent workflow data
AdminProtected operator console
0Hidden trackers