docs: record audience question routing fix
This commit is contained in:
@@ -152,6 +152,18 @@ Experiment 54N tested whether an interpretation disagreement can be judged for m
|
||||
- `npx vitest run tests/graph/apply-proposal.test.js tests/graph/reasoning-context-compatibility.test.js` → PASS (96/96)
|
||||
- **Still unproven live:** the exact 60B.12 client-retention continuation case under live model output.
|
||||
|
||||
### 60B.23 audience-question routing specificity
|
||||
|
||||
- 60B.22 identified that `decision_audience` routing was too broad: any occurrence of `customer|user|buyer|stakeholder|recipient|audience` inside a decision unknown could hijack a proposition-specific question before proposition extraction ran.
|
||||
- `decision_audience` is now gated by explicit audience-identity phrasing only; raw noun occurrence is no longer sufficient.
|
||||
- `extractMeaning()` now prefers explicit `whether ...` propositions from descriptions when the label is a nominal status/risk/likelihood phrase, so proposition-specific decision unknowns preserve their actual unresolved proposition.
|
||||
- Decision-pattern `whether ...` propositions now remain on `decision_evidence_clarification` instead of being pre-empted by `decision_threshold_outcome`.
|
||||
- Legitimate audience-discovery cases remain preserved, and 60B.20-style direct interrogatives remain unchanged.
|
||||
- Focused verification passed:
|
||||
- `npx vitest run tests/graph/question-formulator.test.js` → PASS (25/25)
|
||||
- `npx vitest run tests/graph/question-formulator.test.js tests/graph/question-formulation-v0.24.test.js` → PASS (45/45)
|
||||
- **Still unproven live:** the exact 60B.21 product-launch regression in the full end-to-end path.
|
||||
|
||||
### When This Knowledge-Management Phase Is Complete
|
||||
|
||||
Provisional criteria for review (all confirmed met by Experiment 38 cold-start test):
|
||||
|
||||
Reference in New Issue
Block a user