Staleness Discipline
Define what "stale" means in the Mall and how to remove entries without breaking heirs that depend on them.
When to Use
- Monthly mall audit (fired by
/audit-mall) - A heir reports a broken or outdated entry
- A
/prune-storeinvocation - Coherence-check finds an Edition reference to a Mall entry that should be pruned
What "Stale" Means
An entry is stale if any of these apply:
| Signal | Threshold |
|---|---|
| Link unreachable | HTTP 4xx/5xx for 2+ consecutive checks across 7 days |
| Upstream archived | Repo settings show "Archived" or equivalent |
| No upstream activity | No commits, releases, or issue activity in 18+ months |
| License changed unfavorably | Switched to a more restrictive or unclear license |
| Description drift | Mall description no longer matches upstream README's description |
| Replaced by superior alternative | Another Mall entry covers the same ground better |
| Heir reports persistent breakage | ≥ 2 heirs report the entry doesn't work as documented |
Classification
| Stale signal | Action |
|---|---|
| Link unreachable, but upstream still active | Refresh (update URL) — not prune |
| Upstream archived but stable | Keep, mark archived: stable in entry |
| No activity AND archived | Prune |
| License change | Defer to ACT pass — license escalation may need AlexMaster input |
| Description drift only | Refresh |
| Replaced by superior alternative | Prune the worse entry, update the better one's description |
| Persistent heir breakage | Investigate before pruning — may be a Mall-side fix |
Pruning Procedure
Pruning is always reversible by re-add. Never delete history.
- Run
mall-curation's decision tree to confirm prune is correct - Check coherence: does any Edition skill or instruction reference the entry being pruned?
- If yes, fix the Edition reference first (open Edition PR), then prune
- If no, proceed
- Comment out the entry in STORES.md and CATALOG.md (do not delete)
- Add a
pruned: YYYY-MM-DD reason: <reason>line above the commented entry - Update README counts
- Open Mall PR titled
prune: <entry name> (<reason>) - After merge, document in
decisions/if this prune sets a class precedent - Record in
decisions/curation-log.mdwithMorSclassification
Pruning Anti-Patterns
| Anti-pattern | Correction |
|---|---|
| Hard-deleting the entry | Comment out instead — preserves history and reversibility |
| Skipping the coherence check | Pruning a referenced entry breaks the Edition for fleet heirs |
| Pruning without updating README counts | The Mall claims N stores; the count must match reality |
| Pruning multiple entries in one PR without separate rationales | Each prune is a decision; bundle wastes the audit trail |
Re-Add Procedure
If a pruned store revives (un-archived, link restored, license clarified):
- Run full
store-evaluation— past acceptance does not transfer - If it passes, uncomment in STORES.md and CATALOG.md
- Update the prune line to
re-added: YYYY-MM-DD - Increment counts
Output Template (prune verdict)
# Prune Verdict — <store name>
**Entry**: <STORES.md line or CATALOG.md ID>
**Date**: YYYY-MM-DD
**Reason**: <which staleness signal fired>
## Coherence Check
- Edition references: <count>
- References fixed first: yes/no
- Files affected: <list>
## Counts After Prune
- STORES.md: <before> → <after>
- CATALOG.md: <before> → <after>
- README badge: <before> → <after>
## ADR?
Yes | No — <if yes, link to decisions/ADR-NNN>
## ACT Pass Trail
<markers>
Related
mall-curationstore-evaluationmall-maintenance-rules/prune-storeprompt