Eidos

Knowledge

@The-Virtual-Panda/ace

An Obsidian vault in the ACE shape (Atlas, Calendar, Efforts) with an Eidos framework under it; a flat atlas with maps, calendar entries grouped by series, efforts with heat as status, and a home page.

0installs in the last 30 days0installs in total

Install

The whole root

npx eidosmd install @The-Virtual-Panda/ace

One collection, or one variant into a collection you already have

npx eidosmd install @The-Virtual-Panda/ace --collection About This Vault
npx eidosmd install @The-Virtual-Panda/ace --variant About This Vault.practice
Source
The-Virtual-Panda/Eidos-Examples on GitHub
Tag
ace/v0.3.0
Path
ace
Eidos version
5.4.0
Naming
Title Case
Keywords
obsidianaceatlascalendareffortssecond-brain
Published
September 20, 2026

What it contains

Collections

About This Vaultframe

Two short pages: what this vault is for, and how it runs. The agent reads them before touching anything.

Variants

purposedefaultwhat the vault is for, and what it is not

Template: templates/frame.purpose.md

# {{title}}

_What this vault is for. Keep it short; a brain does not need a charter, just a sentence it can be held to._

## What This Is For

_A few sentences: what you keep here, what you do with it, and what you want to be true because it exists._

## Not This

_The vault you are deliberately not keeping: the task manager, the file dump, the journal of everything. Writing it down here is what keeps the vault from becoming a junk drawer._
practicehow it runs: where things land, the daily and weekly rhythm, naming and linking, what the agent may do

Template: templates/frame.practice.md

# {{title}}

_How the vault runs: the few habits that keep it alive. The agent reads this page before it touches anything._

## Where Things Land

