forgeplan_stale

Detect artifacts whose valid_until date has passed. These are “stale” — the decision or evidence they carry may no longer reflect reality and should be refreshed, renewed, or deprecated. This is the first step in the evidence-decay quality loop.

Category: Quality

When an agent calls it

Periodic sweeps — run weekly to catch expired decisions before they silently degrade R_eff.
Before release — confirm no active artifact ships with expired evidence.
Session start — complements forgeplan_health by showing per-item expiry.
After a long absence — many artifacts may have drifted past valid_until while you were away.

Stale ≠ invalid — the artifact still exists, but its R_eff contribution is penalised (CL0, weight 0.1 in the scoring formula) until it’s renewed.

Input parameters

No input parameters. Call this tool with an empty object {}.

Returns

{
  "stale": [
    {
      "id": "EVID-047",
      "kind": "evidence",
      "valid_until": "2026-03-30",
      "days_expired": 12,
      "linked_to": ["PRD-039", "RFC-006"]
    },
    {
      "id": "ADR-003",
      "kind": "adr",
      "valid_until": "2026-04-01",
      "days_expired": 10
    }
  ],
  "total_stale": 2
}

Example invocation

{}

Typical sequence

forgeplan_stale — list expired artifacts.
For each: decide renew vs reopen vs deprecate.
forgeplan_renew to extend valid_until (if the decision is still sound).
forgeplan_reopen to create a new draft while deprecating the stale one.
forgeplan_decay — see R_eff impact from remaining stale evidence.

CLI equivalent

forgeplan stale