Show honest qualifying-day progress and confidence #77

Closed
opened 2026-09-13 21:03:29 +00:00 by xavierk · 0 comments
Owner

Parent

Implement Fenris TUI polish and hourly history

What to build

Users see meaningful UTC evidence progress and truthful lifespan availability, without confusing first graph data, warm-up clearance and Supported confidence. Covers remaining TPH-4/7 qualification and confidence behavior.

Implement the approved companion contract and applicable TPH acceptance amendments linked from the parent. Preserve the frozen redesign, lifecycle/security boundaries, existing evidence thresholds and mathematics except explicit approved accounting amendments. Reuse existing seams; any necessary prefactoring precedes behavior changes within this slice. No release, deployment, or parent-issue changes.

Acceptance criteria

  • Coverage is elapsed classified monitored seconds divided by elapsed represented monitored seconds, independent of byte-allocation completeness. Current UTC date qualifies provisionally at ≥50% coverage, counts once, may regress, and entirely paused dates do not count. No unsupported sample-per-date requirement is added.
  • Current controller segment clears warm-up at ≥14 represented UTC dates with ≥12 qualifying; old poor dates do not permanently veto clearance. Supported separately needs ≥14 qualifying dates and all existing numerical/evidence requirements. Same-day segment fragments cannot borrow previous-segment qualification.
  • Render the approved Building evidence — N of 14 days observed · Q qualifying and First lifespan estimate after 12 qualifying days block, with both gate requirements explicit through the facts. No hours countdown or guarantee that elapsed waiting creates a valid rate or Supported confidence.
  • Habit-change checks use completed consecutive UTC dates with evaluable totals; missing dates cannot become adjacent rows or zero usage. Unknown daily totals block burst/concentration and dependent Supported checks; use the observed eligible part of the 28-day burst span without inventing new minimum horizons.
  • TUI and CLI retain explicit baseline/counter/numerator/re-warm/zero-rate reasons and frozen stale-estimate note. Once eligible, preserve existing lifespan format and Limited/Supported labels; graph remains visible independently.
  • Test public projection and rendered parity for 12 qualifying plus 2 poor dates, 14 qualifying with other prerequisites satisfied/failed, provisional regression, paused dates, same-day resets, good coverage with unknown bytes, consecutive-day gaps, short history and stale evidence. No change to lifespan mathematics or threshold constants.

Blocked by

## Parent [Implement Fenris TUI polish and hourly history](https://git.bongbetic.com/xavierk/Fenris/issues/72) ## What to build Users see meaningful UTC evidence progress and truthful lifespan availability, without confusing first graph data, warm-up clearance and Supported confidence. Covers remaining TPH-4/7 qualification and confidence behavior. Implement the approved companion contract and applicable TPH acceptance amendments linked from the parent. Preserve the frozen redesign, lifecycle/security boundaries, existing evidence thresholds and mathematics except explicit approved accounting amendments. Reuse existing seams; any necessary prefactoring precedes behavior changes within this slice. No release, deployment, or parent-issue changes. ## Acceptance criteria - [ ] Coverage is elapsed classified monitored seconds divided by elapsed represented monitored seconds, independent of byte-allocation completeness. Current UTC date qualifies provisionally at ≥50% coverage, counts once, may regress, and entirely paused dates do not count. No unsupported sample-per-date requirement is added. - [ ] Current controller segment clears warm-up at ≥14 represented UTC dates with ≥12 qualifying; old poor dates do not permanently veto clearance. Supported separately needs ≥14 qualifying dates and all existing numerical/evidence requirements. Same-day segment fragments cannot borrow previous-segment qualification. - [ ] Render the approved Building evidence — N of 14 days observed · Q qualifying and First lifespan estimate after 12 qualifying days block, with both gate requirements explicit through the facts. No hours countdown or guarantee that elapsed waiting creates a valid rate or Supported confidence. - [ ] Habit-change checks use completed consecutive UTC dates with evaluable totals; missing dates cannot become adjacent rows or zero usage. Unknown daily totals block burst/concentration and dependent Supported checks; use the observed eligible part of the 28-day burst span without inventing new minimum horizons. - [ ] TUI and CLI retain explicit baseline/counter/numerator/re-warm/zero-rate reasons and frozen stale-estimate note. Once eligible, preserve existing lifespan format and Limited/Supported labels; graph remains visible independently. - [ ] Test public projection and rendered parity for 12 qualifying plus 2 poor dates, 14 qualifying with other prerequisites satisfied/failed, provisional regression, paused dates, same-day resets, good coverage with unknown bytes, consecutive-day gaps, short history and stale evidence. No change to lifespan mathematics or threshold constants. ## Blocked by - [Show evidence-anchored projection rates](https://git.bongbetic.com/xavierk/Fenris/issues/76)
xavierk added the ready-for-agent label 2026-09-13 21:03:29 +00:00
xavierk added a new dependency 2026-09-13 21:04:17 +00:00
xavierk added a new dependency 2026-09-13 21:04:24 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: xavierk/Fenris#77