An Obsidian vault in the ACE shape
ACE@The-Virtual-Panda/ace
Atlas, Calendar, and Efforts, with an Eidos framework under the vault.
- About This Vault
- Atlas
- Calendar
- Efforts
In the app: New Project, then pick it from the list.
Eidos opens the same markdown files as your vault and adds a layer underneath: a framework the vault is checked against, a backlog beside your efforts, and your own AI agent that knows what each folder is for. Obsidian still opens every note.
Free for macOS, Windows, and Linux. No account, no subscription.

Sound familiar?
Then came the third rebuild.
A property spelled three ways, half the notes with a status, and no list of which ones drifted.
Where a note lands, how it links up, when an effort cools: the system lives in your head, and an AI agent editing the vault has never heard of it.
To-dos in one plugin, the plan on a canvas, and neither tied to the note it’s about.
How it fits
ACE is Atlas, Calendar, and Efforts, the shape Nick Milo teaches, as an Eidos framework: a template for each kind of note, the few properties that make a note findable, and two pages an agent reads before it touches anything. It lives in its own folder inside the vault, with its setup in a hidden .eidos/.
up link to a map.
What you will use most
The check lists every note missing a property or a section, or with a link that goes nowhere. A strict setting makes any of it fail.
Tasks as markdown files in the vault, on a board, each pointing at the effort or note it serves.
Lay out efforts and maps as cards drawn live from their notes, then export the page as JSON Canvas for Obsidian’s Canvas.
Claude Code or Codex beside the note. The framework’s Agent role says what it may do alone (make today’s note, link a note up, flag an effort) and what it never does: change your heat or settle an open question.
One list marker, one emphasis style, no stray blank lines, in every file Eidos writes. Switch off any rule your setup disagrees with.
Same files
Eidos reads plain markdown with YAML properties, in the types Obsidian shows (text, list, number, checkbox, date). Installing ACE in a new folder adds .eidos/ and the framework’s folders there, and leaves every other note as it is. Move a note in, and the check tells you if it still needs an id and a title.
$ cd ~/Vaults/Field\ Notes
$ eidos install @The-Virtual-Panda/ace Blueprints --naming "Title Case"
✓ installed @The-Virtual-Panda/ace → Blueprints (Eidos 5.5.0, naming Title Case)
collections: About This Vault, Atlas, Calendar, Efforts
$ mv "Atlas/Bloom Time.md" Blueprints/Atlas/
$ eidos check
Atlas/Bloom Time.md
✗ id-missing no `id`; add a permanent identity (a slug, a number, a GUID)
✗ title-missing no `title`Back to Obsidian
A canvas in Eidos is drawn from the notes and styled by their properties: here each effort’s border shows its heat. Export any page as PNG, SVG, or JSON Canvas for Obsidian.

Start here
In the app, choose New Project and pick your vault’s folder. The vault is offered as the project, so its folders can become collections where they are, and every note stays as it is. To keep the framework apart, name a folder inside it instead. From a terminal, run the install inside the vault with . as the folder, or a new folder as above. Either way, keep Title Case so the names match your notes.
An Obsidian vault in the ACE shape
Atlas, Calendar, and Efforts, with an Eidos framework under the vault.
In the app: New Project, then pick it from the list.

Download Eidos MD, open your vault’s folder, and put ACE under it. Your notes stay markdown, and Obsidian still opens them all.
Free for macOS, Windows, and Linux. Your files stay plain text in a folder you own.