Story: Implement the full report pipeline
Table of Contents
This page documents a story in Product backlog — inbox. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
One report definition runs end to end from the scheduler through the workflow to the compute grid and back, with report pre- and post-processing, the orchestration contract, the substituted and live proofs, and a measured baseline. The design, the documentation and the run configuration shipped with the source story; this story is the implementation. The target state is written as Report Processing.
This story was split from Run a full report: scheduling, reporting and compute when that story was reworded to the design and the run configuration it delivered and closed DONE at the sprint 26 close on 2026-10-05; its eight remaining tasks moved here.
2. Status
| Field | Value |
|---|---|
| State | BACKLOG |
| Parent sprint | Sprint 26 |
| Now | Not yet started. |
| Waiting on | Nothing. |
| Next | Implement the phases, define the orchestration contract, and prove both runs. |
| Last touched | 2026-10-05 |
3. Acceptance
- A run with both ends substituted executes the real scheduler, the real workflow, the real grid and the real storage, and records that it was substituted.
- A run with neither end substituted reads live trades and market data, and records the engine's results.
- Report processing has a measured baseline, and the reporting handlers use the engine's idempotency check.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Implement Run a full report: scheduling, reporting and compute | BACKLOG | Initial task for: Run a full report: scheduling, reporting and compute | ||
| Implement report post-processing | BACKLOG | Task for: Run a full report: scheduling, reporting and compute | ||
| Implement report pre-processing | BACKLOG | Task for: Run a full report: scheduling, reporting and compute | ||
| Measure report processing and record a baseline | BACKLOG | Task for: Run a full report: scheduling, reporting and compute | ||
| Define and enforce the orchestration contract | BACKLOG | Task for: Run a full report: scheduling, reporting and compute | ||
| Prove the full pipeline against live data | BACKLOG | Task for: Run a full report: scheduling, reporting and compute | ||
| Prove the pipeline with both ends substituted | BACKLOG | Task for: Run a full report: scheduling, reporting and compute | ||
| Use the engine's idempotency check in the reporting handlers | BACKLOG | No reporting handler checks whether the step it is answering has already run, so a run recovered after a restart repeats the work of every phase it re-dispatches. | ||
| Price the bonds a report run carries | DONE | 2026-10-16 | Task for: Implement the full report pipeline |