The ghost is not you. But it echoes you.

What survives beyond scattered archives? Beyond exported conversations and curated bookmarks? The stuff we never think to preserve: the photos that show how you see the world. The correspondence that maps who matters to you.

The Long Echo toolkit has grown. PTK for photos. MTK for mail. But these are sources, not destinations. The destination is something stranger: longshade, a persona built from your data that can respond to questions you never answered.

I’m going to invert the usual pattern here. Instead of tools first, philosophy later, I want to start with the philosophical destination and work backward to the data that feeds it.

longshade: The Ghost That Speaks

The Central Question

What if your archive could respond?

Not a chatbot trained on your data. Not a digital resurrection. Something more careful: a voice that carries your patterns, your interests, your way of seeing the world.

That’s longshade. Right now it’s spec-only (no implementation yet). It defines what it would mean to synthesize a conversable persona from personal archives.

The Ghost Metaphor

“The ghost is not you. But it echoes you.”

This framing matters. longshade isn’t about immortality or resurrection. It’s about preservation with a kind of agency. The echo can answer questions you never answered, using patterns you established. It speaks in your voice without claiming to be you.

The distinction is important:

• Resurrection claims to recreate the person
• Simulation claims to predict the person
• Echo acknowledges it carries patterns, not identity

An echo is honest about what it is. It responds because you left enough traces to inform a response, not because it is you.

Voice vs. Personality

longshade extracts voice, not personality.

Your actual phrases. Your vocabulary. Your reasoning patterns. Your recurring metaphors. The way you explain things, not the things you might explain.

I noticed something working with conversation archives: user messages are the strongest signal. AI responses contain the AI’s voice. Your messages contain your voice. How you ask questions, how you frame problems, how you push back. That’s where the signal lives.

The ghost speaks like you because it learned from what you actually said, not from responses you prompted.

The Long Echo toolkit now covers conversations, bookmarks, and ebooks. But two of the most emotionally significant categories of personal data remain: photos and mail.

Both share a troubling pattern: scattered across devices and cloud services, organized by date rather than meaning, vulnerable to platform disappearance. They deserve better.

The Expanding Ecosystem

The orchestration layer, longecho, ties these together into a unified personal archive.

PTK: Photo Toolkit

Photos are the most emotionally valuable digital artifacts most people have. They’re also among the worst-managed.

The Problem

Your photo library is probably:

• Scattered: Phone, old phones, cloud services, camera imports, messaging app saves
• Organized by date: Not by who’s in them, where they were taken, or what they mean
• Cloud-dependent: Google Photos, iCloud, Amazon Photos. What happens when you switch?
• Unsearchable by content: “Find photos of mom at the beach” isn’t possible
• Missing context: Only you know why that blurry photo matters

The Vision

ptk provides:

Unified import from any source:

ptk import ~/Pictures/
ptk import ~/phone-backup/DCIM/
ptk import google-takeout.zip --source google-photos
ptk import icloud-export/ --source icloud

Intelligent organization by multiple dimensions:

ptk shell
ptk:/$ cd /people/mom
ptk:/people/mom$ ls
2019/  2020/  2021/  2022/  2023/  2024/

ptk:/$ cd /locations/beach
ptk:/$ cd /events/christmas-2023
ptk:/$ cd /years/2020/months/march

AI-powered features:

# Face detection and clustering
ptk faces detect --all
ptk faces cluster
ptk faces label cluster-7 "Mom"
ptk faces find "Mom"

# Scene captioning
ptk caption --all --model ollama/llava
ptk search "sunset over water"

# Semantic search
ptk ask "photos from our trip to Colorado"

Preservation guarantees:

# Verify nothing is corrupted
ptk verify --checksums

# Export to durable formats
ptk export ~/archive/photos/ --format longecho
ptk export photos.html --format html-gallery

# Original files always preserved
ptk originals list
ptk originals verify

Why SQLite?

Like the other Long Echo tools, ptk uses SQLite for metadata:

# Works even if ptk disappears
sqlite3 photos.db "
  SELECT path, caption, taken_at
  FROM photos
  WHERE caption LIKE '%birthday%'
  ORDER BY taken_at
"

The database stores metadata, face embeddings, captions, and organization. The actual photo files stay in place or are copied to a managed library, your choice.