Resolve target-user question (ADR-0006) and anchor the roadmap#4
Merged
Conversation
The recurring complexity-reduction feedback keeps asking the same unanswered question: optimize for fully non-technical 'On/Off' users, or intermediate users who still need profile control? This commit answers it durably instead of re-litigating it per proposal. - ADR-0006: choose the motivated *intermediate* user, delivered via progressive disclosure (one dominant next action, named intents over raw files, consent-based setup). Explicitly defers the silent-trust 'appliance' product because it conflicts with ADR-0002 (no silent trust install). - ROADMAP: add a Target user section, re-anchor Next items to ADR-0006, and add an explicit Out-of-scope section covering the supercomposition rewrites (PyO3/Cap'n Proto/Tauri/Slint/io_uring/eBPF/embed-in-Xray) that conflict with ADR-0001/0003. - repository-structure.md: index the new ADR. No code paths changed. Full offline suite: 34/34 pass. Note: the other actionable proposal items (verified-session bundle, JA3 oracle wiring) were already delivered in merged PR #3; failure classifier and single-binary distribution already existed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This iteration analyzes the same complexity-reduction + supercomposition ideas again, but the actionable engineering from them was already delivered in merged PR #3 (verified-session bundle, JA3 oracle wiring) and pre-existing code (failure classifier, single-binary distribution). Re-implementing would be churn.
The one thing those proposals consistently leave unresolved is the question they keep asking literally twice:
Every UX/distribution decision depends on this. This PR answers it durably as an ADR so future proposals stop swinging between contradictory directions, and re-anchors the roadmap to that decision. No code paths change.
Changes
docs/adr/0006-target-user-and-progressive-disclosure.md(new) — decides the primary user is the motivated intermediate user, delivered through progressive disclosure:ProjectState.next_action)active_profile, never a file pickerverified-sessionbehind an advanced affordanceROADMAP.md— adds a Target user section, re-anchors Next items to ADR-0006, and adds an explicit Out of scope section for the supercomposition rewrites (PyO3, Cap'n Proto, Tauri/Slint, io_uring/eBPF, embed-in-Xray) that conflict with ADR-0001/0003.docs/repository-structure.md— indexes the new ADR.Idea-by-idea disposition
active_profileper ADR-0006scripts/core/failure_classifier.py)build_gui_exe.py+ release workflow)Testing
Docs-only change; ADR indexing verified against
repository-structure.md.