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.
1. The protocol
The specs and schemas on this page. They are open now, under CC-BY-SA-4.0. Build on them without asking.
2. The engines
The software that runs the protocol. It stays private until any organisation meets the public gate in the charter. Then it opens to everyone.
3. The service
What Leap of Faith Labs runs for organisations, for a fee. Your records can always leave it, as files in this format.
The four kinds of record
Each one has a spec to read and a schema to check against.
A promise
A signed statement by one person or organisation about what they will do. It never promises someone else’s result. It carries its reasons for and against.
Evidence
What was done, what it left behind, and who checked it. There are four levels of checking, from L0 to L3. The level says how something was checked, not how good it was.
A deliberation record
The reasons for a decision, and the reasons against it. The disagreement is kept. The field for disagreement can never be empty.
The record envelope
The few fields that every record carries. With them, records from different tools read the same way.
Rules every record keeps
Every record keeps these four rules, whatever tool made it.
No numbers that rank
No field is called score, rank, rating or points. Records are shown together as a set, never sorted into a league.
Promises are about yourself
You promise what you will do. No one signs another person’s promise.
Nothing is deleted
A newer record corrects an older one and says which one it replaces. The older record stays readable.
No personal data about the people served
No names, photos or details of students, parents, patients or community members, in any field.
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.
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.
spec/01-promise.mdspec/02-evidence.mdspec/03-deliberation.mdspec/04-envelope.mdschema/promise.schema.jsonschema/evidence.schema.jsonschema/deliberation.schema.jsonschema/envelope.schema.jsonexamples/promise-m-2026-11.jsonexamples/README.mdCHARTER.md· as a pageLICENSE· the full licence textledger.json· every fingerprint
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.