Task: Seed ACME with the report type, the bundle and the definition
Table of Contents
This page documents a task in the Prove the report grid run end to end — the remaining work story. It captures the goal, current status, acceptance, and any notes or results.
1. Goal
The story needs a report type, a definition owned by an ACME party, and the input the run consumes, all reproducible from a freshly recreated database. The existing fixture is owned by the system party because a business-party-owned definition is invisible to a session scoped elsewhere, so the ACME definition needs a session that can see ACME.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent story | Prove the report grid run end to end — the remaining work |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-21 |
3. Acceptance
- After a database recreate, ACME carries the new report type and the definition, and a session that can see ACME can trigger it.
- The input the chosen chain consumes exists in storage at the keys that chain expects.
- The tenant has a compute app version, without which submit fails.
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. Notes
6. 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 |
|---|---|---|
7. PRs
| PR | Title |
|---|---|
| #3745 | [agile] Close the seed task and record the analytic-switch gap |
8. Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|
9. Result
A recreate followed by one provision gives a triggerable report, and the run's inputs reached storage.
- After a database recreate the ACME tenant carries the report type and 78
report definitions. A session acting for
Acme Corporation Plctriggered "Audit Trail Summary" (definition831711f4-d9f1-4f39-b5da-246e202fbc7e), and instance25922e99-e541-44ca-ab22-c6b7ddbc558awalked pending, running and completed. - The chain's inputs exist where it expects them. The run left
reporting/runs/25922e99-e541-44ca-ab22-c6b7ddbc558a/holdingtrades.msgpack,market_data.txtandfixings.txt, and builtore/packages/25922e99-.../ore_package.tar.gz. The engine read that package and loggedBuilt Portfolio. Initial size = 8, size now 8, built 0 failed trades. - The tenant has compute app versions. The provision publishes
1.8.16.0-4-g3b62ba248and1.8.17.0. Dispatch used608de93d-b96d-455a-925b-1d31ca3d6234, and a wrapper claimed the work, so submit did not fail for want of an app version.
The evidence is recorded in full, with every id, on Prove the run end to end and keep it repeatable.