experiment: isolate semantic-to-mutation contract live

This commit is contained in:
2026-08-11 13:09:51 +01:00
parent 39217b6b65
commit 6aea0bd90c
2 changed files with 142 additions and 1 deletions
+25 -1
View File
@@ -676,4 +676,28 @@ This run did not test the v0.17 contract's core question because the model never
**Ollama calls beyond harness count:** 0
**Documentation updated:** YES
Now let me commit:
---
### Experiment 57J.41 — Semantic-to-Mutation Contract Live Validation: Faithful Meaning Only
**Objective:** When the user introduces one simple, explicit unresolved uncertainty with no conditional/constraint language, does v0.17 translate that faithful meaning into structural graph progress rather than a semantic-only no-op?
**Fixed scenario:** "We are considering relocating the engineering team to reduce operating costs."
**Fixed answer:** "I am unsure whether the projected office savings from the relocation are realistic."
**Live-call count:** start: 1, update: 1, total: 2
**START:** HTTP 200 | stage: unknown | nodes: 6 | edges: 3 | question: "What would clarify current annual operating costs and cost structure of the engineering team in this situation?"
**UPDATE 1:** HTTP 422 | stage: proposal_compatibility | First error: "answerMeaning.userSupportedMeaning is populated, but the proposal contains no graph mutation. answerMeaning alone does not constitute graph progress."
**Rejected Proposal Snapshot:**
- `userSupportedMeaning`: "The user is unsure whether the projected office savings from the relocation are realistic." — **FAITHFUL** (preserves uncertainty, no conditional/constraint language)
- `possibleInference`: null
- All structural fields: empty (zero updatedNodes, zero resolvedUnknownNodeIds, zero addedNodes, zero addedEdges)
**Classification: B — SAME SEMANTIC-ONLY NO-OP.** Meaning is FAITHFUL. All structural mutation fields are empty. The v0.17 MUST rule + validator diagnostic fires as designed, converting the original 57J.36 silent accepted no-op into an explicit rejected proposal with specific error. However, this does NOT prove that faithful meaning CAN produce graph progress — only that it cannot do so without structural mutation under v0.17's new contract.
**Key finding:** v0.17 successfully blocks the original failure (accepted semantic-only no-op) but does not establish a positive path for faithful meaning to produce graph progress. The open question remains: is there any valid pathway where faithful meaning translates to structural mutation, or does the MUST rule universally block it?
Configured Ollama: qwen-claude:latest at http://192.168.1.111:11434. No production code changed. Harness restored. No-retry preserved. Dev server disturbed: NO.