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 Root, then pick it from the list.
Eidos opens the same markdown files your vault already holds and puts a layer underneath: a framework the vault is checked against, a backlog beside your efforts, a decision log, 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 half without, and no list of which ones drifted.
Where a note lands, how it links up, when an effort cools down: the system lives in your memory, and an AI agent editing the vault has never heard of it.
To-dos in one plugin, the plan on a canvas, the decisions nowhere at all, and none of them tied to the note it is about.
How it fits
The ACE framework is Atlas, Calendar, and Efforts, the shape Nick Milo teaches, with an Eidos framework under it: 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 a hidden .eidos/ folder beside .obsidian/.
up link to a map.
What you will use most
The check lists every note missing a property its folder asks for, a section its template expects, or a link that goes nowhere, and 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, the format Obsidian’s Canvas reads.
“Twelve spreads, not twenty.” Logged once against the effort, confirmed by you, and listed beside it whenever it is open.
Claude Code or Codex beside the note. The framework’s Agent role spells out 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 what is still to decide.
One list marker, one emphasis style, no stray blank lines, applied to every file Eidos writes. Each rule can be switched off if your own setup disagrees.
Same files
Eidos reads plain markdown with YAML properties, in the types Obsidian shows (text, list, number, checkbox, date). Installing ACE in the vault adds .eidos/ and the folders the vault lacks, and leaves your notes as they are. The first check then tells you which notes still need an id and a title to join in.
$ cd ~/Vaults/Field\ Notes
$ eidos install @The-Virtual-Panda/ace . --naming "Title Case"
✓ installed @The-Virtual-Panda/ace → . (Eidos 5.5.0, naming Title Case)
collections: About This Vault, Atlas, Calendar, Efforts
$ 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 themselves and styled by their properties: here each effort’s border is its heat. Export any page as PNG, SVG, or JSON Canvas for Obsidian.

Start here
In the app, choose New Root on the folder that holds your vault and give the vault’s own folder as the place for the root. From a terminal, run the install inside the vault with . as the root, as above. Either way, keep Title Case so the names match the notes you already have.
An Obsidian vault in the ACE shape
Atlas, Calendar, and Efforts, with an Eidos framework under the vault.
In the app: New Root, then pick it from the list.

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