Skip to main content
All field notes

OrgX / Journal

Field note

Guardrails Before the Work, Acceptance After It

Handing real work to agents takes two records: what an agent may do before it acts, and who accepted what it produced afterward. OrgX keeps both on the same initiative.

OrgX separates permission to do work from acceptance of its result. Before an agent acts, the question is what it may do. Afterward, the question is whether the output met the request and who accepted it.

A draft can respect every permission and still be wrong.

Before the work: permission

OrgX's autonomy policy defines three modes: Manual waits for a person; Gated allows low-risk work while holding specified deliverables for review; Autopilot permits more continuation within the policy. Connector settings can further allow, ask about, or deny an action.

The policy retains a human boundary for consequential actions such as external sends, spending, deploying, merging, and deleting. An agent cannot raise its own autonomy or approve its own work. Broader approval-flow behavior remains a beta claim; inspect the policy and supported path for the operation you intend to run.

After the work: acceptance

Consider an illustrative announcement draft. The agent was allowed to write it, but it describes a feature as generally available when the owner's decision said invited customers only.

Review the actual draft against that decision. Record the requested correction, attach the revised artifact, and preserve the owner's ruling. The permission to draft never supplied permission to send, and producing a revision did not establish that someone accepted it.

RecordQuestion for the announcement
PermissionMay the agent draft or send it?
EvidenceDoes the audience decision support the wording?
AcceptanceHas the owner accepted this version?

In this illustrative case, allowed drafting establishes neither factual accuracy nor permission to send.

OrgX keeps these records attached to the initiative. Versioned quality-bar checking is a separate beta capability. A producer's receipt is an account of the work, not independent proof that its claims are true.

Check one complete record

Our July account of 3,328 execution receipts and one acceptance row showed why this distinction matters. Capturing activity did not produce an equally complete record of human judgment. Those historical counts are not a current adoption measure.

Choose one deliverable. Find its original request, the permission boundary, the artifact, and the owner's ruling. If the ruling is missing, keep acceptance unresolved.

Read the receipt specification, or bring that deliverable to a proof review to inspect what the record actually establishes.

OrgX research & field notes Explore all field notes