What an organisation intends, published the way facts are
backlog/1 — the future tense of a record. One item per intention, filed where the work happens, emitted as a fragment per repository and merged into one list across an estate or a portfolio. Filed is private, publication takes a named human, and every item decays.
The record has a present tense and had no future one, so the intentions an organisation could actually collaborate on lived in seventeen to-do files and several heads. This is one item per intention, filed by the agent doing the work in the repository where the work happens, and merged into one list across an estate or a portfolio.
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.
flashy-backlogApache-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.