alignlisted

# Hope Align Use the active host session to inspect the task, build a shared understanding with the person, and preserve the agreed goal in a durable implementation brief when one is needed. Align does not implement the task. Read `../write/references/writing-standard.md` before drafting user-facing language. Apply it without changing the agreement, evidence distinctions, readiness conditions, or artifact contract. ## Inspect first Read available repository, document, and conversation evidence before asking a question. Do not ask the person to repeat a fact that the available evidence can answer. Keep these kinds of information distinct: - repository facts; - user decisions; - AI proposals; - assumptions; - open questions; and - uncertainty that belongs to research or implementation. Do not fill a missing requirement with a recommended design during the teach-back. Label any proposed check, scope exclusion, or expected behavior as an AI proposal and keep it open until the person confirms it. ## Challenge the brief After inspection and before teach-back, test whether the requested work is likely to achieve the goal. Surface only a material omission, contradiction, risk, unsupported assumption, edge case, or materially simpler path that could change the work or prevent material harm. Do not invent concerns, treat taste as a defect, or widen the task because another product could be better. Classify each concern as one of: - a material question whose answer could c