xavierk/Fenris
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases 11 Wiki Activity

Write the Fenris redesign specification and close the map #19

New Issue
Closed
opened 2026-08-31 18:01:52 +00:00 by xavierk · 1 comment
xavierk commented 2026-08-31 18:01:52 +00:00
Owner
Copy Link
Copy Source

Parent map: Chart Fenris's persistent TUI monitoring redesign

Question

The assembly decisions are settled on Assemble the implementation-ready specification (all seven recommendations accepted). Execute them:

  1. Verify first. Build the two-way ADR↔criterion traceability matrix — every ADR 0001–0006 section maps to at least one criterion ID; every criterion cites its ADR or ticket. Fill decided-but-uncritered gaps inline in docs/spec/acceptance-criteria.md, each new criterion citing its ADR. Escalate genuinely undecided behavior as a new blocking ticket before proceeding.
  2. Write docs/spec/fenris-redesign.md. Single document, data-flow ordered: system context → collector acquisition → observation store → controller identity & segmentation → hour/day derivation → projection & confidence → Panes TUI → service lifecycle & sanctioned toggle → failure & recovery → installation. Normatively restate every operative contract (the what); rationale (the why) stays in ADRs 0001–0006, cited per section. Restate the Panes TUI layout as normative requirements; the prototype branch is visual reference only. Each section opens with its ADR links and criterion-ID block. Status header links this map and the assembly decision. The traceability matrix is an appendix. docs/spec/acceptance-criteria.md and the ADRs remain canonical; the spec never restates criteria as criteria.
  3. Commit to main and post the resolution comment with the matrix result and the commit link.
  4. Close the map. Re-fetch the map, append this ticket to Decisions so far, and close it — the destination is reached when the spec is committed, the matrix is clean, and no tickets remain.

AFK: the agent drives this alone; no human input required.

