# Weatherreporter Operations

## Normal Workflow

The implemented preparation workflow is:

```text
weatherreporter generate daily --date 2026-05-29
```

The command fetches weather data, builds the Daily briefing, builds the prompt
input data package, runs `scriptorium render`, and writes inspectable artifacts
under the configured workspace.

## Filesystem Layout

The default workspace root is `workspace`.

```text
workspace/
  snapshots/
    daily/
      YYYY-MM-DD/
        <run_id>.briefing.json
        <run_id>.metadata.json
  data-packages/
    daily/
      YYYY-MM-DD/
        <run_id>.data_package.json
  preflight/
    daily/
      YYYY-MM-DD/
        <run_id>.render.json
  reports/
    daily/
      <run_id>.md
```

The report path is reserved in metadata for the eventual rendered report. The
current workflow does not write the Markdown report.

## Run Identifiers

Run IDs are based on generation time plus report ID, such as:

```text
20260529T100000.123456789Z_daily_today
```

Managed artifact filenames use the RunID so repeated runs for the same valid
date do not overwrite each other.

## Metadata

Each Daily preparation writes metadata that links:

- RunID
- report ID and prompt ID
- generation time and valid period
- source location, source hashes, and source warnings
- briefing snapshot path
- prompt input data package path
- preflight output path
- reserved rendered report path

## Recovery

If render preflight exits nonzero after producing a result, the captured stdout,
stderr, exit code, and command are still written to the preflight artifact, and
metadata is still written for inspection.

The application does not currently implement resume, cleanup, archive, or
remote storage behavior.