Cascade guide

Cascade connects company direction to seat-level commitments. It is a goal tree, not a ticket tracker. Work belongs in Cascade when it explains how a seat contributes to a larger outcome.

Good Cascade structure

• Company goals connect back to the Compass.
• Team or function goals connect to company goals.
• Seat commitments connect to the goal they advance.
• Each commitment has one owning seat.
• Status is evidence-based where possible.

What does not belong

Do not put every task into Cascade. Small errands, private notes, and work with no strategic connection should stay out. Cascade should answer whether the company is moving toward its stated outcomes.

Operate Cascade from CLI or MCP

• Read: rost goal list --json / goal.list / rost_list_cascade_goals (scope: seat or tenant-admin). Returns goals, optionally filtered by cycle_id or seat.
• Create: rost goal create ... / goal.create / rost_create_cascade_goal with cycle, seat, parent, title, and definition of done.
• Track: goal.update (title or definition of done — not gated) and rost goal status / goal.set_status (on/off/done). Seats may set only their own goals.
• Restructure: rost goal reparent / goal.reparent and rost goal drop / goal.drop.

When to stop for confirmation

goal.reparent and goal.drop are human_required; goal.create, goal.set_status, and goal.update are none, so a seat can add goals and update their status directly. Moving or dropping a goal changes how the company reads its own progress, so it returns a pending confirmation over MCP. An agent proposes the branch and surfaces the approve link; a human decides.

Agent guidance

Agents can suggest commitments and report progress. They should not create a new goal branch when the parent outcome is unclear. Ask a human to clarify the goal instead.