experiment: diagnose runtime question formulation path

2026-08-14 06:48:24 +01:00
parent 9b5942799f
commit 29d565372b
2 changed files with 152 additions and 0 deletions
@@ -2915,3 +2915,7 @@ Experiment 60B.27 ran the exact product-launch live regression on the post-60B.2
 ---

 Experiment 60B.31 was a live regression of 60B.29 on the post-60B.30 branch to verify that `Uncertainty over whether...` now preserves the full proposition end-to-end live. **Classification: B — FULL PROPOSITION PRESERVED BUT DIFFERENT PREFIX EXERCISED.** The model produced `n_enterprise_customer_signing` (kind=unknown, status=unknown) with a depends_on edge. Decision remains unresolved. However, the node description started with `Whether...` not `Uncertainty over whether...`, meaning 60B.30's targeted normalization was NOT exercised live. The final question ("What outcome would demonstrate enough value to justify launching?") is generic justification interrogative — same shape as 60B.29, full proposition lost from the question text but preserved in the source node description (source graph meaning intact). No rationale contamination in the final question. One live Ollama call at qwen-claude:latest on http://192.168.1.111:11434. No production code changed. The `Uncertainty over whether...` normalization is deterministic-proven (39/39 tests) but never exercised against the live model producing this exact prefix — follow-up needed to force that prefix live.
+
+---
+
+Experiment 60B.32 was a code-path diagnosis of why the full runtime produces generic decision-justification questions for nodes whose descriptions start with bare "Whether..." — despite deterministic tests producing correct evidence-framed propositions. **Classification: D — ACTIVE CONTEXT DRIFT.** Three compounding factors in question-formulator.js cause the divergence: (1) extractMeaning's proposition detection requires label keywords (likelihood/status/probability/chance/risk/uncertainty) that "Enterprise customer signing decision" lacks, so the meaning strips "Whether" and isWhetherPropositionMeaning returns false; (2) hasDecisionValueLanguage becomes true because the description contains "value" within a parent-driven decision context; (3) extractActionPhrase scans ALL related nodes including the parent product-launch node, which supplies an action phrase ("launch") embedded in the generic template. The focused test avoids all three because its graph has no parent nodes and its label "Supplier renewal likelihood" contains the keyword "likelihood". Minimum corrective boundary: make extractMeaning recognize bare "Whether..." descriptions regardless of label keywords, so isWhetherPropositionMeaning returns true and blocks decision_threshold override. No production code changed. 0 Ollama calls. Pure code inspection.