Carrot Watcher · Operating Doctrine

§1 · What it is

The Carrot Watcher is the sovereign-side console at /carrot-watcher. Every supplier that fills the public intake at /carrot-intake arrives here in real time. The page polls the database every 10 seconds and surfaces new submissions with a flash animation so they can't be missed.

It is the operator's eye on the front door of The Carrot. Without it the public intake would be a one-way drop-box. With it, every submission is a tracked obligation — grabbed, contacted, kit-sent, completed, archived.

§2 · How to operate it

Daily flow (5 minutes)

1. Open /carrot-watcher. The unread badge in the header pulses orange if anything is waiting.
2. Click any supplier name to open the detail modal. Read everything in one screen.
3. Hit Grab on any new submission to take ownership (status flips to In Review).
4. If verified: Send Carrot Kit queues the welcome email; Mark Complete closes it.
5. If something is off: Mark Action Needed flags it red so it can't be lost.
6. Add notes any time — every note is timestamped and audit-logged.

Filters

Status (New · Review · Action · Complete) · Source (Website · QR · API) · free-text search across name/email/material. Filters are debounced 300ms and update without page reload.

The H.BLUE log stream

The right-side panel polls /api/carrot/watcher/log every 8 seconds and shows the last 50 events: form submissions, grabs, kits sent, status changes, notes. Nothing happens silently.

§3 · Functions exposed

§4 · How it helps now

• No missed supplier. The public intake page has been live but had no operator surface. The Watcher closes that loop in one screen.
• Audit-immutable. Every action — grab, status change, note, kit sent — is written to op_ledger via the carrot-submission webhook so the audit trail survives the page.
• Pattern visibility. The H.BLUE side panel shows volume rhythm: hour-by-hour activity, repeat suppliers, drop-offs.
• Onboarding is now 5 minutes. A new operator can open this page and run a full intake without training.

§5 · How it helps in the future

• Routing rules. When the team grows past one operator, status colours become assignment lanes — Region A → Operator 1, Region B → Operator 2.
• Predictive ranking. H.BLUE will start sorting by lifetime-value forecast so the highest-impact suppliers surface first.
• Auto-actions. Trusted supplier patterns (verified before, clean material, low fraud score) can auto-grab and auto-send the kit, reducing operator load to exception handling.
• Cross-feed. Completed submissions can auto-promote into the dPRN Console mint queue (/dprn-console) — the watcher is the upstream of the vault.

§6 · How to make it better

1. Real WebSocket. Current implementation polls every 10s. Swap to a WebSocket on /ws/carrot-stream for sub-second arrival animation.
2. Email + SMS triggers. Wire the Send Carrot Kit action into a real SMTP relay; add SMS for high-priority alerts.
3. Sound + browser notifications. The "ding" + Notification API hooks are stubbed in the template — enable per-operator setting.
4. H.BLUE insights upgrade. Currently shows known-supplier + lifetime value. Add: average response time, conversion rate, last-contact decay, fraud-pattern matches.
5. Bulk operations. Multi-select rows and grab/complete in batches.
6. Export. CSV download of filtered list (the dPRN Console already has this — port the same pattern).
7. Mobile view. Current grid collapses but isn't optimised — tap-targets need 48px minimum.

§7 · Connected MDs

• MD-233 · The Original Carrot — the doctrine the Watcher serves.
• MD-363 · The Three-Engine Architecture — Engine 2 is the Carrot.
• MD-459 · Supplier Intake Operating Doctrine — the upstream surface.
• MD-460 · dPRN Console Operating Doctrine — the downstream vault.
• MD-452 · The Pathway · 1/3 Client — every Carrot starts here, climbs from there.