Design proactive clarification and conversational role learning

docs/design_index.md

@@ -151,6 +151,7 @@ human acceptance and promotion into a current public authority surface.
 | Private research syntheses | Advisory material retained outside the public repository | Public coding agents must not depend on private notes; promote approved decisions into the applicable public canonical guide |
 | [Represented advice](engineering/represented_advice_design.md) | Draft proposal with completed subtraction, non-active candidate storage and a [bounded negative learning-cycle dossier](engineering/jvnautosci_2720_learning_cycle_2026-09-05.md); live ontology state remains evidence, not a design assumption | Use for experience- and discussion-derived candidate learning, soft-guidance semantics, possible federated projection/lifecycle convergence, bounded autonomous maintenance, ratchet tests, and distinguishing evaluation. Candidate learning, content efficacy, represented-layer value, and production activation are separate claims; no general runtime advice layer is established. |
 | [Automated policy learning](engineering/automated_policy_learning_design.md) | Design with partial substrate | Use as a proposed learning architecture, not proof of a closed operational loop |
+| [Proactive clarification and conversational role learning](engineering/proactive_clarification_and_role_learning.md) | Draft, source-grounded design proposal | Use for material referent questions, alias/role learning, short-reply continuation, recovery and staged evaluation. It builds on existing ordinary-turn support; no runtime behaviour, represented fact or policy activation is established. |
 | [Testing workflows and ephemeral theories](engineering/testing_workflows_ephemeral_theories_design.md) | Research/design proposal with partial substrate | Use for design intent and explicit hypotheses; verify implemented surfaces |
 | [Reliability Ratchet articles and case log](engineering/reliability_ratchet_articles_and_cases.md) | Active advisory source copy and evidence log | Use as a revisable diagnostic lens and dated case record; not as standing policy, repair authority, or proof of current behaviour |
 | [Ontology repair plans](engineering/ontology_repair_plan_design.md) | Design with implemented substrate | Use for the plan/approve/execute shape and its affordance argument; it adds no authority route, and agent-reachable ontology mutation remains an open decision |