Graveyard Shift
Graveyard Shift finds abandoned npm packages, issues each a cited Death Certificate, and resurrects them on demand with a Proof of Life.
The four roles
- Coroner: deterministic code that makes the Death Certificate.
- Gravedigger: deterministic code that fetches and checks the Original and decides eligibility.
- Medium: the only Kiro agent. It runs on demand on the maintainer's machine and makes no CI decision.
- Undertaker: deterministic CI code. It runs the Proof of Life, attests only an alive Verdict, opens the pull request and re-verifies every entry nightly.
Only the Medium calls an LLM.
The four outcomes
- alive: zero divergences, every Declared Delta demonstrated and no harness error.
- restless: a divergence, or a Declared Delta that was not demonstrated.
- inconclusive: the proof could not be completed, for example because of a harness error.
- not resurrected: the package failed an eligibility rule, so nothing was resurrected, proven or attested. This is not a failed run.
How to read the Crypt
- Only the Verdict alive is attested.
- Entries with the Verdict restless or inconclusive are shown and never hidden.
- An entry labelled "stub run" is not a Medium-produced resurrection.