Intention records
Intended-state records written mostly by workflows and policies — what something was supposed to look like, and whether it was satisfied.
An intention record says what some part of the system was supposed to look like. Most are written by workflows rather than typed by a person, which makes this the most machine-facing of the five Company State record types.
What it holds
- Source type and source ID — where the intention came from:
workflow,policy, orhuman, plus the identifier of the specific one. The list shows these joined, likeworkflow:quote-approval. - Expected state — a JSON object describing the intended state, for
example
{"stage":"approved"}. - Owner and status.
The expected state is entered and shown as raw JSON. That's deliberate: these records are usually produced and consumed by workflows, and the shape varies by what wrote them.
No drift detection here
The record states an intention. It does not compare that intention
against reality, and nothing here remediates a mismatch. If the
expected state says approved and the record is actually in draft,
nothing on this page will tell you so.
Marking one satisfied is an operator asserting the intended state was reached. It is a human judgement recorded as one, not a check the system ran.
The four statuses
- Proposed — captured, not yet agreed.
- Accepted — agreed as the intended state.
- Satisfied — confirmed reached.
- Cancelled — no longer pursued.
Satisfied and cancelled are terminal, set through Satisfy or cancel on the detail page, which takes an optional reason. Once terminal, that button is disabled.
Finding one
Filter by status, source type, and source ID, or by owner user ID. Search matches source ID and owner. The landing page counts everything that isn't satisfied — so cancelled records are still in that number.
A note on the URL
This section answers at both /company-state/intention-records and
/company-state/intentions. They're the same list; the nav and every
in-app link use the first.