Story: Trace a process run and the trade groups it creates

Table of Contents

This page documents a story in Sprint 28, carried unfinished from Sprint 27 at close. It captures the goal, current status, acceptance criteria, and the tasks that compose it.

1. Goal

Record one run of a process over a set of trades: its identity, its state machine, the process it is a run of, and the trade groups that carry what the run read and what it wrote. The record is what lets a process be undone or repeated.

2. Status

Field Value
State ABANDONED
Parent sprint Sprint 28
Now Nothing.
Waiting on Nothing.
Next Nothing.
Last touched 2026-10-24

3. Acceptance

Nothing shipped under this story. Its one finished task only scaffolded the story. The tasks that carry the work moved to the story named in Decisions.

4. Tasks

Task State Start End Description
Scaffold story: Trace a process run and the trade groups it creates DONE 2026-10-08 2026-10-08 Story scaffolding rides this task: documents, sprint wiring, and the scaffold PR. Close it before merging that PR.

5. Decisions

5.1. The run is modelled against a client process, not in the abstract

Taken 2026-10-08 with the owner. A process run exists so that a process can be undone and repeated, and no process is implemented. Modelling a run before a process has a client would fix its shape against nothing. This story therefore waits on one process with a real client, the funding roll or the spot sweep, and the first task after the scaffold is to settle the run against that pilot.

The trade set model settled on 2026-10-08 supplies what the run needs and did not have: the trade group, its membership, the read and write sets, and the roles the process declares. That work is in Trade sets and trade groups.

The shape is written down in Trace a process run over a set of trades. It is roughly the shape and not yet a design.

6. Out of scope

Emacs 29.3 (Org mode 9.6.15)