read-only-intent-delivery

Read-only intent routing is handled by enforcing a strict non-mutation policy and wiring deterministic paths for querying data without altering external systems. This guarantees repeatable outcomes for conversational runtimes processing schedule or report queries.

A read-only intent is a query or reporting capability, like schedule.day_view or report.reminders, that retrieves data without mutating external systems. You need deterministic routing to ensure these queries return repeatable, traceable results across runtime workflows.

Traceable outcomes are ensured by requiring a trace_ref in both success and failure replies. The runtime surfaces inconsistencies for partial data and provides a copy.askFor fallback to safely request any missing fields during the query process.

Yes, deterministic routing applies specifically to reporting and query capabilities like schedule.day_view and report.reminders. It enforces a strict non-mutation policy, ensuring external systems remain completely unaltered while delivering traceable query results.

When missing fields are encountered during read-only intent delivery, the runtime provides a copy.askFor mechanism to request the missing information. It also surfaces inconsistencies and includes a trace_ref in the failure reply to maintain full traceability.