INITIALIZING SKYE OPS...
CALIBRATING CONTROL LOOPS
Skye Suite · Ops Control

SkyeOps Mission Control

Listen for keywords embedded in SkyeDocx templates, fire kAIxuGateway13 streams with the shared helper, and pause or resume the timeline when caps are hit. Every response logs usage through the kaixu_events BroadcastChannel and the Neon-backed logs endpoint.

Request a kAIxU Key KAIXU_VIRTUAL_KEY is the only persisted secret.
Keyword-driven playbooks

Define the keyword triggers, start the stream, pause when the plan is capped, and resume only after budgets clear.

Trigger keywords

Idle No alerts Stopped
Stream logs appear here.

Ops timeline

Every `meta`, `delta`, and `done` event charts status so you can pause/resume when budgets change.

    Budget & diagnostics

    Every gateway response ships usage metadata via `kaixu_events`, and the Neon logs endpoint keeps a heartbeat for auditing.

    Cap

    —

    Spent

    —

    Remaining

    —

    Provider

    Skyes Over London

    Model

    skAIxU Flow6.7

    Diagnostics

    idle

    Last label

    —
    BroadcastChannel & Neon logs live here.
    Tutorial

    Follow Ops mission-control steps to keep streams under budget.

    Step 1 · Store the key

    Use the hero key panel so keyword-triggered streams authenticate through kAIxuGateway13 only.

    Step 2 · Start the stream

    Insert keywords and click "Start ops run". The stream connects to kAIxu Gate v2 stream with `meta/delta/done` diagnostics captured.

    Step 3 · Control caps

    Pause/resume using the buttons when you see 402 or budget warnings in the timeline; the ledger state is rendered in the budget grid.