Labels
Every statement in a record or on the roadmap carries one label, so you can tell what is known from what is planned:
| Label | Meaning |
|---|---|
observed | Seen directly, for example a response or a published file |
inferred | Concluded from observed facts |
proposed | Planned, not available |
unknown | Not yet established |
superseded | Replaced by a later statement, kept for the record |
A label changes only with new evidence. Superseded statements stay published so the history can be checked.
Records
A public record describes one subject as a list of claims, each with its label and evidence. Records carry a version and an as_of date; a new version replaces the old one. The first record is Dusk State's record of itself, dusk-state.
Versions
| What | Format | Example |
|---|---|---|
| API | Major version in the path and the X-Dusk-State-Version header | /api/v1/, 1 |
| Policies | <slug>-<date>, then .2, .3 for later versions on the same day | privacy-2026-10-04.2 |
| Docs pages | <path with dots>-<date>, same suffix rule | api.errors-2026-10-06 |
| Records | <date>.<n> | 2026-10-04.8 |
Publishing a new version of a policy or docs page supersedes the previous one. Superseded versions are kept.
Published
"Published" means available now. A product is published only when it can be fulfilled; a capability is listed in /capabilities.json only when it works. Prices are in minor units (pence for GBP).