Task: Scaffold story: Run a full report: scheduling, reporting and compute

Table of Contents

This page documents a task in the Run a full report: scheduling, reporting and compute story. It captures the goal, current status, acceptance, and any notes or results.

1. Goal

(Describe what user-visible-or-internal change this task produces.)

2. Status

Field Value
State DONE
Parent story Run a full report: scheduling, reporting and compute
Now Nothing.
Waiting on Nothing.
Next Nothing.
Last touched 2026-09-27

3. Acceptance

4. Plan

(Implementation strategy. Written when work starts; key decisions are distilled into the parent story's * Decisions at close, but the plan itself stays — it is the historical record of what we did.)

5. Measurements

Every number this task claims about a tree, with the command that produced it and the commit it was measured at. A number without both is not a measurement, because a clean-up record describes a tree and trunk moves under a branch: a consumer count, a gate's component count and a suite's size all change with no code changing, and the reader of a bare number cannot tell which tree it came from. Where the raw output matters, put it in an evidence/ file beside the task and name that file in the Command column.

What Value Command Commit
       

6. Notes

7. Test Scenarios

Manual QA scenarios (scaffolded via compass add test_scenario) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.

Scenario State Notes
     

8. PRs

PR Title
#2278 [reporting] Design the two-mode report pipeline

9. Review

Comment summary File Decision Notes
       

10. Result

Delivered. The story is wired into Sprint 26 with four tasks, and the target architecture is written as Report Processing, a knowledge page rather than a story document, because the target outlives the story. That page replaced an earlier single document, written under the same task, whose subject was the run's modes rather than the pipeline.

The story was framed as "integrate scheduling, reporting and compute". The design found that the integration already exists along one path — the shell can drive a batch to completion — and fails along the path the story needs, because the reporting to compute handoff publishes on a subject no wrapper subscribes to, leaves the workunit's fields empty, and hands over a URI in the wrong shape. That work is the ACME smoke-test story's and this one waits on it, recorded on the story so the dependency is visible rather than implicit.

Four tasks carry the rest: design, the execution mode together with role-addressed step results, demo mode end to end, and full mode. The fourth is deliberately deferred.

Emacs 29.3 (Org mode 9.6.15)