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

experiment: validate intentional structural no-op live

Browse Source
This commit is contained in:
robbond
2026-08-12 08:49:40 +01:00
parent 67699ecd03
commit f78061c1db
2 changed files with 107 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/current-handoff.md
+12
View File
@@ -1417,3 +1417,15 @@ Full record in `docs/experiment-57j66.md`.
---
New branch: `feature/semantic-action-contract-v0.23`
---
### Experiment 57J.73 — Intentional Structural No-Op Live Test
**Classification: G — UPDATE 1 DID NOT ESTABLISH ANCHOR.** One start + one update via the canonical harness. Fixed scenario: "We are considering relocating the engineering team to reduce operating costs." Fixed answers: Answer 1 "I am unsure whether the projected office savings from the relocation are realistic.", Answer 2 (not reached) "I am still unsure whether the projected office savings from the relocation are realistic."
**Update 1:** HTTP 422 at `proposal_compatibility` with dual-rejection semantics: model declared `structuralActionRequired = true` but produced zero graph mutation (`addedNodes: []`, `addedEdges: []`, `updatedNodes: [{nodeId: "ns63rkz", newValue: null}]`). Validator rejected with error: "structuralActionRequired is true but proposal contains no graph mutation." This is the same contract violation pattern from 57J.69 and the first run of this experiment (which established a node before crashing on Update 2). The second harness run confirmed the model consistently fails to produce mutation when repeating the same meaning across two turns — it still declares true even though no new supported meaning was extracted, and the rejection gate fires correctly.
**Update 2:** NOT REACHED (Update 1 blocked).
**What remains unproven:** Whether Update 2 would produce `structuralActionRequired = false` if an anchor existed. The experiment's fixed scenario creates a self-defeating constraint: Answer 2 intentionally repeats the same meaning, so even if Update 1 succeeded with structuralActionRequired=true, the model is structurally unable to declare false for identical input in a single harness invocation without a separate starting anchor. Configured Ollama: qwen-claude:latest at http://192.168.1.111:11434. No production code changed.