experiment: define structural reasoning-context embedding

2026-08-13 10:26:54 +01:00
parent 48de8b6ce7
commit 7f97268f68
2 changed files with 292 additions and 0 deletions
@@ -2825,3 +2825,7 @@ Experiment 60B.13 performed read-only architectural diagnosis of the 60B.12 kind
 ---

 Experiment 60B.14 performed read-only design analysis on whether a newly-created unresolved factor inside an active decision should inherit the decision's reasoning pattern rather than being classified mainly from its wording. **Classification: D — COMPATIBILITY FALLBACK.** The current architecture separates *active pattern determination* (which DOES use parent-chain traversal via `determineActiveReasoningPattern` and correctly yields "decision" for the 60B.12 node) from *node-intrinsic pattern inference* (which does NOT use that context — it runs standalone text analysis on the node's label/description only). This separation is the root cause: the active pattern correctly walks up to find "decision" in the decision unknown, but the compatibility check re-runs standalone inference on the new node and gets "diagnosis" from its diagnostic-style wording ("will our largest client leave"). The smallest correct fix preserves intrinsic text analysis as primary signal but adds a normalization fallback: when inferred node pattern is incompatible with active pattern AND the node's graph position (parentId, edges) places it structurally within that active context, reinterpret using the active pattern rather than rejecting. This requires no new schema, no new keywords, and preserves genuine pattern transitions (the intrinsic inference still returns diagnosis; only the compatibility decision changes).
+
+---
+
+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.