The console Live · by invitation
Where the work lives, and where the approvals land
Enforcement stays on your machine; this is everything that has to outlive it. One line from anywhere lands in Triage, a request for a wall to move arrives with its reason attached, and the trail keeps its shape after the laptop is gone.
What it is for
- Capture, from wherever you are. A task takes about four seconds from one line to Triage — measured once, on one machine, for one task.
- The approval moment. A zone's owner sees what is being asked, why, and what the agent would do instead — then answers in one tap, with a clock attached to the yes.
- The trail past one machine. Records live in your repository and survive uninstalling us; the board is what makes them legible to someone who is not standing at that checkout.
Getting in
Access is by invitation while this is new. That is a real queue rather than a coming-soon page: the product runs today, and the invitation is about how fast it grows, not about whether it exists.
Already have an account? Sign in.
What it deliberately will not do
- It cannot close a task. Closing compares a branch against what the task declared, and a server has no repository to diff. A button that can only fail is not worth offering, so it is not there.
- It is not in the deny path. The hook decides locally and never phones home, so an outage here cannot open a zone — and cannot shut one either.
- It does not run your agents. Nothing is executed here. This is the board, the owners and the record.
The local half arrives with the plugin orthe CLI, and the model they all read is the zone map.