noCV
BTRIAGE-102 · Scope incident inputs

Limit incident retrieval to the caller's service grants

Practice briefTaskAdvanced

A related-service lookup exposes another team's restricted incident notes.

Focused work estimate
3h + prerequisites
Priority in the scenario
High
Engineering practice
Authorization · Tool design

Estimated field mix

  • Security60%
  • Applied AI40%

Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.

Your next step

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

  • Scope every tool read by caller grants.
  • Recheck access for referenced records.
  • Return non-enumerating denial responses.

Implementation constraints

  • Tool definitions cannot widen caller permissions.

Verification to include

  • Read an authorized service timeline.
  • Deny a cross-service record guessed by ID.

Deliverables

  • Authorized tool boundary.

Rollout and recovery

Disable assistance when grant resolution fails.

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.