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

experiment: validate bounded structural context admission live

Browse Source
This commit is contained in:
robbond
2026-08-13 12:56:20 +01:00
parent a7ca8d712d
commit 43b9e5a35c
2 changed files with 208 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/current-handoff.md
+6
View File
@@ -2841,3 +2841,9 @@ Experiment 60B.14 performed read-only design analysis on whether a newly-created
---
Experiment 60B.15 addressed the unresolved boundary question from 60B.14: **what exact structural relationship is strong enough to count as "embedded in the active context" without becoming so permissive that genuine pattern transitions are hidden?** Analysis of all available signals confirmed: (1) SituationRelationship enum defines 11 edge types with distinct semantic force, (2) node-level parentId/childIds provide unambiguous hierarchy, (3) parent-chain-only is too narrow (misses edge-connected nodes), (4) any-graph-path is too permissive, (5) Candidate E — PARENT OR DECISION-OPTION PATH was selected as the winning predicate. The rule: a new unknown is embedded in active context Y if EITHER its parentId/ancestor chain reaches a node with pattern Y, OR it attaches via may_cause/causes/affects edge to an option contained_in a decision-unknown. This uses two independent routes with clear boundaries — neither alone sufficient, together covering all common embedding patterns. The genuine-transition test at apply-proposal.test.js:2486 (comparison child under decision parent) is preserved because comparison IS already in the ALLOWED list for decision context — structural embedding only affects the normalization step when intrinsic inference produces an incompatible result, which indicates likely wording drift. No new schema required. Implementation readiness: A — ready for bounded implementation.
---
Experiment 60B.20 was the live verification of bounded structural context admission from 60B.19 (commit d871a8c). **Classification: A — FULL LIVE CHAIN CONFIRMED.** The exact client-retention case that failed at result_validation in 60B.12 now passes through all stages end-to-end. The model produced `n_client_retention_risk` (kind=unknown, status=unknown) with a `may_cause` edge from opt_relocate. Proposal applied successfully. Decision remains unresolved. Final selectedQuestion targets n_client_retention_risk specifically with text "will our largest client leave if we relocate?". Client risk clearly attributed to Relocate. No fabrication, no over-closure, no unrelated uncertainty invented.
---