engramlisted
Install: claude install-skill poorants/engram
# engram — networked PARA knowledge brain
Manage documents with the PARA method while weaving them into **one connected
knowledge network** through bi-directional links, MOC hubs, and integrity
linting. The core idea is *Networked PARA*: a logical link layer on top of
physical classification.
Two layers:
- **Management (PARA)** — create, move, archive, migrate, review. Folders own
governance.
- **Connection (network)** — link documents by context, clear orphans, weave
lonely spokes into a mesh rather than a star, catch broken links. Links own
context. The detailed rules are in
[references/linking-rules.md](references/linking-rules.md); load it before any
linking work and follow it.
The thing being defended is simple: **a session dies, knowledge should not.** The
measure of success is not investigating the same question twice.
## The store — resolve this first
The brain is normally **not a tree of files**. It is a Postgres-backed service,
and there is **one client for it**: the `engram` binary. Everything below is a
surface over that one client — the address, the token, the path rules and the
author byline live there, once.
1. **MCP tools (prefer these in a session)** — `brain_search`, `brain_get`,
`brain_revisions`, `brain_integrity`, `brain_put`, `brain_move`. Same
endpoints, same single ranking, no permission churn, and available before this
skill even loads. One difference: an MCP server is spawned once per session
and cannot see which checkout