Bound tool arguments and returned telemetry volume
A broad query attempts to retrieve days of raw logs.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Schema validation
Estimated field mix
- Applied AI50%
- API design30%
- Site reliability20%
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 on-call team wants an assistant that joins alerts, deployment notes, and runbooks. Incomplete telemetry and hostile log content make unsupported conclusions dangerous.
Setup prerequisites
- Author synthetic alerts, deployment records, and runbooks plus deterministic tool and model doubles.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Require bounded time range and record count.
- Reject unknown tool names and properties.
- Truncate with explicit completeness metadata.
Implementation constraints
- Use aggregate synthetic records instead of secret-bearing logs.
Verification to include
- Retrieve a bounded incident window.
- Reject excessive ranges and unsupported tool arguments.
Deliverables
- Tool request validator.
Rollout and recovery
Start with conservative limits; report incomplete context rather than expanding silently.
Value of the work
For the engineer: Practice constrained tool use, operational uncertainty, and traceable AI outputs.
For the team: Produce concise incident drafts that preserve source traceability and operator control.
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.