September 18, 2026 · Standard 5.3.0
Eidos 0.3.0
This is an older release. The latest is 0.18.0. See what’s new in 0.18.0
Edit the framework from the shell
The CLI takes standard 5.3.0 and edits the framework from the shell with a plan shown first, and the browser reads every top-level doc.
Release highlights
eidos configure:eidos configure:<noun> <operation>edits properties, collections, folders, groups, variants, terms, top-level docs, and roles, printing each change as a plan before it runs and rewriting every link a move breaks.- One blueprint's frontmatter:
eidos property get|set|unset @<blueprint>edits it, typed by the Properties table. - Top-level docs in the browser: A top-level doc reads in the same reader as a blueprint and can be added from the sidebar, and Show in Finder (Explorer, Files) sits beside Editor.
New
eidos configure
eidos configure:<noun> <operation> edits properties, collections, folders, groups, variants, terms, top-level docs, and roles, printing each change as a plan before it runs and rewriting every link a move breaks. Commands →
One blueprint's frontmatter
eidos property get|set|unset @<blueprint> edits it, typed by the Properties table.
Top-level docs in the browser
A top-level doc reads in the same reader as a blueprint and can be added from the sidebar, and Show in Finder (Explorer, Files) sits beside Editor. The browser →
Improved
Edits stay yours
A change on disk never replaces what you are editing, and a rename is a git mv where git is on.
The check sees the whole root
New findings cover a value off a property's list, an unclosed region, and a file or folder the framework does not describe, and strictness is the root's own setting. What check reports →
Changed
Standard 5.3.0
Every folder at the root is declared under folders and every file under top_level. eidos migrate makes each hop in place and reports what only you can decide. The hops →