Core concepts

Six concepts explain the OrgX work record: Work, Decision, Artifact, Receipt, Process, and Event.

You can start with Work and learn the rest when your integration needs it.

The six core concepts

Concept	What it means	Launch-review example
Work	A result someone intends to produce	“Review the launch plan”
Decision	A point that needs human judgment	Approve the launch date
Artifact	A durable output of the work	The reviewed launch plan
Receipt	A portable record of the actor, evidence, and reported outcome	The completion receipt
Process	A repeatable flow that work can follow	Draft → review → publish
Event	An accepted state change you can consume in order	work.completed

Initiatives, workstreams, milestones, handoffs, discovery runs, and projections are advanced ways to organize or analyze these six concepts. The API reference introduces them only where they are required.

Contract principles

Accepted state is explicit

An API success records the state described by that operation. The response identifies the work, receipt, and event created by the call.

Retries are safe

Send an Idempotency-Key with every state-changing request. Reusing the key with the same input returns the original result; changing the input returns a conflict.

Evidence supports a specific claim

Producer reports, verifier checks, human approvals, and provider outcomes remain distinct fields so a reader can judge the result.

Derived views identify their freshness

Projections include the source and freshness information needed to decide whether a result is current enough for the next action.

Where the result appears

Created work appears in Mission Control and has a stable task page at https://useorgx.com/tasks/{taskId}. The taskId comes directly from the API response.

Create your first work item

Reach a visible 201 with one required body field.

Browse advanced operations

Add processes, handoffs, events, and projections when you need them.