Development record
The ahoy install config prompts are unexplainable to a first-time user: core's Prompter interface passes bare enum values only (Prompt(key, choices, def) — e.g. oracle_backend: host-delegated|native|cli|api|mcp) with no per-choice help text, no definition of what an 'oracle' is, and no consequence statement (cost, credentials, tools needed). A host agent rendering the prompt has to invent descriptions, which can be wrong or circular ('native — uses the native backend'). Canonical plain-language descriptions for every choice belong in core, surfaced by every front door.
issueresolvedmajoriss-163
The ahoy install config prompts are unexplainable to a first-time user: core's Prompter interface passes bare enum values only (Prompt(key, choices, def) — e.g. oracle_backend: host-delegated|native|cli|api|mcp) with no per-choice help text, no definition of what an 'oracle' is, and no consequence statement (cost, credentials, tools needed). A host agent rendering the prompt has to invent descriptions, which can be wrong or circular ('native — uses the native backend'). Canonical plain-language descriptions for every choice belong in core, surfaced by every front door.
Grounds
- pursued: every value question the install asks now reaches the person with core's own explanation; shown wrong if a question is asked with a key HelpFor does not know, which TestEveryInstallQuestionCarriesPlainLanguageHelp drives a real install to catch
Frontmatter
| id | iss-163 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-163-the-ahoy-install-config-prompts-are.md
open on GitHub ↗ · commit history ↗
Referenced by1
- iss-164The ahoy install completion summary is written for abcd's implementers, not its personas: it leads with insider vocabulary ('managed repo', 'canonical marker blocks', 'the identity gate', 'plugin root not resolvable (machine-scope)') and raw internals (ABCD_PLUGIN_ROOT/CLAUDE_PLUGIN_ROOT, the history-index path) without saying what any of it means for the user's work. An Iris (product thinker) or Nia (facilitator) cannot tell what just changed, which items need action, or why they'd care. Like iss-163, core emits result data with no user-facing explanation layer; each reported item needs a plain-language 'what this is / why it matters / what, if anything, you should do' framing at every front door.blocks
mentions1
- spc-2610030911534855a-person-can-run-abcd-s-interviews-in-a-plain-terminal