For business
What it is
The approved result goes where it is needed: a PDF report, a live view in the app, or an API response.
Why it matters
People get results in the format they already use, as soon as they are ready.
Risk without it
Good output in the wrong format, or arriving too late, simply does not get used.
For engineers
How it works
Documents are rendered from the structured output with templates; progress streams to the UI over server-sent events; other systems receive an API response or a signed webhook with retries.
Typical stack
- server-sent events
- PDF / DOCX templates
- REST API
- signed webhooks
Pitfalls & trade-offs
- Webhooks need signatures, retries and idempotent receivers.
- Stream progress on long runs: silence feels broken.
- Version the API contract.
In this example
In
→ report v2
Out
report.pdf stream → adviser UI POST /webhook 200
Fictional sample · not a client system