Story: Close the tenor journey and the remaining refdata gaps — the remaining work

Table of Contents

This page documents a story in Sprint 30, carried unfinished from Sprint 28 at close. 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 BACKLOG
Parent sprint Sprint 30
Now Not yet started. Split from Close the tenor journey and the remaining refdata gaps, which closed in sprint 28 with its done tasks.
Waiting on Nothing.
Next Triage into a sprint.
Last touched 2026-11-08

3. Acceptance

  • The tenor resolution screen runs end to end in ores.web, and the server resolves a tenor over the wire with a typed refusal.
  • The party memberships serve their versions, and the convention list is filtered and validated by term.
  • A portfolio right is addressed by account, portfolio and code, and the Acme dataset carries the book-control actors.
  • The party list filters on the server, a party's removed parts are listed, and its timeline reads one window at a time.

4. Tasks

Task State Start End Description
Give the party memberships their versions BACKLOG 2026-10-15   Serve a versions read for the party_countries and party_currencies junctions, and settle whether the journey's membership history wants that read or the generic history route, which is blocked on a composite id.
Serve the convention family mapping, its term filter and term rules BACKLOG     Give the server the family-to-entity mapping, a term filter on the convention lists, an existence check on each term column, and a draft version in the history view.
Address a portfolio right by account, portfolio and code BACKLOG     The portfolio right's wire key is its code alone, so a grant collides across accounts and a removal reaches whichever account's row is found first. Give the right a key that names the account, the portfolio and the code, so the book structure screen can grant and remove rights.
Add the missing book-control actors to Acme BACKLOG     The Acme dataset has no controller, no Finance account, no quant or IT user, and no second person for each approving part, so the book controls cannot be walked as Acme. Add the actors, and decide the roles their approvals use.
Filter a record list on the server BACKLOG     Let a record list offer a type and a status filter that the server applies, starting with the party list.
List the parts a party removed BACKLOG     Add a history read by parent for party identifiers, contacts and business units, so the party timeline shows the ones that were removed.
Window the party timeline BACKLOG     Read a party's history a window at a time with a load-older control, and replace the read for each part row with one read for the party.

5. Decisions

6. Out of scope

Emacs 29.3 (Org mode 9.6.15)