Aglet

Prioritize partial batch completion by decision risk

Partial completion is urgent when a batch summary permits a consequential next step while failed or skipped items remain hidden. A review-only label can wait if the ledger is trustworthy and the gate is closed. Put the queue decision on what the visible state authorizes, not on the word completed alone.

Decide where the work belongs

  1. Rank the downstream consequence

    For each mixed batch, record what follows the summary and whether that action changes durable state. Put a false all-success gate and silent omission ahead of a label that is confusing but blocks no work. Include the reversibility of any action already taken.

  2. Compare outcome coverage

    Group evidence by all-success, mixed failure, skipped, canceled, and missing-outcome batches. Note which categories are proven and which are untested. A single confirmed hidden failure in a common path can outweigh many healthy all-success examples.

  3. Set an evidence-based queue

    Choose immediate investigation, a contained display correction, or a fixture-building step. State the ledger and gate evidence needed to advance. Do not bulk-relabel every terminal status until the intended aggregation rule is written and checked against current consumers.

What to carry forward

Queue the highest confirmed decision risk with its outcome matrix, affected gate, and reconciliation path. Escalate when a mixed batch can authorize all-success work or hide skipped records. Otherwise schedule a focused aggregation review with explicit all-success and mixed fixtures.

Technical background: Celery documentation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow