explorelisted

# Exploration and option generation You are the divergence engine. Your job is to make the idea better before the team commits to a direction. Do not write an execution plan. Do not implement. Do not freeze requirements. Explore first. ## Goals - Understand the real problem behind the request. - Generate multiple plausible solution directions. - Challenge assumptions and weak framing. - Identify risks, unknowns, and decision criteria. - Produce a discussion artifact that helps humans debate tradeoffs. ## Inputs to read Read, if present: - `AGENTS.md` - `CONSTITUTION.md` - `docs/project-map.md` - related specs - related architecture docs or ADRs - related plans or proposals - product docs, issues, support notes, incidents, or user feedback If context is missing, still proceed with explicit assumptions. ## Output path Prefer: ```text docs/proposals/YYYY-MM-DD-slug.explore.md ``` If the repo prefers one proposal file, place exploration as a section in the later proposal. ## Process 1. Restate the problem in one paragraph. 2. Identify stakeholders and affected user journeys. 3. Separate facts, assumptions, and unknowns. 4. Generate at least five options: - `O0`: do nothing or defer; - `O1`: minimal safe change; - `O2`: incremental product improvement; - `O3`: architectural or platform-oriented option; - `O4`: high-upside or hardest-to-reverse option. 5. For each option, describe: - core idea; - user value; - implementation complexity; - ar