Run the active launch system without leaving AI K9.
This dashboard reads from the live Codee Office dashboard API for queue, fulfillment, inbox, platform auth, and runtime status. The site gate is static. The data is production.
Loading AI K9 owner dashboard status…
Client lane: codee
Data source:
Trigger-ready owner actions
These controls do not rewrite the stable sales flows. They generate clean next-step directives, links, and review actions so Codee stays the operating lane between you and the system.
Approve, hold, revise, or escalate without losing context.
Loading trigger-ready owner actions…
What Codee should pay attention to next.
Starter through architecture-review visibility
These cards summarize the paid custom-site lane without touching the checkout or webhook paths. Use this section to see what is paid, what is generating, and what should stay in architecture review.
Active prompt-driven clients and delivery posture
These are the live Prompt Support clients discovered from paid site configs and dashboard state. Use this section to see who is active, which mode they bought, whether scrape-first advisory was requested, and where Codee should focus next.
Actionable next moves without disturbing stable flows
These are derived from current queue, platform, inbox, and high-ticket state. Recommendations are owner-facing only until you explicitly trigger them.
Live surfaces
Public intake routes
Production links
Tier 4 paid requests and fulfillment state
These are the premium custom-site records saved under the Codee Office/Codee admin lane. This is the queue that matters for auto-generation and architecture-review tracking.
Recent review items
Latest queue items saved into the dashboard state. This keeps approvals and pending review work visible in one place.
Connected and staged integrations
Loading platform cards…
Google Inbox status and recent stored signals
Checking inbox intelligence status…
Server-backed trigger history
These are the owner decisions recorded by the dashboard trigger API. This keeps trigger history separate from the public flows while still making the decision trail visible.