@flashyos/canon

A lockfile for facts

canon/1 — a lockfile for facts. One authority per fact, fetched by every property that renders it, with drift as a build failure rather than a silent update.

Why it exists

Ten properties render the same definitions, counts and paths, and each was typed in by hand — so changing one meant remembering every place it was written, and the places nobody remembered were wrong quietly for a year. This is `npm install` for prose: one authority, a revision, a lockfile, and a build that fails when they disagree.

Use it

npx canon check

Installing it puts this command on your path — read from the package’s own manifest, so this list cannot drift from what you actually get.

The licence

Apache-2.0, read from the package’s own manifest. Embed it in anything, including closed software — that is what makes a spec adoptable and a verifier worth running. FlashyOS’s server side is AGPL-3.0-only instead, and a test in the monorepo asserts the direction between them: AGPL code may consume this, this may never consume AGPL code.

Keep reading