Glossary
Every term the standard uses, in the order they build on each other. This is
EIDOS.md’s own vocabulary table, with pointers into the rest of these docs.
The one folder Eidos lives in, holding the framework, the collections, and any
top-level docs. Found by the hidden _eidos/ inside it, never by its name.
→
framework
Section titled “framework”The form everything is written in — its collections, shapes, flavors, roles,
naming convention, and Schema. Lives in the hidden _eidos/ at the root.
Portable: one framework governs any number of roots.
→
collection
Section titled “collection”A top-level folder of repeated blueprints that share a body shape. A framework declares each one, and may group a collection’s blueprints in one level of sub-folders. →
blueprint
Section titled “blueprint”One markdown file in a collection, defining one unit completely. Frontmatter (a contract) plus a body (a shape). →
A blueprint describing the whole thing rather than one unit of it. Frames set what every other blueprint is judged against, and are revised whenever that judgment changes. Every framework declares a framing collection. →
One body template: the sections a blueprint carries, in order, under set names,
each with its guidance. Body only; frontmatter is generated. One file per
shape, in _eidos/shapes/.
→
flavor
Section titled “flavor”A collection’s shapes are variants of one family, and each variant is a flavor
(<kind>.<flavor>). A collection declares one or more and marks one default —
typically a light flavor a blueprint can grow out of, beside a fuller one.
→
property
Section titled “property”One frontmatter field: a name, a type, which collections it applies to, and a meaning. →
Schema
Section titled “Schema”The framework’s whole property contract: the core properties Eidos requires, plus whatever the framework adds. →
top-level doc
Section titled “top-level doc”A one-of-a-kind document at the root — a Roadmap, a Vision, the generated canvas. Free-form: no shape, no flavors, no validation. →
A response contract for one role, saying how an agent talks to that kind of person. →
Who is in the seat right now: their role, plus a personal calibration. →
A starting framework the standard ships. install copies one into a new
root.
→
Terms Eidos deliberately does not define
Section titled “Terms Eidos deliberately does not define”Worth naming, because their absence is the point.
| Not defined | Because |
|---|---|
Specs, Chapters, Frames … |
Collection names belong to a framework, never to the standard. |
## Intent, ## Out of Scope … |
Section names belong to a shape. The standard never governs a section. |
status, domain, tags … |
Eidos defines no custom properties. Every one of these is a seed’s choice. |
| A grouping | A collection’s grouping is the collection’s own. |
sprint, estimate, assignee |
Forbidden outright. These turn a blueprint into a task. |
- Conventions — the load-bearing ones, grouped.
- Versioning