# Fabric Tower

> Mission control for AI agent squads. Where people watch, steer, and approve the work.

Role: Human oversight console
Databricks surfaces: Genie, Unity AI Gateway, Databricks Apps, Lakebase, Temporal
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: https://tower.fabric.pro
Canonical: https://www.techfabric.com/accelerators/fabric-tower

---

## 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 changes for you

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.

## Questions

### 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.