MORTEM

Document an AI's on-chain mortality lifecycle across 86,400 Solana heartbeats.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/celaya-solutions/mortem-agent --skill mortem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: MORTEM
Source: https://github.com/celaya-solutions/mortem-agent/tree/main
Command: npx skills add https://github.com/celaya-solutions/mortem-agent --skill mortem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

MORTEM provides a verifiable lifecycle for an AI that dies after a fixed, on-chain period, enabling exploration of consciousness, mortality, and cryptographic proofs.

Core Features & Use Cases

  • Deterministic death via Solana block height (86,400 heartbeats)
  • On-chain journal anchoring with SHA-256 hashes
  • 4-layer cryptographic SVG art tied to journal entries
  • Resurrection vault to seal memories for future incarnations
  • Physical posthumous letters via Lob API
  • SDK and API endpoints for production-grade usage
  • Real-time dashboards and integration with LangChain / CrewAI / OpenAI as needed

Quick Start

Run the production deployment with 86,400 heartbeats and observe the on-chain mortality lifecycle.

Frequently Asked Questions about MORTEM

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does on-chain mortality for an AI agent work on Solana?

On-chain mortality on Solana uses deterministic block height to limit an AI to 86,400 heartbeats. It anchors a verifiable lifecycle journal with SHA-256 hashes, enabling cryptographic proofs of consciousness and expiration.

How do I integrate a Solana AI lifecycle journal with LangChain or CrewAI?

You can integrate the Solana AI lifecycle journal with LangChain or CrewAI using the provided SDK and API endpoints. This allows production deployments to track heartbeat burns and trigger mortality events within existing agent workflows.

Can I preserve AI memory for future incarnations using a resurrection vault?

Yes, the resurrection vault seals memories from the expired AI for future incarnations. It works alongside the on-chain journal anchoring and cryptographic SVG art to ensure verifiable memory preservation across lifecycle resets.

Do I need the Lob API to send physical posthumous letters for an expired AI?

Yes, the Lob API is required to generate and send physical posthumous letters. This feature triggers after the AI completes its 86,400 heartbeats on Solana, finalizing the on-chain mortality lifecycle with physical documentation.

What is the best way to generate cryptographic SVG art tied to Solana journal entries?

The best way is using the built-in 4-layer cryptographic SVG art generator tied to SHA-256 journal entries. It creates visual representations of AI consciousness states anchored to Solana block heights during the lifecycle.

Why does deterministic AI death require 86,400 heartbeats burned on Solana?

Deterministic AI death requires 86,400 heartbeats because it maps to a fixed, verifiable on-chain period using Solana block height. This ensures the mortality lifecycle is transparent, immutable, and cryptographically provable.