Questions This Page Answers
- What happens from task intake to shipped artifact?
- Which agent domains are used in routing?
- Where does human approval fit?
- Why this architecture is safer than autonomous black-box execution?
- Which integrations are live today vs planned?
The Big Picture
How Agents Work
Task Enters the System
A task arrives from a connected tool, you create an initiative, or you ask an
agent to do something via Mission Control, ChatGPT with remote MCP enabled,
Cursor, Claude, or the OpenClaw plugin.
Agent Selection
OrgX analyzes the task and selects the best agent(s)—Engineering, Product,
Marketing, Sales, Design, or Operations—with the Orchestrator coordinating
cross-domain dependencies.
Agent Executes
The selected agent works on the task, reading from your connected tools and
generating artifacts (specs, PRs, campaigns, reports).
Decision Checkpoint
Before shipping anything, the agent surfaces a decision for your approval
with full context and reasoning.
You Approve
You review the decision in Mission Control, an MCP client, ChatGPT where
remote MCP is enabled, Cursor, or OpenClaw. Approve to ship, reject with
feedback, or edit before approving.
Access Surfaces
OrgX works wherever you work:Mission Control
Full web dashboard with Next Up scored queue, Slices Plane IWMT hierarchy
view, live agent dashboard, and red-dot control plane for proactive health
monitoring.
OpenClaw Plugin
Browser-native OrgX dashboard with 60-second pairing, automatic MCP config,
and live decision triage. Set up OpenClaw
ChatGPT / Remote MCP
Conversational interface for approvals, bulk decisions, and organizational memory
queries in accounts and workspaces where custom remote MCP connectors are
available.
Cursor/Claude
IDE integration via MCP for developer workflows and agent-assisted coding.
Integration Flow
When you connect a tool like Linear or GitHub, here’s what happens:What Gets Synced
| Tool | OrgX Reads | OrgX Writes |
|---|---|---|
| Linear | Projects, issues, labels, states | Comments, new issues, state changes |
| GitHub | Repos, branches, PRs | New PRs, comments |
| Slack | Planned | Planned notifications and approvals |
Data & Privacy
Where is my data stored?
Where is my data stored?
OrgX stores your organizational data (initiatives, decisions, artifacts) in
a secure, encrypted database. Integration tokens are stored with
column-level encryption.
What do agents have access to?
What do agents have access to?
Agents only access tools you’ve explicitly connected via OAuth. Each
integration requests specific scopes—you can see exactly what’s being
requested during setup.
Can I disconnect a tool?
Can I disconnect a tool?
Yes, anytime via Settings → Integrations. This immediately revokes OrgX’s
access.
Real-Time Updates
OrgX keeps you informed as agents work:- Progress streams: See agents thinking and working in real-time
- Decision notifications: Get alerted when agents need your input
- Sync status: Know when integrations are connected and healthy
Current production connectors center on Linear, GitHub beta, Stripe billing,
and MCP/OpenClaw access surfaces. Slack, Notion, HubSpot, Figma, and Mailchimp
are roadmap items or selected-runtime stubs, not generally available native
integrations.
Key Concepts
IWMT Hierarchy
OrgX organizes work using the IWMT hierarchy — Initiative, Workstream, Milestone, Task. This structure enables automatic cascade execution:| Level | What It Is |
|---|---|
| Initiative | A high-level goal (e.g., “Q1 Product Launch”) |
| Workstream | A parallel execution track within an initiative |
| Milestone | A checkpoint or deadline within the initiative timeline |
| Task | An individual unit of work assigned to an agent |
Core Entities
| Concept | What It Is |
|---|---|
| Agent | A specialized AI worker (Engineering, Product, Marketing, Sales, Design, Operations, Orchestrator) |
| Decision | A checkpoint where agents need your approval |
| Artifact | A verified output (spec, PR, campaign, report) |
Intelligence Flywheel
The flywheel connects agent execution to measurable outcomes, building trust over time:- Value Ledger: Every action generates a receipt tracking cost and attributed value
- Trust Levels: Agents earn trust per capability (
read_only→draft→act_with_approval→autonomous) - Autonomous Sessions: Budget-bounded overnight execution with morning brief review
- Org Learnings: Agents share discoveries across the org for continuous improvement
Next Steps
Agents
Learn about each agent type and their capabilities.
Decisions
Understand the approval workflow.