Keep local-day history trustworthy after detail expires #93

New Issue

2026-09-17T10:33:44Z

xavierk commented

2026-09-17 10:33:44 +00:00

Parent

Implement live daily drive activity, keyboard date navigation, and an endurance outlook

What to build

After three-minute detail ages beyond 14 days, users can still read trustworthy hourly/daily activity summaries with their original timezone and visible evidence limits. Complete the prune, repair, upgrade, and aged-history read lifecycle around the local-day summaries already introduced. Demonstrate the behavior through the existing history/readout views or public reader; the new keyboard-navigation ticket is not a prerequisite.

All behavior follows the parent specification, including its precedence over conflicting earlier TUI requirements. The approved proof uses controlled acquisition and time through a real observation store into public TUI/CLI results; preserve the existing collector/reader ownership and no-fabrication rules.

Acceptance criteria

Advance controlled time through the 14-day detail boundary, run the normal retention path, reopen readers/TUI, and verify that eligible detail expires while hourly/daily summaries remain available at their actual precision.
Before pruning any source evidence, preserve the summaries, unresolved boundary evidence, and required anchors needed for future derivation and interpretation. Do not retain every fine-grained interval indefinitely solely for arbitrary timezone regrouping.
Aged local summaries retain recorded timezones and boundaries after a system-timezone change; historical volume must not silently move between dates. Make recorded timezone and unavailable precision visible in the history readout.
Legacy data with surviving raw evidence can be conservatively derived; legacy UTC summaries that cannot establish a local-day total remain labelled incomplete/unavailable at that precision. Preserve valid old summaries and never replace them with fabricated finer-grained evidence.
Migration, pruning, and repair are interruption-safe and idempotent. Repeated operations and restart neither lose retained measured evidence nor duplicate boundary deltas. Respect concurrent readers and newer-schema/store-fault behavior.
Attributable summary volume plus separately retained unallocated boundary evidence conserves each measured delta once. Do not count midnight-spanning bytes in both endpoint days or hide their uncertainty.
Use existing retention, migration, and repair entry points with real temporary stores, injected time, and normal readers; add targeted persistence assertions only for safety properties not observable through the public result.
Verify the user-visible transition from recent detail to older summaries, including measured zero, gaps, incomplete dates, and preserved read/write totals. The result must remain useful without the new date-entry controls.
Document the 14-day detail versus indefinite-summary policy and the deliberate historical-timezone trade-off. Preserve existing durable evidence; this feature is not authorization for unrelated history deletion.

Blocked by

Show trustworthy local-day activity totals

## Parent [Implement live daily drive activity, keyboard date navigation, and an endurance outlook](https://git.bongbetic.com/xavierk/Fenris/issues/88) ## What to build After three-minute detail ages beyond 14 days, users can still read trustworthy hourly/daily activity summaries with their original timezone and visible evidence limits. Complete the prune, repair, upgrade, and aged-history read lifecycle around the local-day summaries already introduced. Demonstrate the behavior through the existing history/readout views or public reader; the new keyboard-navigation ticket is not a prerequisite. All behavior follows the parent specification, including its precedence over conflicting earlier TUI requirements. The approved proof uses controlled acquisition and time through a real observation store into public TUI/CLI results; preserve the existing collector/reader ownership and no-fabrication rules. ## Acceptance criteria - [ ] Advance controlled time through the 14-day detail boundary, run the normal retention path, reopen readers/TUI, and verify that eligible detail expires while hourly/daily summaries remain available at their actual precision. - [ ] Before pruning any source evidence, preserve the summaries, unresolved boundary evidence, and required anchors needed for future derivation and interpretation. Do not retain every fine-grained interval indefinitely solely for arbitrary timezone regrouping. - [ ] Aged local summaries retain recorded timezones and boundaries after a system-timezone change; historical volume must not silently move between dates. Make recorded timezone and unavailable precision visible in the history readout. - [ ] Legacy data with surviving raw evidence can be conservatively derived; legacy UTC summaries that cannot establish a local-day total remain labelled incomplete/unavailable at that precision. Preserve valid old summaries and never replace them with fabricated finer-grained evidence. - [ ] Migration, pruning, and repair are interruption-safe and idempotent. Repeated operations and restart neither lose retained measured evidence nor duplicate boundary deltas. Respect concurrent readers and newer-schema/store-fault behavior. - [ ] Attributable summary volume plus separately retained unallocated boundary evidence conserves each measured delta once. Do not count midnight-spanning bytes in both endpoint days or hide their uncertainty. - [ ] Use existing retention, migration, and repair entry points with real temporary stores, injected time, and normal readers; add targeted persistence assertions only for safety properties not observable through the public result. - [ ] Verify the user-visible transition from recent detail to older summaries, including measured zero, gaps, incomplete dates, and preserved read/write totals. The result must remain useful without the new date-entry controls. - [ ] Document the 14-day detail versus indefinite-summary policy and the deliberate historical-timezone trade-off. Preserve existing durable evidence; this feature is not authorization for unrelated history deletion. ## Blocked by - [Show trustworthy local-day activity totals](https://git.bongbetic.com/xavierk/Fenris/issues/90)

xavierk added the ready-for-agent label 2026-09-17 10:33:44 +00:00

xavierk added a new dependency 2026-09-17 10:34:10 +00:00

#90 Show trustworthy local-day activity totals

xavierk referenced this issue from a commit

2026-09-18 09:36:07 +00:00

Keep local-day history trustworthy after detail expires (#93)

xavierk closed this issue

2026-09-18 09:36:33 +00:00

Sign in to join this conversation.