configure

Change the form: the structure and contract in _eidos/Framework.md. Its collections and their flavors, its property Schema, and its Top-Level index.

A seed is a starting point, not a cage — a framework may reshape or override any of it without forking the standard. This is the skill that does it.

It presses you to decide

A collection, flavor, or property nobody thought through reads as meaningful while no one knows what it holds. It won’t invent them or guess their shape. If you offer only a name, it asks for the rest.

For a collection — its name (the folder, in the framework’s convention), a one-line description, how it groups its blueprints, at least one flavor with a default, and how it draws on the canvas.

For a flavor — its name (lowercase: full, micro, api), a one-line description, and its shape: the sections the body carries.

For a property — all four, because a property missing any one of them is unusable:

Field	Why it’s required
name	The frontmatter key. Lowercase, words joined by underscores, matching the core style (summary, connects_to).
type	From the Obsidian set: Text, List, Number, Checkbox, Date, Date & time. Anything richer belongs in the body.
applies to	all, or a list of collections — so a field never lands where it makes no sense.
meaning	One line: what it holds and why. This is what stops it rotting into a mystery field.

Renaming and retiring

Both touch real data in real blueprints, so it surfaces what’s there before changing anything. It won’t silently drop values.

Retiring is the neglected half. A root accumulates properties nobody fills, and each one adds noise to every blueprint. If a property has been blank on the last twenty blueprints, it isn’t part of your contract any more.

Boundaries

Never touches `### Eidos Core`

Those properties move with the standard’s version, and migrate rewrites that block. A core property change is a standards change, and it will redirect you rather than make one.

• The Framework body only — its ## Top-Level, ## Collections and ### Custom Properties sections, plus shape files in _eidos/shapes/. Not per-collection index.md files (index), not blueprints (eidos).
• Needs a framework. No _eidos/ means nothing to configure — it offers install instead.
• Shapes stay yours. A flavor’s sections are a content decision. It scaffolds a starting point, usually by trimming the collection’s default flavor, and lets you shape it.

Related

• Shaping Your Framework — when and why, at length.