experiment: confirm live sufficiency confirmation question
This commit is contained in:
@@ -3549,3 +3549,48 @@ Pre-existing apply-proposal failures (4) confirmed unrelated via git stash/re-ru
|
||||
|
||||
#### Status
|
||||
COMPLETE — production + tests committed, documentation recorded.
|
||||
|
||||
---
|
||||
|
||||
#### 60B.74 — Missing Sufficiency Confirmation Question (Live Verification)
|
||||
|
||||
**Date:** 2026-08-14
|
||||
**Branch:** `feature/sufficiency-confirmation-question-v0.45`
|
||||
**Type:** Live regression observation only
|
||||
|
||||
#### Objective
|
||||
|
||||
Verify whether the post-60B.73 production path preserves the no-confirmation guard while replacing the generic decision-threshold continuation with the focused sufficiency confirmation/discovery question.
|
||||
|
||||
#### Run
|
||||
|
||||
```bash
|
||||
FIXTURE_MODE=updateOnly \
|
||||
FIXTURE_PATH=tests/fixtures/pre-anchored-product-launch-customer-signing.json \
|
||||
ANSWER_2="The enterprise customer has now confirmed in writing that they will not sign if we launch this year, so the £700,000 of expected annual revenue from them will not be received." \
|
||||
CONFIDENCE_ENGINE_BASE_URL=http://127.0.0.1:3000 \
|
||||
node scripts/reproduce-multi-turn-investigation.mjs
|
||||
```
|
||||
|
||||
#### Result: B — GENERIC QUESTION PERSISTS
|
||||
|
||||
Observed behavior is IDENTICAL to 60B.71 on the question level:
|
||||
|
||||
- Customer resolves correctly → resolved (negative meaning preserved)
|
||||
- Decision stays open → unknown (no premature closure)
|
||||
- Active target remains n_product_launch_decision ✓
|
||||
- **Question remains generic:** `"What outcome would demonstrate enough value to justify launching?"`
|
||||
- **Template is `decision_threshold_outcome` — NOT `decision_threshold_sufficiency_confirmation`**
|
||||
|
||||
#### Root Cause: Deterministic Bug in State B Detection
|
||||
|
||||
The condition at line 2010 of `question-formulator.js`:
|
||||
|
||||
```js
|
||||
node.kind !== "unknown"
|
||||
```
|
||||
|
||||
can NEVER be true for any decision node, because all decisions have `kind === "unknown"` (same as child factors). The SituationKind enum has no "decision" kind value. This prevents the sufficiency template from ever firing.
|
||||
|
||||
#### Status
|
||||
BLOCKED — State B detection bug blocks 60B.73 implementation from reaching production. Fix needed in `question-formulator.js` line 2010 to correctly distinguish parent decisions from child factors.
|
||||
|
||||
Reference in New Issue
Block a user