Run the cross-cutting acceptance sweep #32

Closed
opened 2026-08-31 18:24:39 +00:00 by xavierk · 0 comments
Owner

Parent

Implement the Fenris persistent TUI monitoring redesign

Canonical contracts: fenris-redesign spec · acceptance criteria — criterion IDs cited below live in the register.

What to build

The final green gate across everything the earlier tickets built. From synthetic observation stores, the TUI and fenris status render every realizable combination of confidence state × freshness grade × endurance-baseline tier exactly as the rule table and freshness constants dictate — headline number present only when the rules allow it, contributing facts always, never a percentage. Every TUI action has a CLI twin with identical outcomes and wording. The prohibition set holds as automated checks: single acquisition path, one-key configuration, no alerting or notification machinery anywhere, no /run surface, no stored projections, no partial interpretation of newer-schema stores, no synthetic baselines, polkit authorizing exactly one binary. The fixed user-facing phrases and the six disclosures audit clean in both views.

Acceptance criteria

  • Exhaustive state matrix: TUI and status render every confidence-state × freshness × baseline-tier combination per the rule table and constants — headline only when allowed, facts always, never a percentage (CI-1)
  • TUI/CLI parity: pause, resume, collect-now, baseline set/clear, and the status fact set behave identically with identical wording (CI-2)
  • Prohibition set verified as automated checks, each citing its clause (CI-3)
  • Required wording and six disclosures render as adopted in both views; exact phrases for zero-rate, unavailable, and fault cases (CI-4)

Blocked by

## Parent [Implement the Fenris persistent TUI monitoring redesign](https://git.bongbetic.com/xavierk/Fenris/issues/20) Canonical contracts: [fenris-redesign spec](https://git.bongbetic.com/xavierk/Fenris/src/branch/main/docs/spec/fenris-redesign.md) · [acceptance criteria](https://git.bongbetic.com/xavierk/Fenris/src/branch/main/docs/spec/acceptance-criteria.md) — criterion IDs cited below live in the register. ## What to build The final green gate across everything the earlier tickets built. From synthetic observation stores, the TUI and `fenris status` render every realizable combination of confidence state × freshness grade × endurance-baseline tier exactly as the rule table and freshness constants dictate — headline number present only when the rules allow it, contributing facts always, never a percentage. Every TUI action has a CLI twin with identical outcomes and wording. The prohibition set holds as automated checks: single acquisition path, one-key configuration, no alerting or notification machinery anywhere, no `/run` surface, no stored projections, no partial interpretation of newer-schema stores, no synthetic baselines, polkit authorizing exactly one binary. The fixed user-facing phrases and the six disclosures audit clean in both views. ## Acceptance criteria - [ ] Exhaustive state matrix: TUI and `status` render every confidence-state × freshness × baseline-tier combination per the rule table and constants — headline only when allowed, facts always, never a percentage (CI-1) - [ ] TUI/CLI parity: pause, resume, collect-now, baseline set/clear, and the status fact set behave identically with identical wording (CI-2) - [ ] Prohibition set verified as automated checks, each citing its clause (CI-3) - [ ] Required wording and six disclosures render as adopted in both views; exact phrases for zero-rate, unavailable, and fault cases (CI-4) ## Blocked by - [Build the Panes TUI](https://git.bongbetic.com/xavierk/Fenris/issues/28) - [Ship the fenris-monitor helper, polkit policy, and systemd units](https://git.bongbetic.com/xavierk/Fenris/issues/29)
xavierk added the ready-for-agent label 2026-08-31 18:25:37 +00:00
xavierk added this to the Build: Fenris persistent TUI monitoring redesign milestone 2026-08-31 18:25:39 +00:00
xavierk added a new dependency 2026-08-31 18:25:49 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: xavierk/Fenris#32