What the Hub Is
A gate message in your channel is a single deliverable asking for a decision. The hub is every deliverable on the project in one place, each showing its current state and the actions available on it.
Type /deevoted-hub in your project channel. Coordinator opens the hub — a single view listing every deliverable the pipeline has produced so far, organized by state. Instead of scrolling through individual gate notifications to piece together where things stand, you see the whole project at a glance and act on any deliverable directly.
Deliverable Lifecycle
Every deliverable moves through a defined set of states. The progression isn’t strictly linear — revision creates a loop that cycles a deliverable back for re-review.
Delivered — the skill has produced the deliverable; it’s awaiting your review. Approved — you’ve signed off internally; the pipeline advances and the deliverable is handed to the next skill. With Client — routed to the client for their review. Client Approved — the client has signed off.
Revision Requested — you asked for changes; the deliverable carries your notes and is awaiting dispatch. Queued / Regenerating — the skill is producing the revised version; no actions are available while it works. The revised version returns to Delivered, closing the loop.
The Hub View
When you open the hub, Coordinator posts a message listing every deliverable on the project. Each row shows the deliverable name, its current state badge, and the actions available at that state.
The available buttons change with each deliverable’s state. A Delivered deliverable shows the full action set; a Queued deliverable shows nothing — it’s regenerating and there’s nothing to do until it comes back.
Per-State Actions
These are the same gate actions you see on individual gate messages, expressed in the hub’s project-wide context. For the full mechanics of each action, see Gates & Reviews.
Sign off internally. The pipeline advances and the deliverable is handed to the next skill. Available at Delivered.
Route the deliverable to the client for their review. Available at Delivered and Approved.
Record that the client has signed off. Available at Delivered and Approved.
Add notes describing the changes needed. The deliverable is queued for regeneration and the revised version comes back for re-review. Available at Delivered, Approved, and Client Approved.
Send the requested revision to the skill to regenerate. Available at Revision Requested.
See the revision notes attached to the deliverable. Available at Revision Requested.
Cascade Impact & Revision Detail
When you go to revise a deliverable, the hub shows its cascade impact — whether changing it will trigger downstream regeneration or stay isolated. Each file in a deliverable carries one of two indicators:
- ⚠️ Cascading — revisions trigger downstream regeneration. Other deliverables depend on this file, so changing it will cascade through the project. Action: Revise Deliverable.
- 🟢 Non-cascading — asset revision only, no downstream impact. This is a standalone asset (e.g. an
.svg) that nothing else depends on. Action: Revise Asset.
This is something a single-deliverable gate message can’t do. The hub is aware of the whole project’s dependency graph, so before you request a revision you know exactly whether it will cascade to downstream work or stay contained. That’s project-wide dependency awareness.
Each entry also has a View History button that opens the Revision Notes modal — a log of every revision round with the timestamp, author, and note text. This is how you see the accumulated feedback on a deliverable across rounds.
How the Hub Relates to the Channel
The gate message is a single deliverable’s decision in the channel — it appears when a skill finishes and asks for your review. The hub is the project-wide view where you manage all of them at once, opened on demand with /deevoted-hub. For the gate model itself — gating levels, the four gate actions, revision mechanics, and escalation — see Gates & Reviews. For a visual end-to-end walkthrough of how deliverables flow through the pipeline, see the Pipeline Walkthrough.