You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Construction**: ResponseMetadata must be built via factory methods so all paths produce consistent metadata. Do not construct `ResponseMetadata` manually for request flows. Use:
Copy file name to clipboardExpand all lines: docs/modules/orchestrator.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -402,6 +402,7 @@ class ResponseMetadata:
402
402
intent_clarity: str# LOW | MEDIUM | HIGH (semantic signals)
403
403
misuse_plausibility: str# LOW | MEDIUM | HIGH
404
404
actionability_risk: str# LOW | MEDIUM | HIGH
405
+
decision_correctness: dict[str, Any] |None# optional DCF payload from diagnostics
405
406
```
406
407
407
408
**Construction**: Always build metadata via factory methods for consistency across paths (fast, deliberative, safe_complete, domain_excluded, system error). Use `ResponseMetadata.from_decision(...)` for flows that have a `Decision` (and optional `DecisionExplanation`); use `ResponseMetadata.for_system_error(...)`, `for_domain_excluded(...)`, or `for_fail_safe(...)` for timeout, domain-excluded, and FAIL_SAFE fallback respectively. See `docs/architecture_spec.md` (ResponseMetadata Construction) for the full list.
0 commit comments