Bound assistant time and token reservations per request
Repeated retries can exceed the budget for a single support question.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Cost controls · Provider design
Estimated field mix
- Applied AI70%
- Backend30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional internal support team needs answers from product guides. Some guides are outdated or restricted, and fluent unsupported answers would create operational mistakes.
Setup prerequisites
- Author a synthetic document collection with two tenants, conflicting versions, and a deterministic model double; no model account required.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Reserve a configured maximum budget before provider calls.
- Bound retries and total elapsed time.
- Release unused reservation after terminal completion.
Implementation constraints
- Record provider, model, schema, timeout, cost, version, and trace metadata safely.
Verification to include
- Complete a request within the reservation.
- Simulate timeout and ignored cancellation without unbounded retries.
Deliverables
- Request budget controller.
Rollout and recovery
Default to deterministic provider mode; fail closed when reservation cannot be obtained.
Value of the work
For the engineer: Practice retrieval boundaries, citation validation, and deterministic evaluation.
For the team: Create a reviewable assistant prototype with clear refusal, cost, and freshness behavior.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.