Documentation

Build on the open format.

Everything to author, read, sign, and move a .laplaspack — the open, MIT-licensed memory format. Zero-dependency reference tools; a formal grammar; and the apps built on top.

quickstart — read any pack, offline
# the reader needs nothing but the Python standard library
$ curl -O https://raw.githubusercontent.com/AnYejun/laplaspack/main/laplaspack_reader.py
$ python3 laplaspack_reader.py founder.laplaspack --why "the core offer"
◈ Subscription  ← derived-from ← Founder Interview ← supports ← Pricing
provenance intact · offline ✓
The format
.laplaspack
The spec, the pack anatomy (canonical / derived / optional), and the six causal roles — a SQLite container you own.
Read the standard →
LMD grammar
The human-authored source format packs compile from, formalized in EBNF — headings, properties, causal edges, thinks.
grammar.ebnf →
Addressing · draft
Publish, fetch, and mount packs at a laplas:// address — the network layer (v0 draft).
HUB.md →
Reference tools · Python stdlib
reader.py
Read any pack offline: summary, entities, and the causal ancestry behind any claim. Zero dependencies.
reader.py →
seal.py
Sign a pack with Ed25519 and verify offline that it wasn't tampered with. (Needs pip install cryptography.)
seal.py →
writer.py · merge.py
Compile LMD into a pack (build-time validation) and merge two packs deterministically by declared id — zero model.
writer & merge →
The apps built on it
LAPLAS Desktop
Capture your context as a structured graph and recall it grounded — the app that authors packs.
LAPLAS →
Manifesto
Turn a pack into a grounded concierge for your site — an answer with a receipt on every claim.
Manifesto →
AX Console
Serve a pack to your agents — recall-grounded, cited, with a human approval gate on every write.
AX →
The format is a v3 draft, MIT-licensed and public: github.com/AnYejun/laplaspack. No external adopters yet — it's a spec published in the open, not an industry standard. The full reference implementation is in the repo.