Examples
Nothing in Eidos is named by the standard. EIDOS.md defines collections,
shapes, flavors, and properties — and never what any of them is called.
The easiest way to believe that is to see the same machinery answer to three different vocabularies. Each example below is a complete framework setup: what its collections are called, how its blueprints are grouped, what its shapes ask for, and what a real blueprint looks like.
A Software ProductA subset of YouTube — frames and specs, grouped by domain.
A Research ProgrammeA study of remote-work meeting load — frames and investigations, grouped by strand.
A BookHarry Potter and the Philosopher's Stone — frames and chapters, grouped by part.
The same machinery, three vocabularies
Section titled “The same machinery, three vocabularies”| Software | Research | Book | |
|---|---|---|---|
| Framing collection | frames — architecture, audience, criteria, market |
frames — question, prior work, method, ethics |
frames — premise, reader, voice, market |
| The units | specs |
investigations |
chapters |
| Grouped by | domain |
strand |
part |
| Flavors | full · micro |
full · note |
full · sketch |
| Its cast of roles | Developer, Designer, Project Manager, Stakeholder | Researcher, Reviewer (adversarial), Sponsor (non-technical) | Editor, Reader, Collaborator |
Every one of them also carries the Framework Owner role, who holds the intent, the scope, and the decisions.
What stays identical
Section titled “What stays identical”Under three sets of names, none of this moves:
- One file is one unit, complete, independent of time or status.
- Five core properties —
id,title,summary,flavor,connects_to— and no more required by the standard. - A framing collection declared first, whatever it’s called.
- One shape family per collection, offered as flavors with one default.
- A non-goals section carrying the most weight, wherever the shape puts it.
- No work-tracking fields, in any of them.