Eidos

Keep Obsidian. Give your vault a shape it keeps.

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.

An Obsidian vault in the ACE shape open in Eidos: the effort Write the Garden Zine, with its heat set to On, the map it sits under, what done looks like, and what is still to decide, and the two tasks serving it in the panel beside it.
An effort in an ACE vault: its heat, the map it sits under, and the tasks that serve it.

Sound familiar?

The vault was organized, once.

Then came the third rebuild.

  1. Every note a little different

    A property spelled three ways, half the notes with a status and half without, and no list of which ones drifted.

  2. Rules you carry in your head

    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.

  3. Plans that point nowhere

    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

ACE, written down where the vault can be checked against it.

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/.

About This Vault
Two short pages: what the vault is for (and is not), and how it runs, including what an agent may do on its own.
Atlas
What you know: one note per idea, and maps that gather them. Flat on purpose; a note finds its place through its up link to a map.
Calendar
Dated notes grouped by series: daily, weekly, yearly, or a run of your own, such as meetings or a trip.
Efforts
What you are doing, with its heat as its status: On, Ongoing, Simmering, Sleeping, or Archived.
The Efforts of an ACE vault as a table: six efforts with a one-line summary each and their heat as status, from On and Ongoing to Simmering, Sleeping, and Archived.

What you will use most

What Eidos adds on top of the vault.

  • Blueprints

    A check for drift

    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.

  • Backlog

    A backlog beside your efforts

    Tasks as markdown files in the vault, on a board, each pointing at the effort or note it serves.

  • Canvas

    A canvas that goes back to Obsidian

    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.

  • Decisions

    Decisions that stay made

    “Twelve spreads, not twenty.” Logged once against the effort, confirmed by you, and listed beside it whenever it is open.

  • AI Agent

    An agent that knows the vault’s rules

    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.

  • Linter

    One markdown style

    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

Put a framework under the vault you have

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.

  • Reading, a live editor, and Source, as in Obsidian
  • Import your vault’s theme in Preferences
  • Properties edited as typed fields
$ 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

Draw it here, open it there

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.

A canvas of an ACE vault: efforts coloured by their heat, the maps they draw on, and the notes a zine draws on, joined by arrows, with a sticky note about the weekly look back, and the Export menu open on JSON Canvas (Obsidian).

Start here

Put the ACE framework under your vault.

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

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.

See it in the Registry
The Atlas of an ACE vault as a table: notes and maps, each with a one-line summary, its variant (note or map), and the map it links up to.

Give your vault a framework tonight.

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.