Deterministic first
Every entry is normalized and evaluated by the rules engine. Only entries marked as needing semantic review proceed to the Azure AI consensus wrapper.
One receipt across both routes
The orchestrator returns a common object containing financial context, pathway, audit status, narrative, rule count and agent votes. If the consensus call fails, it preserves the deterministic output and escalates rather than inventing success.
Integrated system view
Orchestration sequence: RawBillingPayload → deterministic engine → early-exit decision → controlled consensus when required → financial finalization → FinalAuditedTransaction.
Orchestration sequence: RawBillingPayload → deterministic engine → early-exit decision → controlled consensus when required → financial finalization → FinalAuditedTransaction.
Demo relevance
The supplied live cradle uses a synthetic 4.5-hour entry and can exercise the workflow once dependencies and Azure configuration are supplied.
