Home

Aught One Normalize

The project's durable knowledge: why the canonical forms are shaped the way they are, what the modules promise, and how to work on them. Anything with a status that will someday be "done" is a tracker issue instead — see WORKFLOW.md.

Start with How This Documentation Works if you are new to the layout. Each section below explains what belongs in it.

• Architecture Decision Records — hard-to-reverse choices, and why the alternatives lost.
• Specifications — how the suite is built and the standards it is held to.
• Research — investigations and designs still being worked out.
• Developer Guides — how to build, extend and release this project.
• Reference — settled facts kept close, including what this suite has decided not to build.

The governing constraint runs through all of it: the same input must produce the same canonical bytes, on any platform, at any time. A consumer hashes a canonical form and discards the original, so a one-byte difference is an undetectable, unrecoverable miss. Read Normalization Suite Structure before changing anything that can reach a canonical string.