Versioning
Three things version separately, all with Semantic Versioning.
| The standard | The CLI | The Claude plugin | |
|---|---|---|---|
| Current | 5.5.0 | 0.14.0 | 5.5.0 |
| Lives in | EIDOS.md, Buildable’s repository |
eidosmd on npm |
The plugin beside the standard |
| A root records it as | eidos_version in Framework.yaml |
not recorded | not recorded |
| Moves when | the text of EIDOS.md moves |
the tool ships | any plugin release ships |
| History | versions/ |
Releases | CHANGELOG.md |
The tooling moves far more often than the standard. Each CLI and plugin release names the standard it carries; Standard: unchanged means your roots need nothing.
Which version am I on?
Section titled “Which version am I on?”eidos framework # the root's eidos_versioneidos --version # the CLI, and the standard it carrieseidos check reports a root on an older standard once, as a warning, and works with it as it stands. The framework in front of the tool is the operative contract either way.
Migrating
Section titled “Migrating”Each release of the standard is frozen in versions/ under its full number. A migration goes directly from any source version to any target by diffing the two snapshots: v1.0.0 to v5.5.0 is one hop, not many.
eidos migrate --dry-run # the moves it would makeeidos migrateeidos migrate makes the mechanical part of the hop: renames what moved, rewrites the standard’s properties.core block, sets eidos_version, and carries every plugin folder and region across untouched. It reports what only the owner can decide and does not do it. Your own properties under properties.custom are never touched.
What each hop moves, what stays, and what needs a person is in versions/MIGRATIONS.md. The migrate skill walks the judgment calls with you. Skills →