eric/weatherreporter
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Correct documentation refresh findings

Browse Source
This commit is contained in:
Eric Rakestraw
2026-07-31 01:59:13 +00:00
parent 35f4f82e94
commit 5e96790d85
5 changed files with 20 additions and 643 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/policy/architecture.md
View File

@@ -17,9 +17,10 @@ mechanics must preserve.
Weatherreporter is a deterministic weather briefing and report-preparation CLI.
It consumes normalized weather data, derives report facts and module snapshots,
builds curated prompt packages, compares structured snapshots with prior runs,
invokes Scriptorium for bounded generated text, renders managed Markdown
reports, persists inspectable artifacts, and can upload completed reports
through Distributor.
and invokes Scriptorium either to produce managed Markdown directly or to
produce bounded generated-text prose for repository-owned templates. It
persists inspectable artifacts and can upload completed reports through
Distributor.
The application is intentionally a small, explicit, dependency-light Go
program. Add abstraction only when it protects a real boundary, makes an
@@ -32,8 +33,9 @@ The primary flow is:
3. normalized weather collection;
4. deterministic fact derivation and module construction;
5. structured prior-snapshot comparison;
6. curated prompt input and generated-text processing;
7. managed Markdown rendering and metadata persistence; and
6. curated prompt input and report-mode-specific Scriptorium processing;
7. generated-text validation when applicable, managed Markdown production,
and metadata persistence; and
8. optional notification using managed report artifacts.
Inspection is a separate read-only flow over persisted state. It must not
@@ -128,10 +130,14 @@ lookup. Keep weather derivation and path construction out of templates.
weather facts.
- LLM prompts receive curated module-based packages rather than raw,
unbounded source payloads.
- Generated text is limited to defined prose slots, validated before use, and
rendered through typed or otherwise explicit contexts.
- Templates arrange validated prose and deterministic facts; they do not
perform meteorological derivation.
- For generated-text-template reports, generated text is limited to defined
prose slots, validated before use, and rendered through typed or otherwise
explicit contexts.
- Direct-Markdown reports receive the same curated prompt-package boundary but
produce managed Markdown directly through Scriptorium rather than the
generated-text schema and repository-template workflow.
- Repository-owned templates arrange validated prose and deterministic facts;
they do not perform meteorological derivation.
### Reports And Comparison