robbond/confidence-engine
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

experiment: validate bare whether proposition live

Browse Source
This commit is contained in:
robbond
2026-08-14 07:08:29 +01:00
parent 2996c30578
commit 0f7babd937
2 changed files with 156 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/current-handoff.md
+4
View File
@@ -2928,3 +2928,7 @@ Experiment 60B.31 was a live regression of 60B.29 on the post-60B.30 branch to v
---
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.
---
Experiment 60B.34 was a live regression on `feature/bare-whether-proposition-v0.33` to verify that bare `Whether...` description preservation survives the full update route end-to-end. **Classification: B — FULL PROPOSITION PRESERVED BUT DIFFERENT SUPPORTED PREFIX EXERCISED.** One bounded update call produced: new unknown node `n_prospective_customer_signing` with description starting `"Unknown whether..."` (not bare `"Whether..."`). Decision remains unresolved (`n_product_launch_decision` still unknown). Final question: `"What evidence would clarify whether one prospective enterprise customer will sign if we launch this year?"` — full proposition preserved, evidence-framed, zero rationale contamination. The exact 60B.33 targeted fix (bare Whether...) was not exercised live; the model produced `Unknown whether...` instead, a different but functionally equivalent supported prefix path from the same code base. Equivalent outcome to 60B.31's deterministic regression. One live Ollama call at qwen-claude:latest on http://192.168.1.111:11434. No production code changed.