noCV
BINCIDENT-104 · Contain safely

Pause selected producers while preserving accepted work

Practice briefTaskAdvanced

Operators stop every producer even though only one import path overloads the queue.

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

Estimated field mix

  • Site reliability50%
  • Platform engineering30%
  • Security20%

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 document service has a rising processing backlog. Operators cannot tell whether arrivals, worker failures, or a slow dependency is responsible.

Setup prerequisites

  • Create a bounded local queue simulation with synthetic jobs and controllable worker/dependency failures.

Preceding work

Complete these dependencies, or supply their agreed outputs before taking this ticket.

Acceptance criteria

  • Scope pause controls to declared producer classes.
  • Reject new work with explicit retry guidance.
  • Preserve previously accepted job records.

Implementation constraints

  • Privileged pause changes require an audit entry.

Verification to include

  • Pause the synthetic import producer.
  • Verify another producer works and unauthorized pause is denied.

Deliverables

  • Scoped admission control.

Rollout and recovery

Start with one producer switch; restore intake gradually after backlog age recovers.

Value of the work

For the engineer: Practice incident timelines, queue diagnosis, and measured recovery.

For the team: Produce a repeatable response that preserves work integrity and exposes customer delay.

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.