install

Stand up a new Eidos root where there isn’t one. It asks what you’re defining, offers the seed frameworks, installs the chosen one into _eidos/, and scaffolds a root around it.

What it asks

Two answers are awkward to change afterwards, so it settles them up front:

The root folder name. Blueprints by default, but it can be anything — nothing points at a root by path. A root is found by the hidden _eidos/ inside it.

The naming convention. kebab-case (the default), TitleCase, or Title Case. One convention governs the whole root, and changing it later means renaming every file. More →

Then which seed to start from — one for a product, one for a book, one for a programme of inquiry. Take the nearest; everything a seed gives you is changeable later, so “close enough” is the right answer.

What lands on disk

DirectoryBlueprints/
- README.md the human “start here”
- Directory_eidos/ the framework — the form
  - Directoryshapes/ body templates, one file per flavor
    …
  - Directoryroles/ how the agent talks to each kind of person
    …
  - Framework.md index + config + the property Schema
  - me.md who’s in the seat (personal, gitignored)
- Directoryframes/ the framing collection
  - …
- Directoryspecs/ the units, grouped one level deep
  - …

It carries the seeds

One of three skills that ships a committed copy of part of the standard — in this case the canonical seed frameworks, so it can scaffold where it can’t reach the repository root. Why →

After it runs

Commit the whole root alongside the code, _eidos/ and all — except the personal me.md, which the seeded .gitignore keeps out.

From there: whoami sets who you are, eidos authors and validates, configure reshapes the framework, and index rebuilds the leaves.

For a root that already exists, this is the wrong skill — use eidos or migrate.