[witbrock]

Merge decision: ready — merging makes the requested source-grounded design available for implementation review; it changes no runtime behaviour or represented knowledge.

User outcome

Define when Von should clarify an operational referent, learn relevant identity/role facts and resume the original action without unnecessary questions or duplicate effects. Deliverable for Von task #V#task_agent_1b946e4ed7a32b95e4869f3159256a1c.

Material changes

Add an advisory design note and an index entry. The proposal covers decision tables, precise question/reply binding, scoped source-preserving learning, pending-action continuity, bounded repair, implementation touchpoints and staged acceptance. It builds on the existing adaptive-turn guidance and identifies the pre-dispatch persistence needed for stable cross-turn task keys.

Twenty-two evaluation cases cover ordinary work, ambiguity, authority, recovery and later role reuse. The unavailable originating transcript and reported CodexDGX alias are explicitly distinguished from source observations and proposed fixtures. No policy, workflow, membership or alias is activated.

Evidence

Tier 0: inspected the referenced source and reviewed the complete documentation change. pdm run python -I /tmp/von_clarification_doc_check.py passed: 27 local references, 14 source symbols, 21 distinct headings, table consistency, fences, whitespace and the index entry. git diff --cached --check passed. Runtime tests and model trials are proposed future work, not evidence claimed by this PR.

Ship boundary

• Minimum ship criteria: All eight requested design topics, implementable trigger/question/state/continuation rules, accurate source references and explicit evidence limits.
• Stop-ship conditions: Invented transcript/live-state claims, conflating descriptive roles with permission, or expanding the design-only boundary.
• Non-blocking observations: Live alias state, prompt ownership and runtime efficacy remain unverified and are identified as implementation checks.
• Non-goals: Runtime implementation, live knowledge writes, authority changes, migrations and deployment. The controller receives no deployment request.