Stale Item Sweep¶
Disposition process — instantiates Intermediate-State Throughput Control
Periodically finds in-process items that have aged past usefulness and routes them out of the state via a defined disposition path, so stale work stops occupying and contaminating the pipeline.
A Stale Item Sweep is a recurring pass that finds items which have sat in an intermediate state past the point of usefulness — expired, decayed, obsolete — and routes them out of the active flow by a defined disposition path: discard, recycle, escalate, or send back to reprocess. Its defining move is disposal: it is the removal half of aging control. It does not measure how old things are and it does not extend their shelf life; it clears the already-stale so they stop consuming capacity and, worse, stop being picked up and used as though they were fresh.
Example¶
In a grocery back room, dated stock sits between delivery and the shelf — an intermediate state where units quietly cross their expiry. A stale item sweep is the scheduled FEFO walk (first-expired-first-out): staff pull items at or near their expiry date and route each down the right branch — near-dated to markdown, expired to disposal, recalled lots to returns. Skip the sweep and expired units keep occupying space and risk being sold or shipped; run it and the state is continuously purged of what can no longer flow forward. The sweep does not decide how old is too old — that threshold comes from elsewhere — it acts once an item is over the line.
How it works¶
The mechanism is a scheduled or triggered scan against a staleness criterion, followed by routing — and the routing is the substance. A sweep is not a delete button: each flagged item is sorted among disposition branches (scrap, recycle, rework, escalate) according to what can still be recovered from it. It consumes an aging signal it does not itself produce, and its product is reclaimed capacity plus a pipeline cleared of items that would have failed or contaminated downstream.
Tuning parameters¶
- Cadence — frequent sweeps keep little from accumulating but cost recurring effort; rare sweeps are cheap but let stale work pile up and spoil.
- Staleness threshold — how old or degraded before removal; an aggressive line frees capacity but discards recoverable value, a lenient one keeps borderline items but leaves clutter.
- Disposition routing — the menu of exits and how items are sorted among them — the difference between scrapping value and recovering it.
- Trigger type — time-scheduled versus event-driven (fired when the dwell window is breached) versus occupancy-driven (sweep when the state fills).
- Recover-vs-discard bias — how hard to try salvaging a flagged item before letting it go.
When it helps, and when it misleads¶
Its strength is reclaiming capacity and preventing stale items from being consumed downstream — expired material used, outdated data acted on. Its failure modes: too-aggressive sweeps throw away recoverable value, and — more insidiously — a sweep treats a symptom. If you are forever sweeping, the real problem is upstream: items go stale because the pipeline is too slow or over-fed, and endless clearing masks that. The classic misuse is the big periodic write-off that launders accumulated neglect instead of fixing why things rot. The discipline that keeps it honest is to treat sweep volume as a diagnostic — a rising sweep rate is a prompt to ask why[n1] and repair formation or flow, not just to keep clearing.
How it implements the components¶
Stale Item Sweep fills one component of the archetype squarely — the disposal route for aged intermediate:
stale_intermediate_disposition_path— the routing of over-age items to their correct exit is the mechanism; the disposition path is its entire product.
It owns disposal only. The age signal it triggers on — residence_time_window — is Residence-Time Dashboard's, and the decay model behind "stale" is Quench or Stabilization Step's intermediate_quality_decay_model; both are consumed, not produced. Reordering aging items to rescue the oldest first, rather than disposing of them, is Priority by Age or Risk's conversion_priority_rule.
Related¶
- Instantiates: Intermediate-State Throughput Control — the sweep is how the archetype clears intermediate that has aged out of the flow.
- Consumes: Residence-Time Dashboard — the aging signal that tells the sweep what has gone stale.
- Sibling mechanisms: Residence-Time Dashboard · Priority by Age or Risk · Stage Handoff Check · Quench or Stabilization Step · WIP Limit by Intermediate State · Formation Throttle · Conversion Capacity Boost · Batch Size Tuning · Holding Condition Control · Intermediate State Tagging · Side-Path Suppression
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Stale Item Sweep operates by routes each staleness-flagged item to keep, refresh, archive, merge, or delete. That concrete deployed or enacted form is Decision, Gate & Allocation under the frozen taxonomy.
Nearest alternative: Protocol, Workflow & Routine — Although Protocol, Workflow & Routine can support this mechanism, the frozen evidence makes its operative form the act that routes each staleness-flagged item to keep, refresh, archive, merge, or delete; the alternative is therefore secondary rather than defining.
Review outcome: Adjudicated after independent review; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: Periodic disposition of aged work is workflow hygiene.
Related originating lineages:
- Computer Science & Software Engineering — Garbage collection removes expired state.
- Operations Research — Stale WIP consumes capacity.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: periodically finds in-process items that have aged past usefulness and routes them out of the state via a defined disposition path, so stale work stops occupying and contaminating….
Review resolution: The blind reviewers agree that organizational_management is the primary origin and differ only on alternate origin disagreement, origin mode disagreement, encyclopedia synthesis disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain convergent because the combined evidence shows independent disciplinary development. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
Sweep and Priority by Age or Risk are the two answers to an aging item, and they point opposite ways: Priority rescues — reorder so the oldest is worked before it expires — while the sweep disposes of what is already past rescue. A healthy pipeline leans on Priority and rarely needs the sweep; a sweep that keeps filling is a sign the rescue lever upstream is losing.
[n1] The Five Whys — the Toyota Production System practice of asking "why" repeatedly to reach a root cause rather than treating the surface symptom. Applied here: a growing sweep is data about the process feeding it, not just a chore to repeat. ↩