frontend-patterns/research/reviews/NavigationCoverage.md
tegwick b8eec87f08 Distinguish feature organization from independent release boundaries
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
2026-09-26 23:06:16 +02:00

2.5 KiB
Raw Blame History

Research stream coverage — 2026-09-26

WP-0003 T01 working matrix. Entries mark located evidence, not completed streams.

Stream Current evidence Key gap / disagreement
A — GUI architecture B01/B02: Presentation Model and selectors Independent application uses and comparison with other controller/state models
B — Navigation/hypermedia N01–N04/N06: htmx, SvelteKit and browser history Framework examples versus pinned application behavior; direct entry versus transient state
C — Rendering/execution N05: SvelteKit HTML/client options; existing SRC-0001 interpretation B04 adds client-island docs; implementation comparisons and performance evidence remain missing
D — Authority/synchronization Transactional evidence, frontend recovery, Matrix experiment Synthetic receiver cannot prove production durability/deduplication; canonical admission remains open
E — Composition/organization B03: feature grouping and public interfaces Independent feature/deployment boundaries and their operational cost
F — Quality Retention/recovery guidance; B05/B06: rendering failures and modal focus No accessibility/performance validation; no-script support is narrower than resilience

The user subsequently requested broader coverage: six drafts and documentary probes were added in the breadth review. Implementation evidence for B/C remains pending. All six streams now have some documentary material; none is thereby complete. VC-01/02 are synthetic reviewed drafts; VC-03 is provisional; VC-04–10 remain planned. No source count is used as a recurrence score or evidence-gate substitute.

Boundary follow-up: React/Radix browser observations add bounded executable evidence to F. Nested dismissal remains timing-sensitive; no screen-reader verification or full quality-stream completion.

Stream E follow-up: feature/deployment contrast adds pinned example code and release workflow definitions; operational independence remains unverified. VC-06 now has a provisional synthetic draft; VC-04/05 and VC-07–10 remain planned. One new developed seed brings the current corpus to seventeen hypotheses.