Àròjinlẹ̀

An articulated mechanism is not necessarily an established desire. Clarify the need, beneficiary, observable success and consequential trade-offs only where they remain unsettled. Reuse complete briefs and accepted constraints; do not manufacture alternatives or re-interview settled choices. A single already-understood bounded choice can remain with its caller.

Use amose when unresolved project-specific meaning—terms, identities, boundaries, relationships, ownership, or invariants—can materially change the decision tree.

Interview the user relentlessly until shared understanding is reached and no consequential branch remains silently assumed. Map it as a decision tree: every decision branches into the decisions that depend on it.

Work the tree in rounds. The frontier is every decision whose prerequisites are already settled. Ask the whole answerable frontier in one round, then wait for the user's answers before starting the next.

Use this question card, rendered as Markdown rather than showing the template fence. Keep question numbers stable across rounds; label choices when that makes answers unambiguous.

❓ **Q1** — **<question title>**: <question and choices, as needed>

💡 <brief context, evidence, trade-off or example, only when it makes the decision clearer>

➡️ <recommended answer and why>