Loading...
Loading...
How Catalyst Cloud runs a ticket on the customer's own tenant, as facts an agent loads on demand: the eight-phase ladder and what each phase produces, the eleven board slots and this team's live stage map, what happens when a phase fails (retry, backoff, Remediate, park), how the queue is ordered and routed and every reason a ticket is excluded, and the coding-account model. Use when a person asks "how does this work?", "why did it do that?", "why is this stuck?", "what runs next?" or "how does it prioritise?". Read-only; its scripts explain one ticket's eligibility in plain English, show what is running and queued, and print the tenant's stage map and thresholds straight from the contract.
npx skill4agent add coalesce-labs/catalyst-cloud-skills how-catalyst-worksGET /api/v1/agent/contractcatalyst-skills--helpnode scripts/explain-ticket.mjs <ticket>node scripts/whats-running.mjs [--queue] [--accounts] [--team <key>]--queue--accountsnode scripts/show-my-map.mjs [--team <key>]| when | read |
|---|---|
| "what are the phases, what does each produce, when is a ticket Done?" | |
| "which column is which, why does nothing dispatch, what is a slot?" | |
| a phase FAILED, a card went to Remediate, a ticket is parked or on hold | |
| "what runs next, why not this one, what does this exclusion reason mean?" | |
| "why is nothing running", walls, quarantine, which provider ran a phase | |
references/what-runs-next.mdunknowncatalyst-linearcatalyst-githubwhat-needs-me