Make historical local-day evidence trustworthy #99

New Issue

2026-09-27T20:01:09Z

xavierk commented

2026-09-27 20:01:09 +00:00

Parent

Deepen observation-history publication, local-day evidence, and activity selection.

What to build

Make older local-day history honest when upgrading or repairing an existing observation store. Rebuild only dates whose surviving evidence supports their recorded local boundaries; preserve original evidence and trustworthy UTC history, but withhold an old local-day amount if its precision cannot be verified. Readers must not silently present unprovable totals as known or treat them as qualifying local-day evidence.

Acceptance criteria

Ordered versioned migration and repair are interruption-safe and idempotent; old local-day summaries with insufficient provenance become visibly unavailable while trustworthy UTC hour/day evidence is preserved.
Dates recoverable from surviving compatible intervals or trustworthy coarse evidence are rebuilt without double-counting overlapping sources, with recorded timezone, controller context and actual boundaries preserved.
A later system timezone change leaves historical labels and boundaries intact; migration does not manufacture local precision from a whole UTC hour straddling midnight.
TUI/CLI and the complete-observation-day projection gate consume only trustworthy reconstructed local evidence; store-fault/newer-schema refusal stays intact.
Verify through migration/repair of temporary observation stores and ordinary reader outcomes, including repeated repair and restart, not destructive resets or mock rows.

Blocked by

#98 Conserve local-day evidence.

## Parent [Deepen observation-history publication, local-day evidence, and activity selection](https://git.bongbetic.com/xavierk/Fenris/issues/95). ## What to build Make older local-day history honest when upgrading or repairing an existing observation store. Rebuild only dates whose surviving evidence supports their recorded local boundaries; preserve original evidence and trustworthy UTC history, but withhold an old local-day amount if its precision cannot be verified. Readers must not silently present unprovable totals as known or treat them as qualifying local-day evidence. ## Acceptance criteria - [ ] Ordered versioned migration and repair are interruption-safe and idempotent; old local-day summaries with insufficient provenance become visibly unavailable while trustworthy UTC hour/day evidence is preserved. - [ ] Dates recoverable from surviving compatible intervals or trustworthy coarse evidence are rebuilt without double-counting overlapping sources, with recorded timezone, controller context and actual boundaries preserved. - [ ] A later system timezone change leaves historical labels and boundaries intact; migration does not manufacture local precision from a whole UTC hour straddling midnight. - [ ] TUI/CLI and the complete-observation-day projection gate consume only trustworthy reconstructed local evidence; store-fault/newer-schema refusal stays intact. - [ ] Verify through migration/repair of temporary observation stores and ordinary reader outcomes, including repeated repair and restart, not destructive resets or mock rows. ## Blocked by - [#98 Conserve local-day evidence](https://git.bongbetic.com/xavierk/Fenris/issues/98).

xavierk added the ready-for-agent label 2026-09-27 20:01:09 +00:00

xavierk added a new dependency 2026-09-27 20:01:10 +00:00

#98 Conserve local-day evidence

xavierk referenced this issue

2026-09-27 20:01:11 +00:00

Prune detail safely through normal collection #100

xavierk added a new dependency 2026-09-27 20:01:12 +00:00

#100 Prune detail safely through normal collection

xavierk self-assigned this 2026-09-28 05:14:51 +00:00

xavierk referenced this issue from a commit

2026-09-28 07:43:08 +00:00

fix: rebuild trustworthy local-day evidence (#99)