Task: Read each document's rows by its parent
Table of Contents
This page documents a task in the Complete the ORE report configuration story. It captures the goal, current status, acceptance, and any notes or results.
1. Goal
Exporting one document reads only that document's rows.
2. Status
| Field | Value |
|---|---|
| State | BACKLOG |
| Parent story | Complete the ORE report configuration |
| Now | Not yet started. |
| Waiting on | Nothing. |
| Next | Begin implementation. |
| Last touched | 2026-10-04 |
3. Acceptance
- Every read in the document store and the run store selects by the parent's id in SQL.
- The round-trip tests pass unchanged.
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
Raised on 2026-10-04 from the open items left after Import a run's configuration from an ORE input directory and Produce the engine's input from the entities.
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 |
|---|---|
9. Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|