Lore

Try it

A sample wiki, in your browser.

Click around. This is the real interface running on twelve made-up pages — the folders, the trust states, the review list and the sign-off all behave as they do on your own wiki.

stack

4 pages · read straight off disk

Deploy pipeline

UnverifiedEdit

stack/deploy-pipeline.md · 14 inbound

  • Push to main deploys to production. There is no staging step.
  • A red build blocks the deploy — never override it.

Postgres notes

UnverifiedEdit

stack/postgres-notes.md · 6 inbound

  • Running Postgres 17. Connection pooling handled at the edge.
  • Migrations are forward-only. There is no down migration.

Auth decisions

AgingEdit

stack/auth-decisions.md · 9 inbound

  • Session cookies over JWTs. Revocation was the deciding factor.
  • Sessions live 30 days and refresh on use.

Glossary

UnverifiedEdit

stack/glossary.md · 11 inbound

  • Shared vocabulary for everything under stack.

Sample data, in your browser only. Nothing here reads or writes a file, and there is no server behind it — which is also true of the app you download, apart from the folder you point it at.

This is a mock — the real thing is one click away

These twelve pages are made up. If you want the real interface on your own notes without installing anything, /web opens a folder you choose and reads it in this browser. Nothing is uploaded there either; it is the same refusal to hold your data, done a different way.

What the real one adds

Your actual pages, a live watcher that notices what your agents changed, search across everything, the MCP server your agents connect to, and the verification ledger. The interface is the one you are looking at.

It is free

The download is the whole application — nothing is held back for a paid tier. Paid plans add syncing between machines, which is the one thing a program on one laptop cannot do for itself.