experiment: test structured evidence to consequence reasoning

This commit is contained in:
2026-08-07 19:02:37 +01:00
parent cd9328ef8e
commit dd3b8e505d
3 changed files with 526 additions and 4 deletions
+3 -3
View File
@@ -141,8 +141,8 @@ Answer before continuing:
---
*Created by Experiment 34. Updated by Experiments 3853, 54A54P. Branch: `feature/user-workspace-ux-v0.7`.*
*Created by Experiment 34. Updated by Experiments 3853, 54A54Q. Branch: `feature/user-workspace-ux-v0.7`.*
### Return-to-Work Note (Experiment 54P)
### Return-to-Work Note (Experiment 54Q)
Experiment 54N failed on a higher-level consequence judgement for competing causes sharing one diagnostic goal. Experiment 54O showed the underlying evidence distinction (staff vs supplier) was available when asked directly. Experiment 54P tested whether making those evidence needs explicit restores the consequence judgement; results across three cases all passed. No winner or next question was generated in either experiment. Same host/model retained; no production behaviour changed. Whether this explains the 54N failure or only narrows it remains open. Branch: `feature/user-workspace-ux-v0.7`. First test/file to inspect when resuming: `tests/reconstruction/semantic-evidence-consequence.test.js`.
Experiment 54N failed when moving directly from hypotheses to consequence on the staff-capacity versus supplier-lead-time case. Experiment 54O showed evidence discrimination works when asked directly. Experiment 54P showed explicit supplied evidence restores consequence judgement. Experiment 54Q tested whether one structured semantic call can first expose evidence needs and then preserve the consequence — it succeeded across all three cases including the original 54N failure. No winner or question generated; same host/model; no production behaviour changed. Whether this explains the 54N failure or only narrows it remains open. Branch: `feature/user-workspace-ux-v0.7`. First test/file to inspect when resuming: `tests/reconstruction/semantic-structured-evidence-consequence.test.js`.