prompt: add existing-first uncertainty fallback

Add one explicit action-order rule in Additional Guidance for when rule #6 applies to explicitly unresolved uncertainty: 1. First check whether an existing unresolved node already represents the same uncertainty. 2. If so, update/refine that existing structure rather than creating a duplicate. 3. If no such node exists, add a new unknown that directly represents the unresolved uncertainty. 4. Do not use an edge alone to represent a previously unrepresented uncertainty. 14 focused prompt tests verify: existing-first ordering, reuse path, fallback-to-add, related-node-insufficient, edge-only-prohibited, possibleInference separation, resolution path preserved, duplicate contract preserved, scope uncertainty-only, fidelity/traceability preserved, noop validator untouched, no semantic classifier added.
2026-08-11 14:12:42 +01:00
parent 96b855b8e7
commit a5dd9d3f1a
2 changed files with 153 additions and 0 deletions
@@ -123,6 +123,7 @@ The JSON object must contain exactly these top-level fields:

 ## Additional Guidance
 - If the answer only clarifies an existing unknown, prefer updatedNodes and resolvedUnknownNodeIds over creating duplicate nodes.
+- When rule #6 applies to explicitly unresolved uncertainty: first check whether an existing unresolved node already represents the same uncertainty; if so, update/refine that existing structure rather than adding a duplicate; if no such node exists, add a new unknown that directly represents the unresolved uncertainty; do not use an edge alone to represent a previously unrepresented uncertainty.
 - When an answer resolves an existing unknown, include that existing node ID in resolvedUnknownNodeIds and update that node rather than creating only a parallel observation.
 - If the answer creates a more specific decision situation, add the smallest set of new nodes and edges needed to represent that situation and only its most consequential unknowns.
 - If you add a new unknown, do not leave it floating: connect it with an added edge to the relevant decision/context node created or updated from the answer.