Story: Raise approval requests from the remaining gated write paths

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 party, convention and tenor screens, the ORE import and the shell counterparty commands raise approval requests instead of writing gated data directly.

2. Status

Field Value
State BACKLOG
Parent sprint Sprint 30
Now Not yet started.
Waiting on Nothing.
Next Break the story into tasks.
Last touched 2026-11-08

3. Acceptance

  • The party details, instrument convention and tenor resolution screens raise a request for a gated change instead of writing it.
  • The ORE import raises approval requests for the gated books it creates.
  • The shell counterparty identifier commands raise approval requests for gated writes.

4. Tasks

Task State Start End Description
Move the convention screen onto the review panel BACKLOG     Make the instrument convention screen raise a request for every write.
Move the counterparty screen onto the review panel BACKLOG     Build the counterparty as a record screen like the parties screen, where a gated change raises a request and a contact change is written directly.
Move the party details screen onto the review panel BACKLOG     Make the party details screen raise a request for a gated change instead of writing it.
Move the tenor resolution screen onto the review panel BACKLOG     Make the tenor resolution screen raise a request for every write.
Raise requests from the ORE import for gated books BACKLOG     Make the ORE import raise approval requests for the books it creates, because the gate now refuses a direct book write.
Raise requests from the shell for gated counterparties BACKLOG     Make the shell counterparty identifier commands raise approval requests, because the gate now refuses a direct write.

5. Decisions

6. Out of scope

Emacs 29.3 (Org mode 9.6.15)