fix(dispatcher): ask Main for unresolved completion assessments #522

Merged
karsten merged 1 commit from fix/validator-main-clarification into main 2026-11-16 06:58:58 +00:00
Owner

Changes

  • Ask Main once for semantic uncertainty instead of repeatedly reviewing unchanged evidence.
  • Bound technical read-only assessment retries to six, then ask Main.
  • Preserve unresolved effect intents while asking/answering, including restarts; never turn a parent answer into expanded operator authority.
  • Stop if uncertainty remains after Main answers.

Verification

  • Full Core suite: 2666 passed, 1 skipped, 0 failed (umask 022; inherited umask 077 breaks an unrelated API credential permission fixture).
  • Dispatcher/execution/completion suites after final review: 350/350 passed.
  • Explicit regression checks Main answer reaches reviewer as data, not new authority.
  • Typecheck, build and git diff --check passed.

No deployment or activation performed by this PR.

## Changes - Ask Main once for semantic uncertainty instead of repeatedly reviewing unchanged evidence. - Bound technical read-only assessment retries to six, then ask Main. - Preserve unresolved effect intents while asking/answering, including restarts; never turn a parent answer into expanded operator authority. - Stop if uncertainty remains after Main answers. ## Verification - Full Core suite: 2666 passed, 1 skipped, 0 failed (umask 022; inherited umask 077 breaks an unrelated API credential permission fixture). - Dispatcher/execution/completion suites after final review: 350/350 passed. - Explicit regression checks Main answer reaches reviewer as data, not new authority. - Typecheck, build and git diff --check passed. No deployment or activation performed by this PR.
fix(dispatcher): ask Main for unresolved completion assessments
All checks were successful
decision-interface-ci / full-validation (pull_request) Successful in 3m41s
d5cf377216
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
harness/core!522
No description provided.