From 7af708159e3dc6410bf7dba14e5f4e2502d1c86a Mon Sep 17 00:00:00 2001 From: robbond Date: Mon, 7 Sep 2026 15:51:18 +0100 Subject: [PATCH] docs(confidence-engine): record Terra journey boundary fixes --- docs/current-handoff.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/current-handoff.md b/docs/current-handoff.md index 2103d34..bb4e149 100644 --- a/docs/current-handoff.md +++ b/docs/current-handoff.md @@ -42,7 +42,9 @@ If YES, the next live experiment is one timed/costed OpenAI UI investigation mea - The focused-deconstruction route now emits complementary safe server diagnostics for start, provider success/failure, focused validation, and end status; the OpenAI schema trace remains provider-owned. No user content or secrets are logged. - Canonical focused relationship items are now strict `{ from, to, type }`: all required non-empty strings, free-text `type`, and no `rationale`; `relationships` remains required and may be `[]`. Schema, prompt field names, and validator align; the stale rationale-bearing test fixture was corrected. - Live Terra focused deconstruction now passes through the real UI, but the following Current Understanding synthesis exposed a separate caller/schema mismatch: its prompt and validator require `{ currentUnderstanding }` while the provider received the default initial-reconstruction schema. -- Synthesis now supplies its own output schema as provider argument three; provider implementation is unchanged. Synthesis and provider deterministic suites pass with zero live calls. Next boundary: one isolated live synthesis request using the already captured situationGraph and findings payload. +- Terra synthesis now supplies its own output schema and unwraps `providerResult.response` before validation; deterministic synthesis coverage is 62/62 PASS and the saved isolated Terra synthesis POST returned HTTP 200. +- Real Terra completed-episode reconsideration can legitimately return no additional meaningful graph change. Completed episodes now tolerate only that exact compatibility outcome; ordinary no-op updates and invalid completed-episode proposals remain rejected, without fake graph mutation or new next-question steering. +- The full apply-proposal owner suite remains known-red in independent pre-existing 60B.43 tests, so the changed Done-for-now boundary was verified through exact isolated owner tests. Zero live calls occurred during closeout. Next boundary: reuse the existing investigation and click Done for now once, observing cases/update and subsequent synthesis. ## Repository checkpoint