Skip to content

Ecosystem

longecho is a convention before it is a program. The convention is small: a directory that carries a README.md (or README.txt) plus data in durable formats is a longecho-compliant source. Any tool that emits those two things produces one, whether or not it ever heard of longecho.

longecho is not an orchestrator: it never invokes or manages those tools. It does not own your data and it does not ask the tools to change. It reads what they produced, walks the tree, and reports on what is already there. check tells you whether a directory is compliant. query finds and searches sources across the whole tree. build generates a single-file site over them. None of these commands rewrite, migrate, or reformat the underlying data. The tools below stay independent: each is its own repository, with its own home, and each works without longecho installed.

Sibling tools

These repositories carry the longecho-ecosystem GitHub topic. Each is independent, lives in its own repository, and produces longecho-compliant exports.

  • arkiv: universal personal data format (JSONL in, SQL out). Its directory exports are longecho-compliant by construction, and the memex tools below write their exports through it.
  • llm-memex: conversation knowledge base across AI providers.
  • repoindex: filesystem git catalog with project metadata.
  • chartfold: personal health data consolidated from multiple record systems into SQLite.
  • jot: plaintext journal, notes, and tasks.
  • pagevault: password-protected content for static sites.

posthumous, a federated deadman-switch with TOTP check-in, is adjacent rather than a producer: it shares the same durable, local-first, self-hosted stack.

The memex family

The *-memex archives each keep one kind of personal data in SQLite, and each can export an arkiv directory: JSONL records, a schema.yaml data dictionary, and a README with frontmatter. That export is a longecho source with no further work. They are not tagged ecosystem members; they are examples of how ordinary tools become producers.

Export them as directories rather than bare .zip bundles: longecho never reads inside an archive file, so a bundle on its own is durable but not a source.

Markdown sources (Hugo, Obsidian, plain note folders) are compliant with no extra work, since Markdown is already a durable format.

Fractal sites

The generated sites compose. A parent archive's site links out to each child's site, so an archive of archives stays navigable at every level. You can run build at the top and reach every interface below it without leaving the page.

Read further

The broader narrative lives in The Long Echo essays and on the longecho project page. For the convention itself, see the philosophy and the Specification.