Decision OS
Every open call Ricardo owes, and every acted call his agents owe him a grade on.
Two gates, one queue: decide what's still open, and grade what agents already did on your behalf.
Nothing sinks silently — every open decision has a number and a deadline.
What it does for you
Decide pane, numbered and answerable
Every open decision carries a mandatory recommendation, a consequence tier, and a number — answer in place, byte-identical to answering by CLI.
Review pane — act then report
Agent-acted, reversible work files itself already-done with a named revert command and a veto countdown — grade it good-job or override with one tap.
Consequence × urgency, at a glance
A matrix header plots every open row by tier and nearest deadline, so the highest-consequence, most time-sensitive rows surface first.
Try it: capabilities
Select a capability — arrow keys move between them, Home/End jump to the ends.
Capability 1 of 5
Decide pane
Every open decision carries a mandatory recommendation, a consequence tier, and a number — answer in place, byte-identical to answering by CLI.
Proof, not adjectives
Runs on Creytix's own queue
docs/creytix/decisions/QUEUE.json — the same file the CLI recorder and the mirror render from.
Shared mutation path
The card's answer box calls the exact same `--answer` recorder as the CLI — no parallel implementation to drift.
Related tools
Built with Creytix, on Creytix
This page itself was produced by the platform it describes — the same design tokens, module pipeline, and review gates used for every Creytix client site. Nothing here is a mockup of the product; it is the product.