The LOFL protocol

An open, plain way to write down good work, so that anyone can check it. You may build on it without asking us.

LOFL protocol · v0.1.0 · published 8 November 2026 · CC-BY-SA-4.0

What the protocol is for

A protocol is a shared set of rules for writing records. When two tools follow the same rules, each one can read the other’s records. This protocol has four kinds of record: a promise, evidence, a deliberation record and an envelope.

Each kind has a spec, written in plain English. Each one also has a schema. A schema is a file that a computer uses to check that a record has the right shape. If the spec and the schema disagree, the spec is right, and the schema gets fixed.

The three layers of LOFL

Only the first layer is on this page. The other two follow their own rules, set out in the charter.

Read the charter →

The four kinds of record

Each one has a spec to read and a schema to check against.

Rules every record keeps

Every record keeps these four rules, whatever tool made it.

The first real promise

M, who founded LOFL, made the first promise in the protocol. M signed it on 8 November 2026, with a key that only M holds:

“I will change the LOFL protocol only by publishing a new version that supersedes the old one, and never edit a published version.”

So the files on this page are never changed. A change comes as a new version, and the old one stays.

Read the signed promise How it was made

How to check the files yourself

Every file has a fingerprint. Anyone can work it out again.

A fingerprint is a short code made from a file’s exact bytes. If one byte changes, the fingerprint changes too. This protocol uses a kind of fingerprint called sha256. The file ledger.json lists every file with its fingerprint.

The files here are copied byte for byte from the repository at version v0.1.0. The tools that check records live in the repository, not on this site. With Python 3 on your computer, run these:

git clone --branch v0.1.0 https://github.com/leap-of-faith-labs/lofl-protocol
cd lofl-protocol
python3 tools/hash.py --check
python3 tools/validate.py examples

The second check also tests the signature on the promise.

Every file on this page

The repository also holds a README, a change log and the tools. Those stay there.

What is still a draft

The specs are drafts. They will change, but only through new versions that replace this one. Each new version gets its own line in the change log.

The charter has a licence text for the engines, in its section 4. A lawyer has not read it yet. We publish it anyway, marked as a draft, because hiding it would be worse.

Build on it, or disagree in the open

The repository on GitHub Discussions