OpenIntent Composer
Translate company requests into structured intents with boundaries, acceptance criteria, and proof.
OpenIntent Composer turns a company request into a structured intent before work begins.
Instead of asking an agent to "just handle it," the requester defines the goal, context, permission scope, success criteria, and proof standard. This reduces drift and makes review possible.
Intent fields
A useful OpenIntent packet includes:
- Goal: The company outcome to produce.
- Requester: Who asked and under which role.
- Context: Relevant docs, SOPs, prior decisions, or source materials.
- Permission scope: What the system can read, write, schedule, or escalate.
- Assignee path: Human, agent, or mixed route.
- Constraints: Budget, deadline, risk, privacy, and tool boundaries.
- Acceptance criteria: What must be true for the work to count as done.
- Proof standard: Evidence and report-back format.
- Memory rule: What should be remembered after completion.
Example
Goal: Prepare a finance recap request for Adit on 22 June, evaluate the output against company standards, and report the result back to Riyan.
Permission scope: Finance workspace only. No payment actions. No external sharing.
Acceptance criteria: Recap is complete, reviewed against the attached standard, and returned with clear findings.
Proof standard: Task record, submitted recap, evaluation notes, and final report-back.
Composer rule
A clear intent is stronger than a long prompt. The composer should make the request legible to the company before an agent or automation touches it.