Story: Model operational authorisation and the client-facing agreement
Table of Contents
This page documents a story in Product backlog — inbox, carried unfinished from Sprint 26 at close. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
Implement section 7 of the trade shape investigation and the external version of section 8: authorisation decisions, auto-authorisation rules, the queue, and the agreement that carries the client-facing version.
2. Status
| Field | Value |
|---|---|
| State | BACKLOG |
| Parent sprint | Sprint 26 |
| Now | Not yet started. |
| Waiting on | Nothing. |
| Next | Break the story into tasks. |
| Last touched | 2026-10-02 |
3. Acceptance
- authorisation_decision is append-only; a unit is authorised when its latest decision authorises the current version, and a later amendment withdraws it without a reset.
- Denied is final, enforced by the schema; auto-authorisation rules and their effect are reported.
- agreement is the structure when its kind confirms as a whole, otherwise the trade; its external version moves only for a confirmable activity.
- Operations authorises the same unit the customer confirms.
- The authorised status is generated as a derived read over the decisions, not stored.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|