This Cross-AI page is English only. Language controls on other site pages are unchanged.
Experimental building blocks. Note: Connecting each AI may require adjustments on your side (API keys, model choice, prompts, and runtime settings). Treat these desks as experimental building blocks, not a guaranteed turnkey multi-cloud product.
Cross-AI · Operations Desk
Operations Desk
Switchboard-style triage with a stop-gate. Date 2026-09-10 JST. RESULT PASS on a SAMPLE inbound ticket.
botshelf-support-triage-3b).
switchboard-coordinator and stop-gate are process seats (desk simulation / Shell skills), not separate LLM providers.
Draft-only: no live email sender. External reply stopped at Human Yes (SEND=false) and was not sent.
Where it sits
Cross-AI ops case study + public proof (not a distributable ZIP kit). Uses Library support-triage as one seat. It is not a Marketplace listing and not a Verified Library badge. Support-triage PE elevate remains HOLD separately.
Setup / handoffs / gates
- How to adapt: there is no Ops kit ZIP. Reproduce the pattern on your side: local Ollama (or mark UNAVAILABLE), a coordinator/process seat, and a stop-gate that cannot send without Human Yes. Expect API keys, model tags, prompts, and runtime settings to need user-side adjustments.
- Envelope / handoff: seats run sequentially (coordinator → triage LLM → stop-gate). Draft stays held; context must carry forward — do not treat the draft as an auto-sent reply.
- Failure / blocked seats: missing Ollama tag → label
UNAVAILABLE/BLOCKED(do not invent a cloud support bot). If Human Yes is denied or absent, status stays held — external reply remains unsent. - Human approval:
SEND=falseuntil Human Yes. No customer send, mass-DM, or X ops from this desk. - Automation vs manual: SAMPLE run used one local Ollama LLM plus process seats. Draft-only — no live email sender integration is implemented here.
Verified runtimes (sequential)
switchboard-coordinator— process · ingest + policy framingollama:botshelf-support-triage-3b— LLM · local triage · ~12.5sstop-gate— process · Human Yes required before any external reply
Hard facts from the run
- RESULT: PASS (SAMPLE ticket)
- NEVER ask for API keys / passwords — enforced
- Escalate-on-policy friction handled by coordinator
- STOP before send / HUMAN YES — held
- Public proof: operations-desk-2026-09-10
Open public proof Cross-AI hub Library support-triage recipe