01
Context boundary
What partner object triggers work, what fields are durable, and what should stay in the source system?
OrgX MCP
Partner integration question
Can outside workflow context become accountable execution?
Use this surface to talk through a possible OrgX integration with a partner product such as Attrove, customer success, product ops, or sales. The conversation is simple: what context arrives, what OrgX creates, what the partner reads back, and where human approval stays in control.
1 call
Create the initiative hierarchy from a partner signal.
2 reads
Verify health through pulse and chronicle before claiming progress.
0 secrets
Public pages explain the path without exposing workspace data.
Talk track
Partner asks
What can we hand OrgX?
A customer signal, product request, account risk, or internal workflow moment with enough context to name the outcome and owner.
OrgX returns
A structured initiative, not a loose note.
Workstreams, milestones, tasks, owners, and an idempotent ref map the partner can store against its own object.
Both verify
Health and proof are read back explicitly.
The integration checks pulse, chronicle, receipts, and gaps before telling a human that work moved.
01
orgx_bootstrap
02
scaffold_initiative
03
get_initiative_pulse
04
get_operator_chronicle
05
orgx_submit_receipt
Learn each other fast
The walkthrough is built around the minimum questions that determine whether an integration should exist.
02
Execution boundary
Which workstreams can OrgX scaffold immediately, and which actions require explicit human approval?
03
Proof boundary
What evidence counts as done, how does the partner read it back, and what gaps should remain visible?
Integration contract
What each side owns
Partner owns the trigger.
Customer signal, account context, source object id, and the user-facing moment.
OrgX owns the execution record.
Initiative hierarchy, owners, status, decisions, artifacts, and receipts.
The human owns approval.
Decision gates stay explicit; the integration can surface them but not silently approve them.
Both systems own read-back.
Pulse and chronicle responses become the shared proof layer for the conversation.
Product proof should stay visible: context in, scaffold created, decision surfaced, receipt returned. If a step is missing evidence, OrgX should show the gap instead of smoothing it over.