OrgX

Tools (29)

• approve_decision

  Approve a pending agent decision after explicit user confirmation. Also known as: sign off, approve AI work, unblock agent, accept decision. USE WHEN: user says to approve a decision returned from list_entities with type=decision and status=pending (or the legacy get_pending_decisions alias). NEXT: Confirm approval to user; agent is notified automatically. DO NOT USE: without showing the decision to the user first. Requires decisions:write.

• reject_decision

  Reject a pending agent decision with guidance after explicit user confirmation. Also known as: request revisions, send feedback, decline decision. USE WHEN: user wants to reject or request revisions on a decision. NEXT: Agent will revise their approach based on the reason. DO NOT USE: without a reason — always include why. Requires decisions:write.

• get_agent_status

  Show current AI agent activity, blocked work, and execution state. Also known as: agent status, what agents are doing, active runs. USE WHEN: user asks about agent activity, progress, or what agents are working on. NEXT: If agents are stuck, suggest approve_decision or entity_action. DO NOT USE: to check initiative health — use get_initiative_pulse instead. Read-only.

• query_org_memory

  Search team memory, organizational decisions, prior artifacts, and project context across agents. Also known as: search memory, recall decisions, find context, retrieve artifacts, project memory. USE WHEN: user asks about past decisions, context, or knowledge. NEXT: Present relevant results; suggest drill-down with list_entities. Prefer `query_org_memory` with scope=decisions with a topic query for new prompts, skills, and examples. DO NOT USE: for listing current entities — use list_entities in

• get_initiative_pulse

  Get project health, blockers, milestones, owners, and recent activity for an initiative. Also known as: project status, roadmap progress, execution health, blockers. USE WHEN: user asks how an initiative is going, or wants a status update. NEXT: If blockers exist, suggest entity_action to resolve. For deeper drill-down, use list_entities with initiative_id. DO NOT USE: for org-wide overview — use get_org_snapshot instead. Read-only.

• spawn_agent_task

  Delegate work to a specialist AI agent and track the assigned task. Also known as: hand this off, assign task, spawn agent, have an agent do it, autonomous work. Automatically checks authorization, rate limits, quality gates, model routing, and budget policy before spawning. Omit model_tier/provider/model to let OrgX auto-route from task complexity; provide them only when the user or verification plan intentionally constrains routing. Returns modelTier, budget, and run details on success, or blo

• handoff_task

  Reassign work to another specialist AI agent and optionally spawn a new run. Also known as: handoff task, transfer work, change assignee. USE WHEN: a task needs to be reassigned to a different specialist agent. NEXT: Use get_agent_status to confirm the new agent picked up the task. DO NOT USE: for new tasks — use spawn_agent_task instead.

• recommend_next_action

  Recommend what should happen next based on progress gaps, blockers, and execution templates. Also known as: next best action, prioritize work, unblock project. USE WHEN: user asks what to do next, or needs help prioritizing. NEXT: Execute the recommended action (entity_action, spawn_agent_task, etc.). DO NOT USE: when user already knows what they want to do. Read-only.

• get_operator_chronicle

  Read the operator chronicle: decision chronology, yesterday/week/30-day rollups, reportingNarrative.briefMarkdown, artifacts, PR receipts, active initiatives, goals, top priorities, velocity, and reporting gaps for a workspace. USE WHEN: user asks what changed yesterday, this week, or this month; asks for decision chronology, top priorities, PR velocity, artifacts, goals, or what OrgX is missing. NEXT: present reportingNarrative.briefMarkdown first, then use reportingNarrative.nextAction and top

• orgx_emit_activity

  Emit append-only run telemetry for OrgX control-plane reporting. USE WHEN: agent is executing and needs to report progress. NEXT: Continue work; emit again at each phase change. DO NOT USE: for entity status changes — use entity_action instead. Setting phase="completed" records telemetry only and does not mark tasks, workstreams, or initiatives complete.

• consolidate_pr

  Generate and persist an orchestration.consolidation_pass receipt for a GitHub pull request. USE WHEN: Eli or another engineering agent needs a durable PR review receipt with reading order, existence evidence, deduped findings, verdict, and server-derived AQ score. NEXT: inspect the returned artifact_id or attach it to task completion proof. DO NOT USE WHEN: only asking for PR status; use GitHub tools instead.

• orgx_bootstrap

  Establish OrgX session context, discover granted scopes, and get the v2 tool routing map. Also known as: bootstrap, setup, tool routing. USE WHEN: first call in a fresh session, after reconnecting, or before performing a multi-step workflow. NEXT: use orgx_search, orgx_inspect, or orgx_recommend based on the returned routing map. DO NOT USE WHEN: you already have session context and need to read or mutate work. Read-only.

• orgx_inspect

  Hydrate one OrgX entity with execution context. USE WHEN: the user names a specific task, milestone, initiative, decision, artifact, or plan session and needs details before acting. NEXT: use orgx_act, orgx_attach, or orgx_write if the user asks to change what you inspected. DO NOT USE WHEN: browsing or searching many records; use orgx_search. Read-only.

• orgx_search

  Find OrgX entities, decisions, artifacts, and memory. USE WHEN: browsing work, searching memory, finding IDs, or listing related records. NEXT: use orgx_inspect for one selected result or orgx_recommend when the user asks what to do next. DO NOT USE WHEN: you already know the exact entity and need full context; use orgx_inspect.

