An app, a service, or a system
Software@BuildableWorks/software
Frames for architecture, audience, criteria, and market, and specs grouped by domain.
- Frames
- Specs
Free for macOS, Windows, and Linux
Define what you’re making, and keep it true.
Eidos keeps every part of what you make as a plain file, shaped by a framework for your kind of work. A canvas, a backlog, a decision log, comments, and your own AI agent all point at those same files, in a folder you own.
Made foran appa novel seriesa worlda gamea channela coursea businessa renovation
No account. No subscription. Your files stay yours.
app downloadsnpm downloads last week
How it works
Three moves, whatever you make.
Write it down once, and everyone, every agent included, reads the same thing. Every move leaves a plain file in a folder you own.
Start from a framework
Pick the framework closest to what you make, from the Registry or right in the app. It sets the collections (chapters, specs, rooms, videos), their templates, and the properties each file carries, and you reshape it whenever it stops fitting.
Write one file per part
A character, a feature, a room, an episode: each is one markdown file with a permanent id, saying what that part is and why. The health check tells you which ones are missing a section or a property.
Work around it
Draw it on the canvas, plan it on the board, record what was decided, discuss it, and ask your agent about it. Every one of those points back at the same file, so nothing becomes a second copy of the truth.
One blueprinta markdown file with a permanent id
Core plugins
Everything points at the same files.
A canvas, a backlog, a decision log, comments, git, and your own AI agent, built into one free app. Each one points at the blueprint it serves, and switching one off leaves your files exactly as they were.
Your own agent, with your team’s commands
Claude Code, Codex, or any agent that speaks the Agent Client Protocol, beside every page, with what you have open as context. Grill a draft with /grill, file work with /task, log a call with /decide, and add slash commands of your own for the whole team.
Explore AI Agent
Work that points at what it builds
A real board, made of markdown: task types, subtasks, links, checklists, and statuses you define. Every task serves a blueprint by its id, and closes when the work ships while the blueprint stays.
Explore Backlog
Draw how the parts connect
Blueprints drawn live from their files, frames and labelled flows between them, sticky notes, and sketches you promote into real blueprints when they are ready.
Explore Canvas
Every call, confirmed by a person
Your agent logs what it decided as itself. A decision waits in an inbox until a person confirms it, then shows in the blueprint it was made for, with who confirmed it and when.
Explore Decisions
The discussion stays on the line it is about
Threads anchored to a section, with reactions and @mentions, signed by people and agents, and written into the file so every reader and every diff sees them.
Explore Comments
History without a terminal
File history and a diff viewer for every blueprint, commit and publish in a click, and auto save with commit messages your agent writes.
Explore Git
Also built in
- AssetsImages and PDFs linked to the blueprints they belong to, renamed without breaking a link.
- LinterOne markdown style for the whole root, applied every time a file is saved.
- TerminalYour own shell in the panel, started in the root.
- Several rootsEvery project you work on open at once, each in a tab of its own.
- The RegistryFrameworks to start from, and a place to publish your own.
- The CLIThe same core on npm, for scripts, CI, and every agent with a shell.
Frameworks
Start from a framework for your kind of work.
A framework is the shape of your files: the collections, their templates, and the properties each one carries. These are published in the Registry today, for very different work. Install one whole, take a single collection from it, or shape and publish your own.
A book, a long argument, or a course
Book@BuildableWorks/book
Frames for premise, reader, voice, and market, and chapters grouped by part.
- Frames
- Chapters
A fictional world, for a series or a table
World@The-Virtual-Panda/world
Places by region, factions, characters, arcs by campaign, a history, and a player role that sees only what is revealed.
- The World
- Places
- Factions
- Characters
- Arcs
A video game, a mechanic at a time
Game@The-Virtual-Panda/game
Mechanics and items by system, levels by act, characters and enemies, a cut list, a playtest log, and a playtester role that sees only what is in the build.
- The Game
- Mechanics
- Levels
- Characters
- Items
A video channel, a podcast, or a stream
Channel@The-Virtual-Panda/channel
Videos and posts by series, pages, a content calendar, a brand kit, and a rate card.
- The Channel
- Videos
- Posts
- Pages
A school of courses
Academy@The-Virtual-Panda/academy
Learner personas, courses by track, learning paths, and a catalog.
- The School
- Learners
- Courses
- Paths
A business as it develops
Venture@The-Virtual-Panda/venture
The thesis, the market, the money, and the runway; ideas, plans, and investments by line; and the decisions made.
- The Business
- Ideas
- Plans
- Investments
- Decisions
A question, a study, or a programme
Research@BuildableWorks/research
Frames for question, prior work, method, and ethics, and investigations grouped by strand.
- Frames
- Investigations
A house, room by room
Renovation@The-Virtual-Panda/renovation
Rooms by floor, the work by phase, selections by room, a schedule, and a change log.
- The Brief
- Rooms
- The Work
- Selections
A wedding, as its run of show
Wedding@The-Virtual-Panda/wedding
The big picture, moments by day, vendors by category, and the timeline.
- The Big Picture
- Run of Show
- Vendors
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
Eidos for…
Find the page written for you.
Each one starts from your problem, shows the framework to install, and the plugins that matter most for your work.
- AI buildersStop your agent from undoing what you already decided.For solo developers and founders shipping with Claude Code, Codex, or Cursor.
- Product teamsThe PRD that is still true after it ships.For the product manager and lead engineer whose team builds with Claude Code, Codex, or Cursor.
- Agencies and studiosEvery client project, built the same way. Every sign-off, a version.For agency owners, delivery leads, and tech leads running several client projects at once.
- Game developersThe game design doc that keeps up with the game.For indie and small-studio teams, designers and programmers alike, who want a GDD people actually read.
- Writers and worldbuildersYour story bible, checked, and never written for you.For novelists, worldbuilders, and tabletop writers with more world than one notebook can hold.
- FoundersYour thesis, your plans, and why you said no, in one place.For founders who are tired of rebuilding the deck and forgetting why they killed an idea.
- CreatorsEvery video on one page, from the hook to the sponsor read.For YouTubers, podcasters, and streamers who plan in series and work with an editor or a sponsor.
- Educators and course creatorsEvery course tied to what the learner will be able to do.For course creators, bootcamp teams, and teachers who build more than one course.
- Research labsEvery exclusion and deviation, decided and dated.For computational and mixed labs whose method lives in one person’s head.
- Obsidian usersKeep Obsidian. Give your vault a shape it keeps.For Obsidian users who want structure, a check, a backlog, and an agent on the vault they already have.
- Big personal projectsEvery quote, decision, and vendor, in one place.For a renovation, a wedding, or any project too big for one spreadsheet.
Where Eidos fits
Not a wiki, a tracker, or a prompt kit.
Each of those does its own job well. None of them keeps a checked definition of what you make, in your own files, that outlives the work. Eidos does that one thing, and works alongside the rest.
WikisNotion, Confluence
- Good at
- Everyone in the company reads and comments, with nothing to install.
- What it leaves open
- A template is only a starting page. Nothing checks it later, and it lives away from the work it describes.
Work trackersJira, Linear
- Good at
- Planning and tracking the work, more and more with agents in the loop.
- What it leaves open
- Specs hang off issues and projects that close, so what the product is gets archived with the work.
Spec-driven AI toolsGitHub Spec Kit, Kiro, OpenSpec
- Good at
- Getting an agent to plan in writing before it writes code.
- What it leaves open
- Agent-first and shaped around the next change: the agent drafts the spec, and the audience, the market, and the architecture have no home.
A docs folder and AGENTS.mdPlain markdown
- Good at
- Free, instant, and read by every editor and agent.
- What it leaves open
- No contract and no permanent ids, so nothing notices when a file falls out of shape or a link breaks.
Eidos
The definition, kept true.
- One file per part of what you make, with a permanent id
- Checked against a framework you declare
- Tasks, decisions, canvas nodes, and comments that point at those files
- Decisions that wait for a person to confirm them
- Your own agent, your folder, and a free app
Other apps have a canvas, a board, or an agent panel, and a few have all three. What Eidos adds is underneath: every unit is a markdown file checked against a framework you declare, served by a backlog and a decision log a person confirms, with frameworks you can share through a Registry, in one free, local app.
Human-first
The human authors. The agent facilitates.
A definition is a check on the work, and a check only works if it comes from somewhere else. Let an agent write the definition and then the work, and everything agrees while nobody decided anything.
So the intent, the scope, and the decisions stay with a person. Your agent reads the files, asks where you were vague, presses hardest on what is out of scope, and logs its own calls for you to confirm. Eidos itself never writes a sentence of a blueprint, and the agent only works when you ask it to.
A blueprint nobody thought through is worse than none.
Resume Playback
Help me tighten the Out of Scope before Tomás starts on it.
Before I add anything, three questions, because each one changes what the spec promises:
- Should trailers and extras resume too?
- If a viewer removes a film from their history, should it still resume?
- Is live sync between two devices a goal, or a non-goal?
I won’t write any of these in until you’ve answered.
Free, local, yours
Plain files, on your own machine.
No account, no subscription, no trial that runs out.
Nothing held back
The desktop app and the CLI are free for personal and commercial work, and nothing in them is a trial.
An open standard underneath
Blueprints are plain markdown in your repo, written to EIDOS.md, an open standard under Apache-2.0. Eidos MD is what sits on top, and your files never depend on it.
Nothing leaves without you
Eidos has no AI service of its own. The agent is the one you already run, under its own permissions, and your files stay on your machine.
Fast enough for agents
The CLI installs in seconds and answers in tenths of one, so an agent can lean on it all session.
εἶδος eidos, from the Greek: the form or essence of a thing.
Write down what you’re making.
Download Eidos MD, open a folder, and start from the framework closest to your work. Everything it gives you can be reshaped later.
macOS (Apple Silicon and Intel) · Windows 10 and 11 · Linux (AppImage and deb)
Rather have the terminal?
npm install -g eidosmd