The graveyard is alive
Code Afterlife
A living archive for abandoned projects, shipped experiments, stalled builds, and the second lives they earn later.
1 day
to stall without activity
3 days
to enter the graveyard
Forever
for lineage and credit
Why it exists
Most projects do not end cleanly. They drift.
Code Afterlife gives that drift a shape. It turns unfinished work into something browsable, forkable, and historically useful, without pretending every repository needs to be a startup.
Archive
Projects deserve a record.
A side project can stop moving without becoming meaningless. Code Afterlife keeps the repository, stack, story, and timeline readable after momentum fades.
Lifecycle
Health should tell the truth.
Projects begin, move, stall, ship, or die based on activity. The point is not judgment. It is a clear signal for builders and visitors.
Lineage
Old work can become new work.
A dead project can be resurrected as a fork, rewrite, or successor. The original stays credited, and the next generation keeps its ancestry.
Lifecycle
The archive changes when the code does.
Automated checks keep the lifecycle honest. New activity can wake a project; silence moves it toward the graveyard.
01Born
A project enters the archive with a fresh pulse.
02Active
New owner activity or fresh commits prove the project is moving.
03Stalled
One quiet day marks the first visible decay.
04Dead
Three quiet days move it into the graveyard.
05Shipped or resurrected
A finished project can be sealed, and a dead one can begin a new lineage.
Preserve the attempt. Credit the spark. Continue the line.
The archive is for builders who know that even unfinished work can teach, inspire, and become useful again.