❄ Views

Module: views

Derived summaries of the store. They are generated from ledger/ip-ledger.json and are never edited by hand — the value of a view is that it can be regenerated and rejected.

Responsibilities

• Answer the two questions asked most often: what is unused? and what can be dialled again?
• Group observations by the project that made them.

Key Files

• views/fresh-ips.json — criteria: *no observation with a real outcome — pulled, never spent*.
• views/reusable.json — criteria: *session_tag + url_template present (country selector included when the dialect needs it)*.
• views/by-project.json — observations grouped by project, with a note explaining the grouping.

Each view carries its own provenance — derived_from, criteria, generated_at — so a stale file can be recognised without guessing.

Current contents

All three views tell the truth as of 22 Sep 2026: fresh-ips.json and reusable.json report count: 0, and by-project.json groups 37 observations into outlook-creator (31) and grok-register (6). The zero for fresh is now a real answer rather than a stale one — the freshness test was repaired that day (see architecture.md) and every row carries a verdict. The zero for reusable remains structural: no row carries both a session_tag and a url_template.

Dependencies

• Used by: the CLI's views command to write them; anything that wants a cheap answer without parsing the store.
• Uses: the store, through the same load() path as everything else.

Notable Patterns / Gotchas

• A view is a photograph, not a source. generated_at is the only thing that tells you whether it is still true; nothing regenerates it automatically after an observe.
• A view is written into the house even when the store is a temp file. Overriding the store path for a test still writes views/ to the real directory — a test row carrying a reserved documentation IP and a fabricated future timestamp was found sitting in by-project.json on 22 Sep. Regenerate views after any test run, and read the newest entries before trusting the file.
• Empty is a valid answer. A zero here once meant the machinery was working correctly rather than broken; the difference is which rows exist, so read the store before doubting the view.