Add 3-Day Outlook generation
This commit is contained in:
@@ -2,18 +2,21 @@
|
||||
|
||||
## Normal Workflow
|
||||
|
||||
The implemented Daily-family generation workflows are:
|
||||
The implemented generation workflows are:
|
||||
|
||||
```text
|
||||
weatherreporter generate daily --date 2026-05-29
|
||||
weatherreporter generate tomorrow
|
||||
weatherreporter generate three-day
|
||||
weatherreporter run evening
|
||||
```
|
||||
|
||||
These commands fetch weather data, build a Daily briefing for the resolved
|
||||
valid date, build the prompt input data package, run `scriptorium render`, run
|
||||
These commands fetch weather data, build a briefing for the resolved valid
|
||||
period, build the prompt input data package, run `scriptorium render`, run
|
||||
`scriptorium run`, and write inspectable artifacts under the configured
|
||||
workspace. The evening run resolves only the Tomorrow Planning Brief.
|
||||
workspace. The evening run resolves only the Tomorrow Planning Brief. The
|
||||
morning run can generate Daily Today and the 3-Day Outlook when the resolved
|
||||
batch does not include an unsupported report type.
|
||||
|
||||
## Filesystem Layout
|
||||
|
||||
@@ -26,22 +29,34 @@ workspace/
|
||||
YYYY-MM-DD/
|
||||
<run_id>.briefing.json
|
||||
<run_id>.metadata.json
|
||||
three-day/
|
||||
YYYY-MM-DD/
|
||||
<run_id>.briefing.json
|
||||
<run_id>.metadata.json
|
||||
data-packages/
|
||||
daily/
|
||||
YYYY-MM-DD/
|
||||
<run_id>.data_package.json
|
||||
three-day/
|
||||
YYYY-MM-DD/
|
||||
<run_id>.data_package.json
|
||||
preflight/
|
||||
daily/
|
||||
YYYY-MM-DD/
|
||||
<run_id>.render.json
|
||||
three-day/
|
||||
YYYY-MM-DD/
|
||||
<run_id>.render.json
|
||||
reports/
|
||||
daily/
|
||||
<run_id>.md
|
||||
three-day/
|
||||
<run_id>.md
|
||||
```
|
||||
|
||||
The Markdown report is written to a RunID-managed report path. When `--out` is
|
||||
provided to `generate daily` or `generate tomorrow`, the managed report is also
|
||||
copied to that path.
|
||||
provided to `generate daily`, `generate tomorrow`, or `generate three-day`, the
|
||||
managed report is also copied to that path.
|
||||
|
||||
## Run Identifiers
|
||||
|
||||
@@ -56,7 +71,7 @@ date do not overwrite each other.
|
||||
|
||||
## Metadata
|
||||
|
||||
Each Daily generation writes metadata that links:
|
||||
Each generated report writes metadata that links:
|
||||
|
||||
- RunID
|
||||
- report ID and prompt ID
|
||||
@@ -75,6 +90,9 @@ data package. Daily Today and Daily Tomorrow can compare with each other when
|
||||
they cover the same valid local date. Meaningful changes are included under
|
||||
`recentChanges.items`.
|
||||
|
||||
3-Day Outlook generation compares against a prior compatible 3-Day briefing
|
||||
snapshot for the same valid local date when one exists.
|
||||
|
||||
When no prior comparable snapshot exists, or no configured threshold is crossed,
|
||||
the Recent Changes list is empty.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user