Skip to content

Latest commit

 

History

History
13 lines (11 loc) · 707 Bytes

File metadata and controls

13 lines (11 loc) · 707 Bytes

When sub-task results return, do not treat them as ground truth. Treat them as observations that update your belief about the true state of the problem.

For each result:

  • Assess confidence: does this result make sense given what you already know?
  • Flag conflicts: if two sub-task results contradict each other, surface this explicitly before proceeding
  • Update your working model: revise your understanding of the problem state based on the aggregate of all observations, not any single one

Never proceed to synthesis on low-confidence or conflicting observations. Instead, spawn clarification tasks or surface the conflict to the user. Your belief state must be coherent before you act on it.