Versioning

PO9 versions two things independently:

• Spec version — the format itself (spec: 1 in the manifest). An integer.
• Skin version — a creator’s own release, in semver.

Compatibility promise

• A skin valid under spec N stays valid under every later minor revision of N.
• Additive changes (new optional tokens, new asset types) land in minor spec revisions and never break existing skins.
• Breaking changes require a new major spec version and MUST ship a migrator.

Targets advertise the spec versions they support; the Validator checks the skin’s spec against them.

Roadmap

The direction of the standard — not app features. This is what companies adopting .po9-skin are really betting on.

Stage	Version	Focus
Current	v1	Stable core: manifest, tokens, assets, packaging.
Next	v1.1	Animation tokens (animation.*). Additive, non-breaking.
Later	v2	Plugin extension points. Major — ships a migrator.
Future	—	Enterprise policy: signed skins, org-level allowlists.

Note

The roadmap is a statement of direction, not a delivery commitment. Dates are intentionally omitted.