These docs are under active development and cover the v0.20 Kobicha security model.
Peios Learn
On this page
Print Full Specification
§3.1

Version Numbers

§3.1.1 SemVer synchronisation

PSD versions MUST use Semantic Versioning (MAJOR.MINOR.PATCH), synchronised with the Peios software version. When a specification is updated, it MUST take the version number of the software release that the change ships with.

The patch component MUST be omitted when it is zero. v0.22 is correct; v0.22.0 is not.

ⓘ Informative
This synchronisation means specification versions are sparse and irregular. KACS might go v0.20 → v0.22 → v0.56.1 because all the versions in between belonged to other subsystems or software changes. This is expected -- the version number tells you when in the release timeline the specification was updated, not how many revisions it has had.

§3.1.2 Complete editions

Each version of a specification MUST be a complete, self-contained edition. Versions are not diffs or patches on previous versions. A reader MUST be able to understand the specification from a single version directory without consulting other versions.

§3.1.3 Revision count

Each specification has a revision count equal to the number of version directories under its specification directory. The revision count MUST NOT be stored explicitly -- it is derived from the filesystem.

ⓘ Informative
Trail renders the revision count in the specification header. Example: PSD-004 — KACS v0.56.1 (revision 3). The SemVer tells you when in the release timeline the specification was last updated. The revision count tells you how many times it has been updated. Together they answer both "is this current?" and "is this mature?".