Story: Close the tenor journey and the remaining refdata gaps
Table of Contents
This page documents a story in Sprint 28. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
The tenor resolution journey and the remaining refdata gaps are built: the tenor resolve operation and its screen, party membership versions, the convention family mapping and term rules, the portfolio right key, the Acme book-control actors, and the party list and history reads.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 28 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-24 |
3. Acceptance
The story closes on the tasks it finished:
- Build the tenor resolution screen.
- Resolve a tenor over the wire, with the refusal it carries.
- Build the pure batch tenor resolution engine.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Build the tenor resolution screen | DONE | 2026-10-15 | 2026-10-15 | Build journey 9 in ores.web from its document and prototype: the tenor list, the tenor, its convention, the schedule, the resolved dates, the review, the refusal and the history.. Journeys 9. |
| Resolve a tenor over the wire, with the refusal it carries | DONE | 2026-10-16 | 2026-10-17 | Add the resolve operation journey 9 draws in two places, and the refusal payload its failures should carry instead of a thrown exception reaching the screen as a 500. |
| Build the pure batch tenor resolution engine | DONE | 2026-10-16 | 2026-10-16 | Task for: Close the tenor journey and the remaining refdata gaps |
5. Decisions
- Closed at sprint 28 close with its 3 done tasks. The 7 open tasks and the original acceptance moved to Close the tenor journey and the remaining refdata gaps — the remaining work in the product backlog inbox.
- The tenor resolution screen is its own screen, reached from its own card at
/refdata/tenors, and not a step inside the instrument-convention journey. Tenors are their own reference-data job. - A tenor and the convention that resolves it are one rail, because they are read together and the review draws one difference list over both. The convention is not a second journey.
- The confirm is a sequence of writes rather than one write, and a refusal names the step that refused and the calls already written. A person has to be able to see what landed.
- The resolved dates, and a schedule axis expanded into dated rolls, wait on one operation the server does not serve yet: resolving a tenor to a date. Both are carried by Resolve a tenor over the wire, with the refusal it carries.
- Every word the screen draws comes from the catalogue. The journey's state module names its changes and its problems by key, never in English.