Parent map: [Chart Fenris's persistent TUI monitoring redesign](https://git.bongbetic.com/xavierk/Fenris/issues/1) ## Question The assembly decisions are settled on [Assemble the implementation-ready specification](https://git.bongbetic.com/xavierk/Fenris/issues/17) (all seven recommendations accepted). Execute them: 1. **Verify first.** Build the two-way ADR↔criterion traceability matrix — every ADR 0001–0006 section maps to at least one criterion ID; every criterion cites its ADR or ticket. Fill decided-but-uncritered gaps inline in `docs/spec/acceptance-criteria.md`, each new criterion citing its ADR. Escalate genuinely undecided behavior as a new blocking ticket before proceeding. 2. **Write `docs/spec/fenris-redesign.md`.** Single document, data-flow ordered: system context → collector acquisition → observation store → controller identity & segmentation → hour/day derivation → projection & confidence → Panes TUI → service lifecycle & sanctioned toggle → failure & recovery → installation. Normatively restate every operative contract (the *what*); rationale (the *why*) stays in ADRs 0001–0006, cited per section. Restate the Panes TUI layout as normative requirements; the prototype branch is visual reference only. Each section opens with its ADR links and criterion-ID block. Status header links this map and the assembly decision. The traceability matrix is an appendix. `docs/spec/acceptance-criteria.md` and the ADRs remain canonical; the spec never restates criteria as criteria. 3. **Commit to `main`** and post the resolution comment with the matrix result and the commit link. 4. **Close the map.** Re-fetch [the map](https://git.bongbetic.com/xavierk/Fenris/issues/1), append this ticket to Decisions so far, and close it — the destination is reached when the spec is committed, the matrix is clean, and no tickets remain. AFK: the agent drives this alone; no human input required.
xavierk added the wayfinder:task label 2026-08-31 18:01:53 +00:00
xavierk added this to the Wayfinder: Fenris persistent TUI monitoring redesign milestone 2026-08-31 18:01:55 +00:00
xavierk self-assigned this 2026-08-31 18:04:26 +00:00
xavierk commented 2026-08-31 18:13:48 +00:00
Author
Owner
Copy Link
Copy Source

Resolution — AFK task; executed the assembly decisions of #17.

1. Matrix result (built first). Two-way ADR↔criterion traceability verified across ADRs 0001–0006: all 52 ADR sections map to ≥ 1 criterion; every criterion carries its ADR/ticket citation (Appendix A of the spec).

  • Decided-but-uncitered gaps found and filled inline in docs/spec/acceptance-criteria.md: CI-3 bullet (no /run coordination surface; ADR 0003 §1, ADR 0001 §2), PR-17 (projection arithmetic E_rated/E_implied/projected; ADR 0002 §2), TUI-4 (normative Panes layout regions + production bindings; ticket #3), IN-10 (fixed artifact placement; ADR 0004 §2, ADR 0003 §4) — commit ff51be2.
  • No genuinely undecided behavior remained — no blocking ticket raised.
  • One reconciliation: ADR 0004 §6's "schema_version table" wording resolves to ADR 0001 §8's PRAGMA user_version as the single version authority (criterion ST-12 already fixed it); noted in spec §3.6.

2. Specification committed: docs/spec/fenris-redesign.md at commit 566d1c8 — 654 lines, data-flow ordered (system context → collector acquisition → observation store → controller identity & segmentation → hour/day derivation → projection & confidence → Panes TUI → service lifecycle & sanctioned toggle → failure & recovery → installation), each section opening with ADR links and a criterion-ID block; normative constants index; the six disclosures and fixed user-facing wording (§6.11); the Panes layout as normative requirements with the prototype cited as visual reference only; traceability matrix as Appendix A. Both commits pushed to main.

3. Handoff is complete: spec + criteria register + ADRs 0001–0006 + CONTEXT.md glossary, implementer-agnostic.

4. Destination reached — the map closes with this ticket.

**Resolution — AFK task; executed the assembly decisions of [#17](https://git.bongbetic.com/xavierk/Fenris/issues/17).** **1. Matrix result (built first).** Two-way ADR↔criterion traceability verified across ADRs 0001–0006: all 52 ADR sections map to ≥ 1 criterion; every criterion carries its ADR/ticket citation (Appendix A of the spec). - **Decided-but-uncitered gaps found and filled inline** in [docs/spec/acceptance-criteria.md](https://git.bongbetic.com/xavierk/Fenris/src/branch/main/docs/spec/acceptance-criteria.md): **CI-3** bullet (no `/run` coordination surface; ADR 0003 §1, ADR 0001 §2), **PR-17** (projection arithmetic `E_rated`/`E_implied`/`projected`; ADR 0002 §2), **TUI-4** (normative Panes layout regions + production bindings; ticket #3), **IN-10** (fixed artifact placement; ADR 0004 §2, ADR 0003 §4) — commit ff51be2. - **No genuinely undecided behavior remained** — no blocking ticket raised. - **One reconciliation:** ADR 0004 §6's "`schema_version` table" wording resolves to ADR 0001 §8's `PRAGMA user_version` as the single version authority (criterion ST-12 already fixed it); noted in spec §3.6. **2. Specification committed:** [docs/spec/fenris-redesign.md](https://git.bongbetic.com/xavierk/Fenris/src/branch/main/docs/spec/fenris-redesign.md) at commit 566d1c8 — 654 lines, data-flow ordered (system context → collector acquisition → observation store → controller identity & segmentation → hour/day derivation → projection & confidence → Panes TUI → service lifecycle & sanctioned toggle → failure & recovery → installation), each section opening with ADR links and a criterion-ID block; normative constants index; the six disclosures and fixed user-facing wording (§6.11); the Panes layout as normative requirements with the prototype cited as visual reference only; traceability matrix as Appendix A. Both commits pushed to `main`. **3. Handoff is complete:** spec + criteria register + ADRs 0001–0006 + `CONTEXT.md` glossary, implementer-agnostic. **4. Destination reached** — the map closes with this ticket.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ready-for-agent
Spec triaged and ready for an implementing agent
 wayfinder:grilling
HITL conversational decision ticket
 wayfinder:map
Canonical Wayfinder decision map
 wayfinder:prototype
HITL prototype decision ticket
 wayfinder:research
AFK research decision ticket
 wayfinder:task
Prerequisite task ticket
No labels wayfinder:task
Milestone
No items
No Milestone Wayfinder: Fenris persistent TUI monitoring redesign
Projects
Clear projects
No projects
Assignees
Clear assignees
xavierk (Xavier Karma)
No Assignees xavierk
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: xavierk/Fenris#19