Skip to main content
These recipes show common multi-tool workflows. Each includes the exact tool sequence, expected responses, and decision points.

Questions This Page Answers

  • What exact tool sequence should an operator run for common workflows?
  • Which calls prove system health before dispatching high-value work?
  • How do trust, autonomous sessions, and ROI queries connect in practice?

Recipe 1: First Connection Handshake

Verify auth, discover workspace, and get org context.
1

Verify Connection

Expected: { "workspace_id": "ws_...", "name": "My Workspace" }If you get workspace_not_set, call workspace with action=list first, then workspace with action=set.
2

Get Org Overview

Expected: Summary with active_initiatives, total_tasks, health indicators.
3

Check Pending Work

Expected: entities array of pending decisions with id, title, status, and urgency.

Recipe 2: Create and Launch an Initiative

Build a full initiative hierarchy and start execution.
1

Scaffold the Initiative

Expected: Returns initiative ID, workstream IDs, task IDs. Auto-launches by default.
2

Check Health

Expected: health_score, milestone progress, blockers.
3

Browse Created Entities

Expected: List of tasks with status, titles, and IDs.

Recipe 3: Decision Triage

Review and process pending decisions efficiently.
1

Fetch Pending Decisions

Expected: Pending decisions. Filter the results client-side for critical items if you want the strictest triage queue.
2

Get Context for a Decision

Use orgx_search to understand the background:
3

Approve or Reject

Or reject with feedback:

Recipe 4: Overnight Autonomous Session

Set up a bounded autonomous session and review results the next morning.
1

Check Trust Levels

Expected: Trust levels per capability. Only autonomous capabilities will execute without approval.
2

Start Session

Expected: Session ID, status active.
3

Morning Review

Expected: Curated receipts, exceptions that need attention, ROI delta.
4

Check ROI

Expected: Session summary, cost, completed work, pending decisions, and artifacts from the latest autonomous run.

Recipe 5: Planning Session

Use collaborative planning tools to improve an initiative plan.
1

Start Planning

2

Get AI Suggestions

Expected: AI-generated suggestions for gaps, risks, and improvements.
3

Record Edits

4

Complete Planning


Recipe 6: Entity CRUD Lifecycle

Manage the complete lifecycle of an entity — create, update, comment, complete, and verify.
1

Create an Entity

Expected:
2

Update the Entity

Expected:
3

Comment on It

Expected:
4

Complete the Entity

Expected:
5

Verify Parent Completion

Expected:
If is_complete is true, the parent workstream can be marked complete as well.

Recipe 7: Scoring & Queue Management

Manage the Next Up Queue — score items, inspect signals, pin priorities, tune weights, and skip blockers.
1

Score the Queue

Expected:
2

Get Scoring Signals

Expected:
3

Pin a High-Priority Item

Expected:
Pinned items always appear at the top of the queue regardless of score.
4

Adjust Scoring Weights

Expected:
5

Skip a Blocked Workstream

Expected:
Skipped workstreams and their tasks are removed from the queue until the workstream is resumed.

Next Steps

Failure Playbooks

Handle errors gracefully.

Tool Profiles

Reduce schema overhead with role-based profiles.