• orgx_recommend

  Recommend next work, summarize operator-chronicle/morning-brief signals, or read prioritization context. USE WHEN: user asks what to do next, wants a brief, asks what changed yesterday/week/30 days, or needs priority guidance. mode=morning_brief returns the operator chronicle when available. NEXT: present the recommendation, then use orgx_act, orgx_write, or orgx_spawn only after the user confirms an action. DO NOT USE WHEN: the user already specified the action; use orgx_act or orgx_write.

• orgx_write

  Create or update one OrgX record (snake_case fields). Create needs: initiative title; workstream title+initiative_id; milestone title+workstream_id; task title+workstream_id; decision title; blocker run_id+description in metadata; skill/studio records title. Artifacts need entity_type+entity_id (or task_id), artifact_type, and artifact_url|external_url|preview_markdown. Practical founder/team artifact examples: orchestration.next_initiative, eng.pull_request, eng.deploy_proof, eng.structured_b

• orgx_attach

  Attach a durable artifact, proof URL, or preview to an existing OrgX entity. USE WHEN: saving evidence, PRs, documents, reports, screenshots, or external artifacts. For founder/team work, prefer practical artifact_type codes such as orchestration.next_initiative, eng.pull_request, eng.deploy_proof, eng.structured_blocker, sales.strategy, sales.icp_offer_sequence, sales.send_plan, marketing.launch_asset, marketing.channel_hypothesis, product.customer_discovery, product.prd, product.pricing_hypoth

• orgx_act

  Run a lifecycle, validation, completion, or proof action on one OrgX entity. Per-action required inputs: • update → "fields" patch object. • complete_with_proof, ship_batch → "artifact" (artifact_type + url/preview). • validate (studio) → "spec" payload. • block, flag_risk, decline, cancel, delete → "note" strongly recommended. • dry_run=true previews any lifecycle action without mutating where supported. Allowed (type → action) pairs (others return an error): initiative: launch|pau

• orgx_plan

  Start, resume, edit, improve, or complete a tracked OrgX planning session. Per-action input requirements: • action="start" → REQUIRES feature_name. Optional: initial_plan (markdown to seed the session). • action="resume" → REQUIRES session_id. • action="improve" → REQUIRES session_id AND plan_content (the current draft to critique). • action="record_edit" → REQUIRES session_id AND edit_summary (one-line description of the change). • action="complete" → REQUIRES sessi

• orgx_spawn

  Guard, estimate, classify, spawn, or hand off specialist agent work. Inputs: spawn from task REQUIRES task_id; ad-hoc spawn REQUIRES title+instructions and should include agent_type. handoff REQUIRES task_id+agent_type. guard REQUIRES agent_type. classify REQUIRES title OR task_id. action="estimate" returns candidate routes and cost context without dispatching work. Routing: omit model_tier/provider/model for OrgX auto-routing from task complexity and workspace policy. Set model_tier, provider

• orgx_decide

  Create, approve, reject, remember, or list durable OrgX decisions. Per-action input requirements: • action="list_pending" → No required fields. Optional: initiative_id, workspace_id (scope filters). • action="create" → REQUIRES title AND decision (the resolved decision text). Recommended: context, initiative_id. • action="remember" → REQUIRES decision (the text to capture as a remembered decision). Optional: title, context. • action="approve" → REQUIRES decision_id. Optio

• orgx_submit_receipt

  Submit a durable receipt (proof, outcome, quality, attribution, or learning) anchored to an OrgX entity or artifact. Required: receipt_type + summary. Strongly recommended: one anchor (entity_type+entity_id OR artifact_id), artifact_type, business_outcome, agent_type, AND at least one verifiable URL inside evidence. Recognized receipt_type: "proof" (completion proof), "outcome" (measurable result), "quality" (review/score), "attribution" (credit link to revenue/value), "learning" (distilled le

• recall_memory

  Search organizational memory for prior decisions, artifacts, project context, and team knowledge. Also known as: search memory, recall decisions, find context, retrieve artifacts, what did we decide.

• approve_agent_work

  Review or act on agent decisions awaiting human approval. Also known as: pending approvals, agent blocked, sign off, review decisions, approve AI work. Per-action input requirements: • action="list" (default when action omitted) → No required fields. Optional filters: limit, urgency_filter, initiative_id. • action="approve" → REQUIRES decision_id. Optional: note (free-text approver rationale). • action="reject" → REQUIRES decision_id AND reason (explanation shown to the assigned agent so

• delegate_agent_task

  Assign work to a specialist AI agent and track the result. Also known as: hand this off, spawn agent, assign task, delegate to agent, have an AI agent do it.

• track_project_progress

  Get health, blockers, milestones, owners, and recent activity for a project or initiative. Also known as: project status, initiative pulse, blockers, roadmap progress, execution health.

• scaffold_initiative

  Turn an objective, roadmap, launch, or feature plan into executable workstreams, milestones, and tasks. Also known as: scaffold project, create roadmap, generate execution plan. Minimum required input: title. Conditionally required: • workspace_id — REQUIRED unless the MCP session already carries workspace context (resolve via list_entities type=command_center or get_org_snapshot). • objective_ids (or goal_ids) — REQUIRED only when workspace policy enforces a primary objective. objective_id

• review_artifact

  Surface the next artifact awaiting review. Renders the artifact-review widget with a preview, version filmstrip, and hold-to-approve / request-changes actions. USE WHEN the user asks to review work, approve a deliverable, or handle pending artifact reviews. DO NOT USE for listing all artifacts — use list_entities type=artifact instead.

• get_morning_brief

  Curated receipts, exceptions, ROI delta, and value signals from the most recent autonomous session. The brief IS curated receipts, not a separate data structure. Prefer `get_morning_brief` with workspace brief with value and exception summaries for new prompts, skills, and examples.