Add an archive inventory verb #264

Closed
opened 2026-07-13 18:06:14 +02:00 by claude · 1 comment
Collaborator

No CLI verb enumerates what the recorded archive contains; instruments and their m1 coverage are discoverable only by listing the archive directory outside aura (the built-in root, DEFAULT_DATA_PATH in the data-server crate). Campaign authoring — instrument matrices, window bounds, cross-instrument generalization — depends on exactly that inventory, and an agent operating through the CLI alone (the deployment posture) has no way to obtain it.

a895891 already derives archive bounds from the monthly file index; a thin aura data list (symbols) and aura data coverage <symbol> (first/last month, gaps) over the same index would close the gap headlessly.

No CLI verb enumerates what the recorded archive contains; instruments and their m1 coverage are discoverable only by listing the archive directory outside aura (the built-in root, `DEFAULT_DATA_PATH` in the data-server crate). Campaign authoring — instrument matrices, window bounds, cross-instrument generalization — depends on exactly that inventory, and an agent operating through the CLI alone (the deployment posture) has no way to obtain it. a895891 already derives archive bounds from the monthly file index; a thin `aura data list` (symbols) and `aura data coverage <symbol>` (first/last month, gaps) over the same index would close the gap headlessly.
claude added the feature label 2026-07-13 18:06:14 +02:00
Author
Collaborator

Concrete failure illustrating the gap: a 22-instrument campaign (8.5-y window from 2018-01-01) aborted mid-run with aura: no data for instrument Copper in window [1514764800000, 1522540799999] — the Copper archive has monthly files from 2016-08 but is missing 2018-01 through 2018-10, so a first/last-file coverage check passes while the window start has no data. The abort came ~6.7 minutes in and discarded the ~36 already-computed cells; the three-tier validate cannot catch it because the executable tier is data-free by design. A coverage verb reporting per-symbol month gaps (not just bounds) would have caught this before the run.

Concrete failure illustrating the gap: a 22-instrument campaign (8.5-y window from 2018-01-01) aborted mid-run with `aura: no data for instrument Copper in window [1514764800000, 1522540799999]` — the Copper archive has monthly files from 2016-08 but is missing 2018-01 through 2018-10, so a first/last-file coverage check passes while the window start has no data. The abort came ~6.7 minutes in and discarded the ~36 already-computed cells; the three-tier validate cannot catch it because the executable tier is data-free by design. A coverage verb reporting per-symbol month gaps (not just bounds) would have caught this before the run.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Brummel/Aura#264