Where humans steer
Fabric Tower
Mission control for AI agent squads. Where people watch, steer, and approve the work.
Your people keep authority over what the agents do. A mission board, approval tickets, and a runs ledger give operators one place to watch, steer, and stop the work. It is the control surface most teams find they need only after something has gone wrong.
3 common questions, answered below ↓- Role in the family
- Where humans steer
- Databricks surfaces
- GenieUnity AI GatewayDatabricks AppsLakebaseTemporal
- Status
- Phase one is live: a real squad runs end to end. The durable path is certified against Temporal Cloud: a mission parked at approval, survived a full application restart, and completed from its original workflow history.
- Documentation
- tower.fabric.pro
The problem
Once several agents are working, the question stops being 'can it run' and becomes 'what is it doing, who approved that, and how do I stop it'. Most agent stacks have no answer because they were never designed for a human to supervise.
How it works
A mission board, one-tap approval tickets, a runs ledger, and shared documents, with the governance pipeline under every mutation. One request plans through a supervisor agent and dispatches to the squad. Anything that would leave the workspace parks at a ticket. The supervisor never approves its own work; a person does.
What it does
One ask runs the squad
A request is planned by a supervisor and routed per task to the right specialist.
Humans hold the gate
Anything leaving the workspace stops at a ticket a person answers. The supervisor cannot approve itself.
Genie-backed analysis
Data questions route to a Genie-backed analyst; the answer and its SQL are the deliverable.
Survives restarts
Approval-parked missions resume from workflow history after a full stop and start.
Your people keep authority over what the agents do. A mission board, approval tickets, and a runs ledger give operators one place to watch, steer, and stop the work. It is the control surface most teams find they need only after something has gone wrong.
FAQ
Fabric Tower, answered
What does Tower actually give an operator?
One place to watch, steer and stop the work of an agent squad: a mission board, one-tap approval tickets, a runs ledger and shared documents, with the governance pipeline under every change.
Can an agent approve its own work?
No, and that is enforced structurally. Anything that would leave the workspace parks at a ticket that a person answers. The supervisor plans and routes; it never approves.
What happens if the system restarts mid-mission?
The mission resumes. The durable path is certified against Temporal Cloud: a mission parked at approval survived a full application stop and start, then completed from its original workflow history.