Story: Complete the ACME report inputs and prove they run
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
Add the analytic and exposure input documents the reports read through DQ, add a readiness check, give the platform reports their own report type, split an ORE file by a key, resolve the curve quote names against the feeds, and prove the exported packages run in ORE.
2. Status
| Field | Value |
|---|---|
| State | BACKLOG |
| Parent sprint | Sprint 30 |
| Now | The build-the-packages task is in flight: its kind lookup, its package chain and its two shell commands are written, and the branch is rebased onto sprint 28 main. |
| Waiting on | Nothing. |
| Next | Finish the build-the-packages task, then the input documents, the readiness check and the ORE run. |
| Last touched | 2026-11-08 |
3. Acceptance
- The simulation, sensitivity, stress test, historical return, Basel traffic light, SIMM calibration and credit simulation documents, and the exposure reports' input documents, are stored and published through DQ.
- A readiness check states, for each definition, what it lacks to run, and passes for every ACME definition after a clean provision.
- The exported run configuration of an ACME report runs through the ORE engine and matches what the report describes.
- The platform reports have a report type and a workflow of their own.
- The export writes one file per value of a key, and the curve quote names match the series the synthetic feeds produce.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Add the analytic configuration documents with DQ support | BACKLOG | Add the entities, document stores and DQ staging for the documents that analytics read: simulation, sensitivity, stress test, historical return, Basel traffic light, SIMM calibration and credit simulation. | ||
| Add the input documents the exposure reports read with DQ support | BACKLOG | Store the counterparty information, netting set definitions, collateral balances, calendar adjustment, currency configuration, reference data and IBOR fallback documents and publish them through DQ. | ||
| Build the ORE packages of a report locally | DONE | 2026-10-13 | 2026-11-08 | Shell commands that build, on the developer's machine, exactly the packages the compute grid would receive for a report, and fetch the packages of an earlier report instance. |
| Give the platform reports their own report type | BACKLOG | Take System Health, Audit Trail Summary and the three trade repository reports off the ORE report type, and give them a type and a workflow of their own. | ||
| Prove the exported packages run in ORE | BACKLOG | Run the exported run configuration of an ACME report through the ORE engine and compare the result with what the report describes. | ||
| Prove the ACME reports are ready to run | BACKLOG | Add a readiness check that states, for each definition, what it lacks to run, and show it passes for every ACME definition after a clean provision. | ||
| Resolve the curve quote names against the synthetic feeds | BACKLOG | Check that the quote keys of the ACME curve configurations match the series that the synthetic feeds produce, once the feed naming refactor lands. | ||
| Split an ORE file by a key | BACKLOG | Let the export write one file for each value of a key, such as one portfolio file for each book, using the name pattern of the file types table. | ||
| Create the intraday reports every ACME entity needs | BACKLOG | ACME's reports are end of day. Every ACME entity needs intraday reports as well. Begin by reading the report documentation to establish which intraday reports are required and for which entity, then build them. A report that runs intraday values at the present moment rather than at the previous close, so it also decides what the market data must supply during the day. |
5. Decisions
- Reviewed on 2026-11-08 at sprint 30 start. The story is wide but each task feeds the same outcome, an ACME report that runs in ORE.