Front matter, at the back

Reference

What the words mean, what the labels are derived from, and every file these pages name — with the ones you cannot open marked as such.

Definitions

Words this book uses in a particular way, and the acronyms it does not spell out every time. Each one says where its definition actually lives; none of them is defined here for the first time.

The evidence labels

Every chapter carries a label, and no author types one: the build derives each from the record and refuses a record that tries to write its own. These are the rules it applies, read out of the build's own source when this page was made — so what you read here is what ran.

Parsed from opensentience.org/_patterns/build/build.mjs at build time.

The rung ladder

How close a witness is to having actually run somewhere a reader could check. A record may not claim a rung above the one the build can derive for it.

spec < in_tree < live_local < live_deployed < external

The three-valued outcome

The three-valued outcome vocabulary, used where a two-valued one would lie.

APPLIED

The work was done, and that is established.

REFUSED

The work was not done, deliberately, and the reason is published. A refusal is a result.

INDETERMINATE

Whether the work was done is not established. A timeout abandons a request but not the work under it, so 'no answer' is not 'no effect'.

Vocabulary from computedriven/receipts/R7-EXECUTED.md.

Files the book cites

Every path named anywhere in these pages, resolved against the tree when the site was built. The build refuses if one of them does not resolve, so a citation here has at least been checked to exist. A file in a repository that is not published is named and hashed but not linked: the book will not offer you a door that does not open.

opensentience.org 66 files

Published at https://github.com/c-u-l8er/opensentience.org.

ProjectAmp2 8 files

The working monorepo. It is not published, so a path in it can be named and hashed here but not linked or quoted.

WRL 6 files

Published at https://github.com/c-u-l8er/WRL.

computedriven 5 files

Not published at the time this page was built.

TRVM 5 files

Published at https://github.com/c-u-l8er/TRVM.

AmpersandBoxDesign 3 files

Published at https://github.com/c-u-l8er/AmpersandBoxDesign.

graphonomous 2 files

Published at https://github.com/c-u-l8er/graphonomous.

super 2 files

Published at https://github.com/c-u-l8er/super.

invariant-r10 1 file

A working directory of evidence packages, not a published repository.

studbook 1 file

A draft spec with no implementation and no published repository. Cited for what it says, not for anything it runs.

Questions

What is this book claiming?

That each chapter names one invariant, and that the label under it says exactly how much of it is established. Nothing on a page is stronger than its label. A chapter labelled STATED is a claim the book has not yet witnessed, and it says so on its own face.

Why does a chapter say STATED when the writing sounds confident?

Because the label is derived, not written. The build computes it from whether a check exists, whether a recorded run of that check exists for those exact bytes, and whether every claim the page cites is standing. An author cannot type a label in, and the build refuses a record that tries.

What makes a board different from a diagram?

A diagram is drawn. A board is a sealed WRL world reduced by TRVM's forge, and the frames you step through are that reduction's output. The geometry is computed from the graph, and the colours come from the Film.

Why can I not open some of the files the book cites?

They live in a repository that is not published. The book still names the path and its hash, because a citation you cannot follow is better than no citation — but it will not pretend to link you somewhere you cannot go.

Why are some wires unlabelled?

A wire that runs a long trunk down the margin carries its kind in its stroke, which the legend names, and in the readout when you hover it. The text was removed where it would have floated in a margin attached to nothing.

What is the counterexample section for?

A pattern that cannot fail is not a pattern. Once a record is WITNESSED the build requires a shipped counterexample — the case where the invariant does not hold — and refuses the record without one.

Is anything here peer-reviewed?

No. The evidence is a recorded run of a named check on named bytes, on one machine. That is a lower bar than review and a higher one than assertion, and every page states which of the two it has.

What does 'the build refuses' mean?

The build exits non-zero and emits nothing. It is not a warning that scrolls past: if a cited claim has been refuted, or a path does not resolve, or a count was typed by hand, the site does not get built at all.