Skip to main content
These are request patterns, not recorded workspace results. IDs, records, and response fields vary by workspace and client. Use the MCP Tools Reference as the source of truth for the current schema. Use a bootstrap call when the client needs a session context, then search the active workspace without changing business records.
Review the returned records before selecting one for deeper inspection. A search result is not evidence that work is complete or shipped.

Recipe 2: Inspect a decision with context

Use orgx_inspect when you have a specific decision ID and need its available context before making a judgment.
Review the decision’s observable rationale, evidence, artifact references, scope, and current status.

Recipe 3: Resolve an approved decision

Only approve after the decision and its evidence have been shown to the human reviewer. Use an idempotency key for the write.
Approval records the human decision. Any follow-on work remains subject to the connected tool’s authorization, OrgX policy, and the actual execution receipt. Approval is not proof that an external system accepted, merged, deployed, or published the work.

Choosing the next action

Use orgx_recommend when the user asks what to do next or wants a brief. Treat the result as a recommendation, not an instruction; ask for explicit confirmation before a separate write action.