A decision you can hand to
a person, a team, or an agent.
Most decisions leave the room as a vague verbal blessing. An ExecutionIntent leaves as a governed, versioned package that any authorised executor, human or machine, can act on without losing what the organisation actually meant.
Nine fields. Nothing optional.
Hover or tap a line in the package, or a card beside it. Each field exists because its absence is how execution goes wrong.
Selected option and decision rationale
The choice made and the reasoning that beat the alternatives. When priorities shift in March, nobody has to reconstruct why the organisation acted in January.
Objective and expected outcome
What the work is meant to change, stated before a line of work begins. This is the yardstick the outcome receipt will be measured against.
Constraints and non-negotiable policies
Regulatory, security, and organisational rules the work must respect. Executors inherit them automatically; they are not a wiki page someone was meant to read.
Permitted evidence references
The documents, datasets, and prior decisions execution may rely on. Provenance travels with the work, so an auditor can trace every claim to its source.
Accountable owner
One named person. Escalations, review gates, and receipts route to them. Accountability that belongs to everyone belongs to no one.
Budget, deadline and success measures
What it may cost, when it must land, and how success will be judged. Agreed up front, sealed in the package, immune to convenient reinterpretation.
Approved agent, runtime and model posture
Which agents, runtimes, and models are authorised to act, and under what posture. Software executes decisions now; authority must be explicit.
Review and escalation requirements
The checkpoints where humans look, and the conditions that pause execution and summon the owner. Autonomy with tripwires.
Configuration fingerprint
A cryptographic fingerprint of the whole package. Change one comma and the version increments and the fingerprint changes. Silent edits are impossible.
Decisions change. The record never lies about it.
Reality intervenes: budgets move, constraints tighten, scope shifts. An ExecutionIntent is allowed to evolve, but only in the open. Every version is kept, every change is attributed, and executing systems always know which version they hold.
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. Six kinds of executor.
The intent stays the same shape whoever executes it. Bridgly routes it to the specialist lane suited to the work, and every lane answers back in progress, exceptions, and receipts.