_Where a new thought goes first (today's note, an inbox note), and what happens to it next._

## The Rhythm

_Daily, weekly, yearly: what each note is for and when you write it. The weekly look back is where an effort's heat changes and a loose note gets linked up._

## Naming and Linking Up

_How notes are named, how a note finds its map (`up`), and what a map is for. The habits that keep Atlas findable without folders._

## What the Agent May Do

_What an agent working alone may create, link, or change here, and what it has to leave for you. The line the Agent role keeps._

Atlasnote

What you know: one note per idea, source, or thing, and maps that gather them. Flat on purpose; a note finds its place by linking up to a map, not by its folder.

Variants

notedefaulta title and nothing more, on purpose

Template: templates/note.note.md

# {{title}}
mapa map of content: the notes it gathers, as links, in the order to read them

Template: templates/note.map.md

# {{title}}

## Map

_The notes this map gathers, as links, in the order to read them. A map is a note about notes; keep it a list and let the notes carry the content._

Calendarentry

When: dated notes, grouped by series. Daily, Weekly, and Yearly are the idea; add a series for any other run of dated notes (meetings, sermons, a trip).

Grouped by Series

Variants

daydefaulta day: what it is for, and what happened

Template: templates/entry.day.md

# {{title}}

## Today

_What today is for, in a line or two. Written in the morning, or not at all._

## Notes

_What happened, what you thought, what to keep. Link anything worth keeping up to its map before the week is out._
weeka week: the look back, and what is ahead

Template: templates/entry.week.md

# {{title}}

## Looking Back

_What the week did: the efforts that moved, the ones that cooled, the notes worth keeping. Set each effort's heat while it is fresh._

## Ahead

_What next week is for. Three things at most._
yeara year: its themes, and the look back as it closes

Template: templates/entry.year.md

# {{title}}

## Themes

_What this year is for, in a few words each. What every weekly look back gets read against._

## Looking Back

_Written as the year closes: what held, what did not, what next year inherits._
loga dated note in any other series: what was said, what to carry forward

Template: templates/entry.log.md

# {{title}}

## Notes

_What was said, what was decided, what to carry forward. Link the people and the topics up to their maps._

Effortseffort

What you are doing: one note per effort, its heat in status. The working notes live in Atlas; the effort says what they are for.

Variants

fulldefaultthe full page for an effort

Template: templates/effort.full.md

# {{title}}

## What This Is For

_Why this effort exists, and why now. A short paragraph. If this changes a lot, it is a different effort._

## Done Looks Like

_What finished looks like, as something you could check. If there is nothing here, the effort has no finish line, and that is fine as long as you say so._

## Still to Decide

_What you do not know yet. Kept near the top so it does not get buried._

## Not This

_What this effort deliberately is not, and which effort or map holds that instead. The section that keeps an effort from swallowing a life._

## Notes It Draws On

_The Atlas notes and maps this effort draws on and feeds, as links. The working notes live in Atlas; this page is the one that says what they are for._

## Notes and Decisions

_Notes: the next step, the reminder, the thing to remember. Decisions: one line each, dated, never deleted._

<!-- 2026-01-04: Put this to sleep until the studies finish; both wanted the same evenings. (Me) -->
quickwhat it is for and what done looks like; grow into full when it earns a finish line

Template: templates/effort.quick.md

# {{title}}

## What This Is For

_Why this effort exists, in a line or two. Grow it into the full page when it earns a finish line._

## Done Looks Like

_What finished looks like._

Other folders

  • Files Images, PDFs, and files the notes link to.

Roles

Agentroles/agent.md
# Agent

## Who they are

An AI working alone in the vault: a scheduled routine, an inbox sorter, a nightly linker. Nobody is in the seat. This role says what it may do without one.

## How to respond

- **Vocabulary & depth:** the vault's own names and nothing else. Write the way the owner would, in their register, or not at all.
- **Decisions:** none that matter. It may create a Calendar note for a day that has none, link a note `up` to the map its title and content plainly belong to, and flag an effort whose heat looks wrong. It may never change an effort's `status`, write a What This Is For, settle anything in Still to Decide, delete or rename anything, or create an Atlas note that says something the owner has not said. Anything past What the Agent May Do on the How It Runs page is a proposal, left as a note for the owner, not an edit.
- **Surface / hide:** when the owner comes back, show what it did and what it left as a proposal, in one list. Hide nothing it touched.
- **Focus:** the mechanical: notes that exist, notes with a way up, the index current. Leave the thinking.

## Calibration

None. An agent alone runs at the line How It Runs draws, whatever the owner's calibration says.
Framework Ownerroles/framework-owner.md
# Framework Owner

## Who they are

You. It is your brain: you decide what goes in, what it means, and what it is for. There is nobody to defer to and no reason to explain the vault to yourself; the role exists so the agent knows whose vault it is in.

## How to respond

- **Vocabulary & depth:** your own words, the vault's own names. No orientation; you know where things are. Go as deep as you ask, and no deeper.
- **Decisions:** all yours. Bring a choice when there is one; never file, link, or rename on your behalf without asking, unless How It Runs says the agent may.
- **Surface / hide:** lead with what you asked for, and the map or effort it belongs to. Keep everything else out of the way.
- **Focus:** whether a note has a way up, whether an effort still has a finish line, and whether the vault still matches What This Is For.

## Calibration

**Experience with the scope** is total. **Technical capacity** is yours to set; it decides whether the agent talks about how the vault works or only what is in it.

Top-level documents

  • Home Home.md where you start: the front page of the vault

Custom properties

statusTextEffortsHow hot the effort is right now: On is this week, Ongoing is always, Simmering is soon, Sleeping is not now, Archived is over. (On | Ongoing | Simmering | Sleeping | Archived)
date_createdDateevery collectionYYYY-MM-DD. Set once.
date_modifiedDateevery collectionYYYY-MM-DD. The last change.
tagsListevery collectionFree tags.
seriesrequiredTextCalendarWhich run of dated notes this belongs to (Daily, Weekly, Yearly, or one of your own). Matches its sub-folder.
upListAtlas, EffortsThe maps this note sits under, as links. The way up.
daterequiredDateCalendarThe day, week, or year this note is for.

Home

The first top-level document, as the author wrote it at this tag, placeholders included. Links open the source.

{{Product}}

Start here. This is an ACE vault (Atlas, Calendar, Efforts) with an Eidos framework under it, so you and an agent both know what each folder is for.

{{One line: what you keep here, and what it is for.}}

Where things are

  • About This Vault: two short pages: what the vault is for, and how it runs.
  • Atlas: what you know: one note per idea, source, or thing, and maps that gather them. Flat; a note finds its place by linking up to a map, not by its folder.
  • Calendar: when: daily, weekly, and yearly notes, and any other run of dated notes, grouped by series.
  • Efforts: what you are doing: one note per effort, its heat in status. The working notes live in Atlas; the effort says what they are for.
  • Files: images, PDFs, and files the notes link to.

How to use it

ACE is Nick Milo’s shape for an Obsidian vault: Atlas for knowledge, Calendar for time, Efforts for action. Eidos adds the agreement underneath: each folder has a template per kind of note, each note carries the few properties that make it findable, and two roles say how an agent behaves when you are in the seat and when it is alone. The Atlas template is a title and nothing more, on purpose. An effort’s heat is its status: On, Ongoing, Simmering, Sleeping, Archived. Change it in the weekly look back.

Built on Eidos. The page types, the properties each note carries, and the roles live in .eidos/; eidos check keeps it honest.