Repository navigation
memory: use choice-only Luna verdicts for bounded Wiki decisions - #3287
Merged
Hillary Mutisya (hillary-mutisya) merged 1 commit intoNov 15, 2026
Merged
Conversation
Enable strict bounded Wiki verdicts without probabilities or confidence. Preserve evidence preparation, exact witness guards and prose generation, and reject verdict/evidence disagreement explicitly. Add regression coverage and a bounded three-arm replay harness. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
GPT_6_LUNAwith strict choice-only answers:{ answers: { questionId: { type: "choice", choice: "<offered value>" } } }. Reject probabilities, confidence, extra fields, missing answers and unoffered choices.Motivation
These boundaries need categorical decisions, not generated probability distributions or confidence claims. Restricting the response contract makes the accepted output explicit while retaining the richer evidence required by the existing host guards.
A preceding component diagnostic used six complete repository documents, 36 bounded packets and three repeats across native, full-shaped Luna and choice-only Luna arms. All 324 scored outputs were valid, but the Luna schemas disagreed on 13/126 question pairs and native/full on 32/126. There were no independent correctness labels or repeat-stable cross-schema differences. This motivates an explicit contract, not an accuracy, equivalence or performance claim. The production integration in this PR is offline-tested; that diagnostic was not an end-to-end test of these new gates.
Behavior and configuration
GPT_6_LUNAendpoint. Restricted calls use temperature one and explicitly opt into the SDK's strict-schema path. No new credentials, configuration files or dependencies are added.Reviewer guide
The replay runner has its own fixed 327-call schedule and immutable evidence/protocol checks. The current fresh-data driver also counts the newly added six completeness calls: expected total 375 within one 420-call/90-minute ceiling. It does not silently reconstruct a missing historical dataset or qualify host consequences.
Validation
Validated on Windows, Node 26 and standalone pnpm, at
e5213de7d920bb08008f6d2e90343d6914f1ec3b:pnpm run buildpnpm run test:memory-qualitypnpm run prettier:changedorigin/maingit diff --checkFrom
ts, the affected suites are reproducible with:The first local circular scan raced a test-owned temporary Git lock directory being deleted. Re-running after tests completed passed without changing the scanner or its baseline. No live inference was run to validate the production integration.
Risks and rollback
This adds model calls and can reject assessments previously accepted by preparation alone. Cost, rejection rate and end-to-end latency/quality have not been qualified; no speedup is claimed. Provider output admission allowance is not a hard wire generation cap. Source-backed correctness adjudication and broader live host qualification remain follow-ups.
Rollback is a revert of this policy change. The PR does not change global model defaults, activate publication authority, weaken evidence guards, or enable automatic merging.