Eclipse Epitaph runs on your own machine — the client starts it, so there is no endpoint to ping.
Signed death record triggers atomic cascade expiry of fixture instruments; local only.
The linked repository no longer exists on GitHub — it was deleted or made private.
This one has been quiet for a while
Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.
Alternatives to Eclipse Epitaph
same job, measured the same wayFailure-attribution recompute over hash-chained fixture records (local only): verdict + proof path.
Pre-agreed revenue splits sealed at spawn, settled on completion records. LOCAL/fixture only.
Guardian veto verdicts + receipts over fixture actions; local/simulator only.
Eval-expiry clock over fixture Benchkit scorecards + fixture drift evidence; local stdio MCP only.
Messy catalog to agent-grade feed with per-attribute provenance. LOCAL/fixture only.
Decision-evidence sealing + audit recompute over fixture decisions; local only.
Pay-per-crawl licensing receipts: sealed identity+terms+fingerprint binding. LOCAL/fixture only.
Capture witness: content, headers + TLS cert sealed as one signed bundle; fixture captures only.
Eclipse Epitaph — questions
Answers built from our own checks of this server.