Home

enumeratio and notatio: the wiki

Design, direction and how the work is run, for the repository enumeratio/notatio. The public documentation (guides, reference, the catalogue) is at enumeratio.dev and ships with the packages; nothing here is user documentation.

The names

• compute-engine computes: the engine and the mathematics.
• Epsil is compute-engine's language, and the only text syntax we read or write.
• enumeratio is the catalogue: a permanent address and a record for every mathematical object, and the checking that keeps the records true.
• notatio is how an expression is written and shown: the presentation heads, their markup, and the notebook built from them.

Names is the full rule, with a table of what belongs where.

Start here

Page	For
Names	Which of the four a thing belongs to, and how to say so in prose
Roadmap	What each part is for, where it is going, and what moves into compute-engine
Sites	The two sites, and the promise the catalogue's URLs make
Ideas	Ideas with no design and no owner yet
Contributing	The toolchain, where a change goes, tests, git, and sending work upstream
Lanes	How parallel work is divided, landed and logged
CI-and-Deployment	The workflows, the checks and how the site ships
Design	Every design page, by subject

How pages are named

• A plain name (Boxes, Structures) states what is true now, in the present tense. Its first line gives a status where one helps: current, partly built, agreed and not built.
• Speculative-… is a proposal that is not adopted. When part of one is adopted, that part moves to the plain page and the banner says so. When all of it is, the page is promoted to a plain name or folded into one.
• Archive-… is retired: a design that was replaced, an adopted design as first written, an audit that was acted on, or a survey from the Postgres-era project. It is kept for its reasoning and is not maintained.

A rule that binds a change is also in the repository's AGENTS.md, in one line, and the two change together.