From demo to production
Reserve model decisions for the part that depends on the situation. Keep boundaries, verification and an operable fallback around that part.
Links containing ?t= open the video at a specific second.
The ideas to retain
Budgets before promises
An agent should have explicit limits:
Retries, idempotency, and terminal failures
Not every failure should be handled the same way. A timeout may be retryable; an invalid argument is not. A 429 calls for backoff and respect for quota limits; a business-rule rejection…
Asynchronous work and honest completion
The local Reactive/Proactive Agent runtime used by 5sigmas models a common case: the agent accepts work, the tool continues outside the visible turn, and the result arrives when the batch…
Jump directly to a section
Read the reviewed transcript
Transcript of the visual text. This video has no narration.
00:00 — The budget defines when to stop.
Policy allows five calls for this illustrative task.
After the fifth call, a sixth proposal must not execute.
Return partial status or escalate the case; do not invent success.
Illustrative example, not production measurements.
00:22 — Classify the failure before retrying.
A 429 calls for waiting; repeating an invalid argument does not fix it.
A timeout can hide an operation that actually executed.
Choose waiting, correction or state inspection according to the contract.
Illustrative example, not production measurements.
00:46 — A retry must not duplicate the intent.
Request K7 creates an operation, but its response is lost.
The retry keeps K7, and the API returns the existing operation.
That guarantee depends on the system’s idempotency contract, not the prompt.
Illustrative example, not production measurements.
01:10 — Failure needs a state and an owner.
Once retries are exhausted, the operation must leave “running”.
Mark terminal failure and route the case to an owned queue or review.
Do not leave a task indefinitely pending with no owner.
Illustrative example, not production measurements.
01:32 — A complete result. One completion message.
Two tools work while conversation continues on its own turn.
The first result does not close a batch that still has pending work.
Once the batch finishes, deliver one completion through the chosen route.
Illustrative example, not production measurements.
01:56 — Use an agent where the sequence needs one.
When the path is already known, a function or workflow can solve it.
Reserve model decisions for the part that depends on the situation.
Keep boundaries, verification and an operable fallback around that part.
Illustrative example, not production measurements.
