A clear, versioned record
of what the organisation decided.
An ExecutionIntent records the option, reason, owner, constraints, budget, measures and approved delivery route in one package. People and authorised systems can work from the same instruction.
Nine fields keep the decision clear.
Hover or tap a line in the package, or a card beside it, to see what each field records.
Selected option and decision rationale
The chosen option and the reason it was selected over the alternatives. This preserves the decision context when priorities change later.
Objective and expected outcome
What the work is meant to change, stated before delivery begins. The outcome is measured against this expectation.
Constraints and required policies
The regulatory, security and organisational rules that delivery must follow. They stay attached to the instruction sent to an approved system.
Permitted evidence references
The documents, datasets and earlier decisions that delivery may use. An authorised reviewer can trace a claim back to its source.
Accountable owner
The named person who receives escalations, review requests and outcome records.
Budget, deadline and success measures
The cost limit, delivery date and measures used to assess the result. These are agreed before delivery begins.
Approved agent, runtime and model posture
The agents, runtimes and models authorised for the work, with the limits that apply to them.
Review and escalation requirements
The points where a person must review the work and the conditions that pause delivery or notify the owner.
Configuration fingerprint
A cryptographic fingerprint of the package. A change creates a new version and a different fingerprint, making the history reviewable.
Keep a clear history when the decision changes.
Budgets, constraints and scope can change. Each version is kept, every change has an owner and delivery systems can identify the version they received.
Initial intent from decision D-118. Budget £40k, deadline 31 August, two approved executors.
Constraint added after security review: UK data residency. Escalation threshold tightened to 80% of budget. Change attributed to the accountable owner.
Budget raised to £50k, deadline moved to 30 September, Linear added as an executor. Approved at a review gate; the receipt will be judged against this version.
One package for different delivery systems.
The intent keeps the same fields whichever approved system receives it. Progress, exceptions and outcome records then return to the same decision.