Glossary

EIDOS.md’s own term table, with pointers into these docs.

Term	What it is
product	What you are defining: an app, a book, a study, anything work produces that has a shape.
framework	How the files are organized: folders, templates, properties, vocabulary, roles. Lives in .eidos/; one framework can govern many products. →
root	The folder it all lives in. Found by the .eidos/ inside it, never by its name. →
folder	A top-level folder in the root, declared with who owns it: @eidos/collections for the standard, @<tool>/<kind> for a tool, nobody for the person’s own. →
collection	A folder owned by @eidos/collections, holding blueprints of one kind: specs, chapters, investigations. Its sub-folders, if any, are its declared groups. →
blueprint	One markdown file in a collection, defining one unit of the product completely: properties on top, a body below.
unit	What one blueprint defines: a spec, a chapter, an investigation. Templates are named for it, singular.
template	The body a collection’s blueprints follow: sections in order, under set names. Body only. One file per variant in .eidos/templates/. →
variant	One of a collection’s templates, <unit>.<variant>.md. One is the default; a blueprint on another says so in variant.
property	One frontmatter field: name, type, which collections it applies to, whether required, meaning, and options when closed. The whole table is the framework’s Properties. →
vocabulary	The framework’s table of words used on purpose: what each means and what it is not. →
top-level doc	A one-of-a-kind file at the root, listed in the framework document. No template; the body is never validated.
role	How an agent talks to one kind of person. .eidos/me.md says which role is in the seat. →
plugin	A tool’s own folder, .eidos/plugins/<name>/, and any root folder it owns. The standard reads none of it. →
region	A span in a markdown file that a tool owns, fenced by two HTML comments carrying its name. →

These docs also say framework document for .eidos/Framework.yaml, the one file that declares the framework, and frame for a blueprint in a framing collection, one describing the whole product. →

What Eidos deliberately does not define

Not defined	Because
specs, chapters, frames	Collection names belong to a framework.
## Intent, ## Out of Scope	Section names belong to a template.
status, domain, tags	Eidos defines no custom properties. Every one is a seed’s choice.
sprint, estimate, assignee	Forbidden. These turn a blueprint into a task.