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

docs: record customer signing followup fixture

Browse Source
This commit is contained in:
robbond
2026-08-14 08:02:45 +01:00
parent 89551c5e8c
commit 870d325d08
2 changed files with 92 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/current-handoff.md
+8
View File
@@ -209,6 +209,14 @@ Experiment 54N tested whether an interpretation disagreement can be judged for m
- Generic non-proposition decision unknowns remain on their existing path when no explicit `Whether...` proposition is present.
- **Still unproven live:** the exact 60B.31 live-shaped customer-signing case through the full end-to-end runtime path on this branch.
### 60B.36 customer-signing follow-up fixture
- Added deterministic reusable fixture `tests/fixtures/pre-anchored-product-launch-customer-signing.json` derived from `tests/fixtures/pre-anchored-product-launch-options.json`.
- Preserved `n_product_launch_decision`, `opt_launch_this_year`, and `opt_wait_twelve_months` unchanged; added one unresolved customer unknown `n_enterprise_customer_signing` only.
- Linked the customer unknown to `opt_launch_this_year` using existing `contained_in` structure; set `graph.activeUnknownNodeId` to the customer node and stored the deterministic selected question text for the next-turn follow-up.
- Deterministic harness validation passed via `npx vitest run tests/reproduce-multi-turn-investigation.harness.test.js` (`64/64`).
- This apparatus now enables the next bounded live experiment: answering the existing customer-signing unknown directly and verifying in-place update plus correct decision-state transition without factor duplication or unrelated uncertainty reopening.
### When This Knowledge-Management Phase Is Complete
Provisional criteria for review (all confirmed met by Experiment 38 cold-start test):