Loading…
← All results// Case study 02 · Jadzia COI · production
Jadzia COI — Chief Operating Intelligence
Jadzia COI · production
Running a print business on eight repos without an operating brain means orders, leads and ops live in separate tools — and WordPress edits stay risky.
COI live — widget chat, WP SSH pipeline, worker queue, hot-lead alerts and weekly strategy brief.
Before — Problem
- ✕ Orders in WooCommerce, leads in the game, chat in the wizard — three silos
- ✕ WordPress edits via FTP and memory — no rollback story
- ✕ Sales questions answered manually across portal and wizard
- ✕ No weekly synthesis — strategy lived in scattered notes and inbox
After — Resolution
- ✓ One COI layer — jadzia.db holds orders, leads and operational state
- ✓ WP SSH agent: diff → HITL approve → write → rollback on Telegram
- ✓ customer_agent on wizard and portal — scored leads, hot alerts to Telegram
- ✓ Worker queue with JWT tasks, cost tracking and weekly strategy brief
Architecture
FastAPI COI on EU VPS — jadzia.db unifies orders and leads, customer_agent powers wizard and portal chat, Paramiko SSH agent supervises WordPress with Telegram HITL.
Jadzia is the Think layer in the Living Operating System — Sense signals enter, COI proposes, humans approve, then Act executes within bounded permissions.
COI operating loop
Sense
Signals in
Wizard checkouts, game registrations, portal visits and operational events feed the COI loop.
Think
Jadzia Strategist
Interpret context, score leads, plan WP changes and synthesise the weekly brief — propose, never auto-ship.
Act
Bounded execution
SSH writes, chat replies, order state updates and worker tasks — scoped permissions only.
Guard
HITL + Kaizen
Telegram approval, rollback path and Kaizen guard — Dowódca approves every consequential action.
WordPress SSH pipeline
- 01Task arrives via Telegram or worker queue
- 02Jadzia routes intent and generates file diff
- 03HITL approval — edit, approve or reject
- 04Paramiko SSH write to theme · rollback on failure
Sales chat widget
- 01Visitor opens chat on wizard or portal
- 02POST /api/v1/widget/chat → Jadzia COI
- 03Claude Haiku reply + lead scoring
- 04Hot lead alert → Telegram · session TTL cache
Agent OS handles code commits across repos. Jadzia COI handles business operations — orders, leads, chat and WP. VCMS governs both from outside the runtime.
This module sits inside the Living Operating System → see full stack
The Build
Six COI capability pillars — the operational brain behind wizard revenue, game leads and portal trust. Same architecture available for Dutch ZZP and SME deployments via Quietforge.
01
Order intelligence
WooCommerce order ingestion, operational state in jadzia.db, status sync for production fulfilment.
02
Lead unification
Game, wizard and portal leads in one operational store — scored, attributed, routed to the right next step.
03
Sales chat widget
customer_agent on wizard and portal — Haiku-powered replies, hot-lead Telegram alerts, session TTL.
04
WordPress SSH agent
Supervised theme edits via Paramiko — diff, HITL approve, write, rollback on Telegram or worker queue.
05
Worker queue + HITL
JWT worker tasks, dashboard metrics, token/cost tracking — nothing ships without Dowódca approval.
06
Weekly strategy brief
COI synthesis across repos — Kaizen guard filters AI proposals before they reach your inbox.
Verified production surface
- API: FastAPI :8000 EU VPS
- Widget endpoint: LIVE
- WP SSH agent: LIVE
- Worker HITL: LIVE
Ecosystem integrations
| System | Flow | Detail |
|---|---|---|
| zzpackage Wizard | In / Out | Widget chat · order webhook → jadzia.db |
| app.flexgrafik.nl | In | Lead sync · coupon attribution |
| flexgrafik.nl | In | Shared customer_agent chat endpoint |
| Telegram | In / Out | Ops commands · HITL · hot lead alerts |
| Agent OS | Sibling | Engineering pipeline — Jadzia does not commit product code |
Inbox Killer is a separate B2B product built on the same COI patterns — see Inbox Killer case study →
Stack
Python 3.11 · FastAPI · UvicornClaude Haiku/Sonnet · Gemini fallbackjadzia.db · SQLite operational storeParamiko SSH · Telegram webhookJWT worker queue · systemd deploy
Proof
Agent OS LangGraph pipeline
Planner → Coder → Tester → Reviewer → Summarizer — hybrid pipeline with human gate before ship.
// Video
Inbox Killer walkthrough
Screen recording is in production. The classification lanes screenshot and flow diagram show how it works today.
Book Automation Map →Measurement
COI live — orders, leads, WP SSH, sales chat, worker HITL and weekly brief on EU VPS.
Could this work for your business?
Start with a paid Automation Map. In 60–90 minutes we map your exact setup, score the ROI, and recommend whether this is the right first system — before you commit to anything bigger.
Book your Automation Map