Centralize report path policy

This commit is contained in:
2026-05-29 20:28:06 +00:00
parent 6915bf1ba2
commit 7dc2ac9253
7 changed files with 140 additions and 64 deletions

View File

@@ -54,16 +54,19 @@ Workspace subdirectories must be relative paths that stay under
## State Or Manifest Behavior
Managed paths are grouped by report family and valid-period start date for JSON
artifacts. Reports are written under the report group. Metadata is stored beside
briefing snapshots and links briefing, data package, preflight, and report
paths. Report listing walks metadata files under the snapshots directory.
Managed paths are grouped by the report definition's artifact group and
valid-period start date for JSON artifacts. Reports are written under the same
artifact group. Metadata is stored beside briefing snapshots and links
briefing, data package, preflight, and report paths. Report listing walks
metadata files under the snapshots directory.
Prior snapshot lookup reads metadata and selects the latest earlier compatible
snapshot. Daily Today and Daily Tomorrow are compatible with each other for the
same valid local date. 3-Day Outlook compares with prior 3-Day snapshots for
the same valid local date. Weekend Outlook compares with prior Weekend snapshots
for the same weekend window. Storm Report currently has no prior lookup.
Prior snapshot lookup reads metadata and selects the latest earlier snapshot
whose report ID is compatible according to the current report definition. Daily
Today and Daily Tomorrow are compatible with each other for the same valid local
date. 3-Day Outlook compares with prior 3-Day snapshots for the same valid
local date. Weekend Outlook compares with prior Weekend snapshots for the same
weekend window. Storm Report currently has no prior lookup because its
comparison strategy is not searched by the filesystem store.
## Skip And Resume Behavior