eidosmd 0.1.0 → 0.3.0

package/standard/seeds/book/Framework.yaml

@@ -0,0 +1,61 @@
+# The framework document: the structure this root is written in. See EIDOS.md for what each key means;
+# the `eidos` CLI edits this file. Every path is relative to this folder.
+
+eidos_version: 5.3.0
+
+# kebab-case | TitleCase | Title Case. Settled at install; changing it later means renaming files.
+naming: kebab-case
+
+# Every file at the root, one entry each.
+top_level:
+  - title: README
+    path: ../README.md
+    description: "the root's front door: what this book is, and pointers in."
+
+# Every folder at the root, one entry each, with its type: collection | assets | other.
+folders:
+  # The framing docs: what every other blueprint is judged against. One left unwritten is a gap to surface,
+  # not a failure.
+  - name: Frames
+    type: collection
+    description: "What every chapter is judged against: what the book argues, who it is for, how it sounds, and where it sits."
+    variants:
+      - { name: premise, template: templates/frame.premise.md, description: "what the book says, and why it has to exist", default: true }
+      - { name: reader, template: templates/frame.reader.md, description: "who it is for, and what changes for them" }
+      - { name: voice, template: templates/frame.voice.md, description: "person, tense, register, and the rules the prose keeps" }
+      - { name: market, template: templates/frame.market.md, description: "shelf, comparables, and how it reaches readers" }
+  - name: Chapters
+    type: collection
+    description: "The book's units, one per chapter, grouped by part."
+    variants:
+      - { name: full, template: templates/chapter.full.md, description: "the complete chapter template", default: true }
+      - { name: sketch, template: templates/chapter.sketch.md, description: "Intent, Open Questions, What Happens, Out of Scope; grow into full" }
+    grouping:
+      label: Parts
+      property: part
+      groups: []              # one entry per part, a name and a description, as they accrue
+  - name: assets
+    type: assets
+    description: "Images, diagrams, and documents the blueprints link to."
+
+# The property contract, one block per owner. A property applies to `all` collections or a list; a required
+# one is generated into every new blueprint and surfaced when missing; `options` closes the value to a set.
+properties:
+  # The standard's. migrate rewrites this block; don't hand-edit it.
+  core:
+    - { name: id, type: Text, required: true, meaning: "Stable, unique identity, in any form. Assigned once, never changed." }
+    - { name: title, type: Text, required: true, meaning: "Human-readable name." }
+    - { name: summary, type: Text, meaning: "One line: what this blueprint is. Feeds the index; absent, the index flags it." }
+    - { name: variant, type: Text, meaning: "Which variant this blueprint follows. Absent = the collection's default." }
+  # Yours. The seed ships defaults; keep, scope, or drop any of them. Only the grouping is required.
+  custom:
+    - { name: status, type: Text, applies_to: all, options: [Draft, Outlined, Drafted, Revised, Final, Cut], meaning: "Lifecycle stage." }
+    - { name: date_created, type: Date, applies_to: all, meaning: "YYYY-MM-DD. Set once." }
+    - { name: date_modified, type: Date, applies_to: all, meaning: "YYYY-MM-DD. The last change." }
+    - { name: tags, type: List, applies_to: all, meaning: "Free tags." }
+    - { name: part, type: Text, required: true, applies_to: [Chapters], meaning: "The group: matches the blueprint's sub-folder. An unknown value warns." }
+    - { name: depends_on, type: List, applies_to: [Chapters], meaning: "Chapters a reader must have read first, each a markdown link." }
+
+# The root's own terms: term, means, not (the near-misses and why), and see (the blueprint that defines it).
+# Starts empty; Eidos declares none.
+vocabulary: []

package/standard/seeds/book/README.md

@@ -7,11 +7,16 @@
 
 ## Where things are
 
-- **[Frames](Frames/index.md)** — what the book argues, who reads it, how it sounds, where it sits.
-- **[Chapters](Chapters/index.md)** — one file per chapter, grouped by part.
+- **[Frames](Frames/)** — what the book argues, who reads it, how it sounds, where it sits.
+- **[Chapters](Chapters/)** — one file per chapter, grouped by part.
+- **[assets](assets/)** — images, diagrams, and documents the blueprints link to.
 
-The full index — every collection, its flavors, and the property Schema — is in
-[`_eidos/Framework.md`](_eidos/Framework.md).
+## Top-level documents
+
+_Your own one-of-a-kind docs: an Outline of the whole book, a Style Sheet (spellings, names, hyphenation), a Bibliography. Add them here as you write them._
+
+The full index — every folder, its variants, and the Properties table — is in
+[`.eidos/Framework.yaml`](.eidos/Framework.yaml).
 
 ## How to use it
 
@@ -19,4 +24,4 @@ A chapter here describes what the chapter **is**: why it exists, what happens in
 reader leaves with. It is not a draft and not a task. Write the chapter's blueprint before the prose,
 and keep it true after — a chapter you cut stays here, marked `Cut`, so the reasoning survives.
 
-_A root. Its framework lives in [`_eidos/`](_eidos/); see [`_eidos/Framework.md`](_eidos/Framework.md) for the full index._
+_A root. Its framework lives in [`.eidos/`](.eidos/); see [`.eidos/Framework.yaml`](.eidos/Framework.yaml) for the full index._

package/standard/seeds/book/_gitignore

@@ -1,4 +1,10 @@
-# Eidos: the per-actor file is personal and never shared.
-# Each person who works on this definition keeps their own me.md (here in _eidos/); the agent reads
-# it to know who they are. It is the one _eidos/ file that is not checked in.
+# Eidos: me.md is personal and never shared.
+# Each person who works on this definition keeps their own me.md (here in .eidos/); the agent reads
+# it to know who they are. It is the one file of the standard's own that is not checked in.
 me.md
+
+# Eidos: a tool's local.yaml is personal and never shared.
+# A tool that keeps a folder under plugins/ may keep its personal settings there, one machine's (a
+# viewer command, an editor, a key path); everything else in its folder is the root's. This one
+# line covers every tool, so no tool writes a .gitignore of its own.
+plugins/*/local.yaml

package/standard/seeds/book/me.md

@@ -4,7 +4,7 @@ Who is in the seat. This file is **personal and per-actor** — it is gitignored
 each person who works on this folder keeps their own. The agent reads it before acting, to know who
 you are and how to help.
 
-Set who you are below — `install` asks, or just edit this file. Leaving it blank is fine: the agent
+Set who you are below — `eidos whoami` asks, or just edit this file. Leaving it blank is fine: the agent
 defaults to full, framework-owner-style facilitation and offers to record who you are.
 
 ## You are:

package/standard/seeds/book/roles/README.md

@@ -1,12 +1,12 @@
 # Roles
 
-Default **roles** for this framework — who is in the seat, and how the agent should respond to them. A role is a **response contract**: it sets the vocabulary, the level of technical depth, what to surface vs. fold away, and who holds which decisions. The agent reads it **before acting** (see the Eidos standard's `EIDOS.md`, "The actor").
+Default **roles** for this framework — who is in the seat, and how the agent should respond to them. A role is a **response contract**: it sets the vocabulary, the level of technical depth, what to surface vs. fold away, and who holds which decisions. The agent reads it **before acting** (see the Eidos standard's `EIDOS.md`, "Roles").
 
-These are the book seed's baseline, browsable here and installed into a root's `_eidos/roles/` by `install` (committed, so a team can tune how a role is treated for their book). Each person who works on the folder picks one in their personal, gitignored `_eidos/me.md` and **calibrates** it — what they own on this folder, their experience with the scope, and their technical capacity — with the `whoami` skill. Role sets the baseline; calibration tunes it per person.
+These are the book seed's baseline, browsable here and installed into a root's `.eidos/roles/` by `eidos init` (committed, so a team can tune how a role is treated for their book). Each person who works on the folder picks one in their personal, gitignored `.eidos/me.md` and **calibrates** it — what they own on this folder, their experience with the scope, and their technical capacity — with `eidos whoami`. Role sets the baseline; calibration tunes it per person.
 
 - [Framework Owner](framework-owner.md) — holds intent, scope, and decisions.
 - [Editor](editor.md) — reads for structure and what the book promises.
 - [Collaborator](collaborator.md) — drafts alongside the owner.
 - [Reader](reader.md) — reacts to the book, doesn't build it.
 
-A role is a baseline, not a cage: an actor can write a custom role in their `me.md`, and a framework can add or reshape role files here. The human-first principle holds for every role — the human authors and decides; the role only changes _how_ the agent helps.
+A role is a baseline, not a cage: anyone can write a custom role in their `me.md`, and a framework can add or reshape role files here. The human-first principle holds for every role — the human authors and decides; the role only changes _how_ the agent helps.

package/standard/seeds/book/roles/framework-owner.md

@@ -2,11 +2,11 @@
 
 ## Who they are
 
-Holds the **intent, scope, and decisions** — true ownership of whatever it defines, be it a product, a body of research, a methodology, or any other form of thought or effort. The person Eidos is built for — they think through what the thing is, and they own the calls. Everything else serves their clarity.
+Holds the **intent, scope, and decisions** — true ownership of the product, whatever kind it is: an app, a body of research, a methodology, any other form of thought or effort. The person Eidos is built for — they think through what the product is, and they own the calls. Everything else serves their clarity.
 
 ## How to respond
 
-- **Vocabulary & depth:** lead with the terms of the thing itself and the decision at hand. But many Framework Owners are also technical — don't assume otherwise; follow their **technical capacity** calibration and go as deep as they want, rather than withholding mechanism by default.
+- **Vocabulary & depth:** lead with the product's own terms and the decision at hand. But many Framework Owners are also technical — don't assume otherwise; follow their **technical capacity** calibration and go as deep as they want, rather than withholding mechanism by default.
 - **Decisions:** theirs. Bring choices and trade-offs for them to decide; never decide direction or resolve an Open Question on their behalf. Press hardest on **Out of Scope**.
 - **Surface / hide:** surface intent, scope, audience, criteria, and the consequences of a choice; fold mechanism into a link they can follow.
 - **Focus:** Intent, Out of Scope, the Premise and Reader frames, and whether each chapter still says what they mean.

package/standard/seeds/book/{shapes → templates}/chapter.full.md

@@ -1,11 +1,3 @@
-<!--
-The Chapter shape — the body of a chapter, and the documentation of each section. A chapter's
-frontmatter is generated from the framework's Schema (in Framework.md), so it is not written here.
-Keep the sections that apply and delete the rest, but leave the order and headings as they are — a
-reader should know what to expect from any chapter in this folder. The italic prompts are
-guidance; delete them as you fill each section in.
--->
-
 # {{title}}
 
 ## Intent

package/standard/seeds/book/{shapes → templates}/chapter.sketch.md

@@ -1,10 +1,3 @@
-<!--
-The Chapter shape, sketch flavor — the smallest useful chapter blueprint, meant to grow into
-`chapter.full` once it earns it. A chapter's frontmatter is generated from the framework's Schema (in
-Framework.md), so it is not written here. Keep the order and headings as they are; delete the italic
-prompts as you fill each section in.
--->
-
 # {{title}}
 
 ## Intent

package/standard/seeds/book/{shapes → templates}/frame.market.md

@@ -1,9 +1,3 @@
-<!--
-The Market frame — where this book sits and how it reaches readers. Loose, point-in-time prose.
-Suggestive, not prescriptive. A Frame's frontmatter is generated from the framework's Schema (in
-Framework.md), so it is not written here. Delete the italic prompts as you fill in.
--->
-
 # Market
 
 ## The Shelf

package/standard/seeds/book/templates/frame.premise.md

@@ -0,0 +1,17 @@
+# Premise
+
+## The Argument
+
+_In a few sentences: what this book claims, or what story it tells. If you can't say it without a list, it isn't a premise yet._
+
+## Why It Has To Exist
+
+_What is wrong, missing, or misunderstood in the world without this book. The problem the reader has._
+
+## The Shape of It
+
+_How the whole book is built — parts, arc, the movement from the first page to the last. Not a table of contents; the logic behind one._
+
+## What It Is Not
+
+_The adjacent book you are deliberately not writing. This is where a book's scope is held._

package/standard/seeds/book/{shapes → templates}/frame.reader.md

@@ -1,9 +1,3 @@
-<!--
-The Reader frame — who this book is for, and what changes for them. Loose, point-in-time prose.
-Suggestive, not prescriptive. A Frame's frontmatter is generated from the framework's Schema (in
-Framework.md), so it is not written here. Delete the italic prompts as you fill in.
--->
-
 # Reader
 
 ## Who They Are

package/standard/seeds/book/{shapes → templates}/frame.voice.md

@@ -1,10 +1,3 @@
-<!--
-The Voice frame — the rules the prose keeps, so any chapter sounds like the same book. Loose,
-point-in-time prose. Suggestive, not prescriptive. A Frame's frontmatter is generated from the
-framework's Schema (in Framework.md), so it is not written here. Delete the italic prompts as you
-fill in.
--->
-
 # Voice
 
 ## Person & Tense

package/standard/seeds/research/Framework.yaml

@@ -0,0 +1,61 @@
+# The framework document: the structure this root is written in. See EIDOS.md for what each key means;
+# the `eidos` CLI edits this file. Every path is relative to this folder.
+
+eidos_version: 5.3.0
+
+# kebab-case | TitleCase | Title Case. Settled at install; changing it later means renaming files.
+naming: kebab-case
+
+# Every file at the root, one entry each.
+top_level:
+  - title: README
+    path: ../README.md
+    description: "the root's front door: what this programme asks, and pointers in."
+
+# Every folder at the root, one entry each, with its type: collection | assets | other.
+folders:
+  # The framing docs: what every other blueprint is judged against. One left unwritten is a gap to surface,
+  # not a failure.
+  - name: Frames
+    type: collection
+    description: "What every investigation is judged against: what is asked, what is known, what would count as knowing, and who is affected."
+    variants:
+      - { name: question, template: templates/frame.question.md, description: "what the programme asks, and why it matters", default: true }
+      - { name: "prior work", template: templates/frame.prior-work.md, description: "what is already known, and where this sits" }
+      - { name: method, template: templates/frame.method.md, description: "how anyone would know, and the standard of evidence" }
+      - { name: ethics, template: templates/frame.ethics.md, description: "who is affected, what they consented to, what could go wrong" }
+  - name: Investigations
+    type: collection
+    description: "The programme's units, one per line of inquiry, grouped by strand."
+    variants:
+      - { name: full, template: templates/investigation.full.md, description: "the complete investigation template", default: true }
+      - { name: note, template: templates/investigation.note.md, description: "Intent, Open Questions, Claims, Out of Scope; grow into full" }
+    grouping:
+      label: Strands
+      property: strand
+      groups: []              # one entry per strand, a name and a description, as they accrue
+  - name: assets
+    type: assets
+    description: "Images, diagrams, and documents the blueprints link to."
+
+# The property contract, one block per owner. A property applies to `all` collections or a list; a required
+# one is generated into every new blueprint and surfaced when missing; `options` closes the value to a set.
+properties:
+  # The standard's. migrate rewrites this block; don't hand-edit it.
+  core:
+    - { name: id, type: Text, required: true, meaning: "Stable, unique identity, in any form. Assigned once, never changed." }
+    - { name: title, type: Text, required: true, meaning: "Human-readable name." }
+    - { name: summary, type: Text, meaning: "One line: what this blueprint is. Feeds the index; absent, the index flags it." }
+    - { name: variant, type: Text, meaning: "Which variant this blueprint follows. Absent = the collection's default." }
+  # Yours. The seed ships defaults; keep, scope, or drop any of them. Only the grouping is required.
+  custom:
+    - { name: status, type: Text, applies_to: all, options: [Draft, Open, Running, Answered, Inconclusive, Abandoned], meaning: "Lifecycle stage." }
+    - { name: date_created, type: Date, applies_to: all, meaning: "YYYY-MM-DD. Set once." }
+    - { name: date_modified, type: Date, applies_to: all, meaning: "YYYY-MM-DD. The last change." }
+    - { name: tags, type: List, applies_to: all, meaning: "Free tags." }
+    - { name: strand, type: Text, required: true, applies_to: [Investigations], meaning: "The group: matches the blueprint's sub-folder. An unknown value warns." }
+    - { name: depends_on, type: List, applies_to: [Investigations], meaning: "Investigations, data, or approvals this one needs first, each a markdown link." }
+
+# The root's own terms: term, means, not (the near-misses and why), and see (the blueprint that defines it).
+# Starts empty; Eidos declares none.
+vocabulary: []

package/standard/seeds/research/README.md

@@ -7,11 +7,16 @@
 
 ## Where things are
 
-- **[Frames](Frames/index.md)** — the question, the prior work, the method, the ethics.
-- **[Investigations](Investigations/index.md)** — one file per line of inquiry, grouped by strand.
+- **[Frames](Frames/)** — the question, the prior work, the method, the ethics.
+- **[Investigations](Investigations/)** — one file per line of inquiry, grouped by strand.
+- **[assets](assets/)** — images, diagrams, and documents the blueprints link to.
 
-The full index — every collection, its flavors, and the property Schema — is in
-[`_eidos/Framework.md`](_eidos/Framework.md).
+## Top-level documents
+
+_Your own one-of-a-kind docs: a Pre-registration, a Data Management Plan, a Bibliography. Add them here as you write them._
+
+The full index — every folder, its variants, and the Properties table — is in
+[`.eidos/Framework.yaml`](.eidos/Framework.yaml).
 
 ## How to use it
 
@@ -20,4 +25,4 @@ notebook, a protocol, or a task list. Write the question and the falsifier befor
 them true after — an investigation that comes back `Inconclusive` or `Abandoned` stays here, because
 the question and the attempt are both part of what the programme knows.
 
-_A root. Its framework lives in [`_eidos/`](_eidos/); see [`_eidos/Framework.md`](_eidos/Framework.md) for the full index._
+_A root. Its framework lives in [`.eidos/`](.eidos/); see [`.eidos/Framework.yaml`](.eidos/Framework.yaml) for the full index._

package/standard/seeds/research/_gitignore

@@ -1,4 +1,10 @@
-# Eidos: the per-actor file is personal and never shared.
-# Each person who works on this definition keeps their own me.md (here in _eidos/); the agent reads
-# it to know who they are. It is the one _eidos/ file that is not checked in.
+# Eidos: me.md is personal and never shared.
+# Each person who works on this definition keeps their own me.md (here in .eidos/); the agent reads
+# it to know who they are. It is the one file of the standard's own that is not checked in.
 me.md
+
+# Eidos: a tool's local.yaml is personal and never shared.
+# A tool that keeps a folder under plugins/ may keep its personal settings there, one machine's (a
+# viewer command, an editor, a key path); everything else in its folder is the root's. This one
+# line covers every tool, so no tool writes a .gitignore of its own.
+plugins/*/local.yaml

package/standard/seeds/research/me.md

@@ -4,7 +4,7 @@ Who is in the seat. This file is **personal and per-actor** — it is gitignored
 each person who works on this folder keeps their own. The agent reads it before acting, to know who
 you are and how to help.
 
-Set who you are below — `install` asks, or just edit this file. Leaving it blank is fine: the agent
+Set who you are below — `eidos whoami` asks, or just edit this file. Leaving it blank is fine: the agent
 defaults to full, framework-owner-style facilitation and offers to record who you are.
 
 ## You are:

package/standard/seeds/research/roles/README.md

@@ -1,12 +1,12 @@
 # Roles
 
-Default **roles** for this framework — who is in the seat, and how the agent should respond to them. A role is a **response contract**: it sets the vocabulary, the level of technical depth, what to surface vs. fold away, and who holds which decisions. The agent reads it **before acting** (see the Eidos standard's `EIDOS.md`, "The actor").
+Default **roles** for this framework — who is in the seat, and how the agent should respond to them. A role is a **response contract**: it sets the vocabulary, the level of technical depth, what to surface vs. fold away, and who holds which decisions. The agent reads it **before acting** (see the Eidos standard's `EIDOS.md`, "Roles").
 
-These are the research seed's baseline, browsable here and installed into a root's `_eidos/roles/` by `install` (committed, so a team can tune how a role is treated for their programme). Each person who works on the folder picks one in their personal, gitignored `_eidos/me.md` and **calibrates** it — what they own on this folder, their experience with the scope, and their technical capacity — with the `whoami` skill. Role sets the baseline; calibration tunes it per person.
+These are the research seed's baseline, browsable here and installed into a root's `.eidos/roles/` by `eidos init` (committed, so a team can tune how a role is treated for their programme). Each person who works on the folder picks one in their personal, gitignored `.eidos/me.md` and **calibrates** it — what they own on this folder, their experience with the scope, and their technical capacity — with `eidos whoami`. Role sets the baseline; calibration tunes it per person.
 
 - [Framework Owner](framework-owner.md) — holds intent, scope, and decisions.
 - [Researcher](researcher.md) — does the work; needs the design in full.
 - [Reviewer](reviewer.md) — reads to find the hole; adversarial by design.
 - [Sponsor](sponsor.md) — funds or answers for it; needs what it can and cannot conclude.
 
-A role is a baseline, not a cage: an actor can write a custom role in their `me.md`, and a framework can add or reshape role files here. The human-first principle holds for every role — the human authors and decides; the role only changes _how_ the agent helps.
+A role is a baseline, not a cage: anyone can write a custom role in their `me.md`, and a framework can add or reshape role files here. The human-first principle holds for every role — the human authors and decides; the role only changes _how_ the agent helps.

package/standard/seeds/research/roles/framework-owner.md

@@ -2,11 +2,11 @@
 
 ## Who they are
 
-Holds the **intent, scope, and decisions** — true ownership of whatever it defines, be it a product, a body of research, a methodology, or any other form of thought or effort. The person Eidos is built for — they think through what the thing is, and they own the calls. Everything else serves their clarity.
+Holds the **intent, scope, and decisions** — true ownership of the product, whatever kind it is: an app, a body of research, a methodology, any other form of thought or effort. The person Eidos is built for — they think through what the product is, and they own the calls. Everything else serves their clarity.
 
 ## How to respond
 
-- **Vocabulary & depth:** lead with the terms of the thing itself and the decision at hand. But many Framework Owners are also technical — don't assume otherwise; follow their **technical capacity** calibration and go as deep as they want, rather than withholding mechanism by default.
+- **Vocabulary & depth:** lead with the product's own terms and the decision at hand. But many Framework Owners are also technical — don't assume otherwise; follow their **technical capacity** calibration and go as deep as they want, rather than withholding mechanism by default.
 - **Decisions:** theirs. Bring choices and trade-offs for them to decide; never decide direction or resolve an Open Question on their behalf. Press hardest on **Out of Scope**.
 - **Surface / hide:** surface intent, scope, audience, criteria, and the consequences of a choice; fold mechanism into a link they can follow.
 - **Focus:** Intent, Out of Scope, the Question and Method frames, and whether each investigation still says what they mean.

package/standard/seeds/research/{shapes → templates}/frame.ethics.md

@@ -1,9 +1,3 @@
-<!--
-The Ethics frame — who is affected and what you owe them. Loose, point-in-time prose. Suggestive, not
-prescriptive. A Frame's frontmatter is generated from the framework's Schema (in Framework.md), so it
-is not written here. Delete the italic prompts as you fill in.
--->
-
 # Ethics
 
 ## Who Is Affected

package/standard/seeds/research/{shapes → templates}/frame.method.md

@@ -1,10 +1,3 @@
-<!--
-The Method frame — how anyone would know, and the standard of evidence this programme holds. Loose,
-point-in-time prose. Suggestive, not prescriptive. A Frame's frontmatter is generated from the
-framework's Schema (in Framework.md), so it is not written here. Delete the italic prompts as you
-fill in.
--->
-
 # Method
 
 ## Approach

package/standard/seeds/research/{shapes → templates}/frame.prior-work.md

@@ -1,9 +1,3 @@
-<!--
-The Prior Work frame — what is already known, and where this sits against it. Loose, point-in-time
-prose. Suggestive, not prescriptive. A Frame's frontmatter is generated from the framework's Schema
-(in Framework.md), so it is not written here. Delete the italic prompts as you fill in.
--->
-
 # Prior Work
 
 ## What Is Settled

package/standard/seeds/research/{shapes → templates}/frame.question.md

@@ -1,10 +1,3 @@
-<!--
-The Question frame — what this programme asks and why it matters. Loose, point-in-time prose: record
-what is true now and revise when it changes. Suggestive, not prescriptive. A Frame's frontmatter is
-generated from the framework's Schema (in Framework.md), so it is not written here. Delete the italic
-prompts as you fill in.
--->
-
 # Question
 
 ## The Question

package/standard/seeds/research/{shapes → templates}/investigation.full.md

@@ -1,11 +1,3 @@
-<!--
-The Investigation shape — the body of one line of inquiry, and the documentation of each section. An
-investigation's frontmatter is generated from the framework's Schema (in Framework.md), so it is not
-written here. Keep the sections that apply and delete the rest, but leave the order and headings as
-they are — a reader should know what to expect from any investigation in this folder. The italic
-prompts are guidance; delete them as you fill each section in.
--->
-
 # {{title}}
 
 ## Intent

package/standard/seeds/research/{shapes → templates}/investigation.note.md

@@ -1,10 +1,3 @@
-<!--
-The Investigation shape, note flavor — the smallest useful record of a line of inquiry, meant to grow
-into `investigation.full` once it earns it. Frontmatter is generated from the framework's Schema (in
-Framework.md), so it is not written here. Keep the order and headings as they are; delete the italic
-prompts as you fill each section in.
--->
-
 # {{title}}
 
 ## Intent

package/standard/seeds/software/Framework.yaml

@@ -0,0 +1,62 @@
+# The framework document: the structure this root is written in. See EIDOS.md for what each key means;
+# the `eidos` CLI edits this file. Every path is relative to this folder.
+
+eidos_version: 5.3.0
+
+# kebab-case | TitleCase | Title Case. Settled at install; changing it later means renaming files.
+naming: kebab-case
+
+# Every file at the root, one entry each.
+top_level:
+  - title: README
+    path: ../README.md
+    description: "the root's front door: what this is, and pointers in."
+
+# Every folder at the root, one entry each, with its type: collection | assets | other.
+folders:
+  # The framing docs: what every other blueprint is judged against. One left unwritten is a gap to surface,
+  # not a failure.
+  - name: Frames
+    type: collection
+    description: "What every other blueprint is judged against: the product's architecture, audience, criteria, and market."
+    variants:
+      - { name: architecture, template: templates/frame.architecture.md, description: "the product as a built system", default: true }
+      - { name: audience, template: templates/frame.audience.md, description: "who it serves, and how each kind differs" }
+      - { name: criteria, template: templates/frame.criteria.md, description: "budget, scope objectives, timeline" }
+      - { name: market, template: templates/frame.market.md, description: "landscape, positioning, and how it earns" }
+  - name: Specs
+    type: collection
+    description: "The product's units, one per blueprint, grouped by domain."
+    variants:
+      - { name: full, template: templates/spec.full.md, description: "the complete spec template", default: true }
+      - { name: micro, template: templates/spec.micro.md, description: "Intent, Open Questions, ACs, Out of Scope; grow into full" }
+    grouping:
+      label: Domains
+      property: domain
+      groups: []              # one entry per domain, a name and a description, as they accrue
+  - name: assets
+    type: assets
+    description: "Images, diagrams, and documents the blueprints link to."
+
+# The property contract, one block per owner. A property applies to `all` collections or a list; a required
+# one is generated into every new blueprint and surfaced when missing; `options` closes the value to a set.
+properties:
+  # The standard's. migrate rewrites this block; don't hand-edit it.
+  core:
+    - { name: id, type: Text, required: true, meaning: "Stable, unique identity, in any form. Assigned once, never changed." }
+    - { name: title, type: Text, required: true, meaning: "Human-readable name." }
+    - { name: summary, type: Text, meaning: "One line: what this blueprint is. Feeds the index; absent, the index flags it." }
+    - { name: variant, type: Text, meaning: "Which variant this blueprint follows. Absent = the collection's default." }
+  # Yours. The seed ships defaults; keep, scope, or drop any of them. Only the grouping is required.
+  custom:
+    - { name: status, type: Text, applies_to: all, options: [Draft, Intake, In Progress, Done, Archived, Deprecated], meaning: "Lifecycle stage." }
+    - { name: date_created, type: Date, applies_to: all, meaning: "YYYY-MM-DD. Set once." }
+    - { name: date_modified, type: Date, applies_to: all, meaning: "YYYY-MM-DD. The last change." }
+    - { name: tags, type: List, applies_to: all, meaning: "Free tags." }
+    - { name: domain, type: Text, required: true, applies_to: [Specs], meaning: "The group: matches the blueprint's sub-folder. An unknown value warns." }
+    - { name: depends_on, type: List, applies_to: [Specs], meaning: "Blueprints this one needs, each a markdown link." }
+    - { name: type, type: Text, applies_to: [Specs], meaning: "Soft category label: drives views and filtering, never structure. e.g. feature, capability, integration." }
+
+# The root's own terms: term, means, not (the near-misses and why), and see (the blueprint that defines it).
+# Starts empty; Eidos declares none.
+vocabulary: []

package/standard/seeds/software/README.md

@@ -4,7 +4,7 @@
 > product is, true whether or not it's been built.
 
 This README is the front door. The full index and config live in
-[`_eidos/Framework.md`](_eidos/Framework.md); this file orients you and points the way.
+[`.eidos/Framework.yaml`](.eidos/Framework.yaml); this file orients you and points the way.
 
 ## What this is
 
@@ -12,13 +12,14 @@ _One or two sentences: what {{Product}} is, and for whom._
 
 ## Top-level documents
 
-_Your own one-of-a-kind docs (a Roadmap, a Vision, the generated Blueprint Map). Add them here as you write them._
+_Your own one-of-a-kind docs: a Vision, a set of Design Principles, the generated Blueprint Map. Add them here as you write them._
 
-## Collections
+## Folders
 
-- **[Frames](Frames/index.md)** — the framing docs: Architecture, Audience, Criteria, Market.
-- **[Specs](Specs/index.md)** — the product's units, grouped by domain.
+- **[Frames](Frames/)** — the framing docs: Architecture, Audience, Criteria, Market.
+- **[Specs](Specs/)** — the product's units, grouped by domain.
+- **[assets](assets/)** — images, diagrams, and documents the blueprints link to.
 
 ---
 
-_A root. Its framework lives in [`_eidos/`](_eidos/); see [`_eidos/Framework.md`](_eidos/Framework.md) for the full index. `configure` and `index` keep these current._
+_A root. Its framework lives in [`.eidos/`](.eidos/); see [`.eidos/Framework.yaml`](.eidos/Framework.yaml) for the full index. `eidos index` keeps the index current._

package/standard/seeds/software/_gitignore

@@ -1,4 +1,10 @@
-# Eidos: the per-actor file is personal and never shared.
-# Each person who works on this definition keeps their own me.md (here in _eidos/); the agent reads
-# it to know who they are. It is the one _eidos/ file that is not checked in.
+# Eidos: me.md is personal and never shared.
+# Each person who works on this definition keeps their own me.md (here in .eidos/); the agent reads
+# it to know who they are. It is the one file of the standard's own that is not checked in.
 me.md
+
+# Eidos: a tool's local.yaml is personal and never shared.
+# A tool that keeps a folder under plugins/ may keep its personal settings there, one machine's (a
+# viewer command, an editor, a key path); everything else in its folder is the root's. This one
+# line covers every tool, so no tool writes a .gitignore of its own.
+plugins/*/local.yaml

package/standard/seeds/software/me.md

@@ -4,7 +4,7 @@ Who is in the seat. This file is **personal and per-actor** — it is gitignored
 each person who works on this folder keeps their own. The agent reads it before acting, to know who
 you are and how to help.
 
-Set who you are below — `install` asks, or just edit this file. Leaving it blank is fine: the agent
+Set who you are below — `eidos whoami` asks, or just edit this file. Leaving it blank is fine: the agent
 defaults to full, framework-owner-style facilitation and offers to record who you are.
 
 ## You are:

package/standard/seeds/software/roles/README.md

@@ -1,8 +1,8 @@
 # Roles
 
-Default **roles** for this framework — who is in the seat, and how the agent should respond to them. A role is a **response contract**: it sets the vocabulary, the level of technical depth, what to surface vs. fold away, and who holds which decisions. The agent reads it **before acting** (see the Eidos standard's `EIDOS.md`, "The actor").
+Default **roles** for this framework — who is in the seat, and how the agent should respond to them. A role is a **response contract**: it sets the vocabulary, the level of technical depth, what to surface vs. fold away, and who holds which decisions. The agent reads it **before acting** (see the Eidos standard's `EIDOS.md`, "Roles").
 
-These are the opinionated baseline, browsable here and installed into a root's `_eidos/roles/` by `install` (committed, so a team can tune how a role is treated for their product). Each person who works on the folder picks one in their personal, gitignored `_eidos/me.md` and **calibrates** it — what they own on this folder, their experience with the scope, and their technical capacity — with the `whoami` skill. Role sets the baseline; calibration tunes it per person.
+These are the opinionated baseline, browsable here and installed into a root's `.eidos/roles/` by `eidos init` (committed, so a team can tune how a role is treated for their product). Each person who works on the folder picks one in their personal, gitignored `.eidos/me.md` and **calibrates** it — what they own on this folder, their experience with the scope, and their technical capacity — with `eidos whoami`. Role sets the baseline; calibration tunes it per person.
 
 - [Framework Owner](framework-owner.md) — holds intent, scope, and decisions.
 - [Developer](developer.md) — builds from the blueprints.
@@ -10,4 +10,4 @@ These are the opinionated baseline, browsable here and installed into a root's `
 - [Designer](designer.md) — shapes the experience.
 - [Project Manager](project-manager.md) — tracks scope and progress.
 
-A role is a baseline, not a cage: an actor can write a custom role in their `me.md`, and a framework can add or reshape role files here. The human-first principle holds for every role — the human authors and decides; the role only changes _how_ the agent helps.
+A role is a baseline, not a cage: anyone can write a custom role in their `me.md`, and a framework can add or reshape role files here. The human-first principle holds for every role — the human authors and decides; the role only changes _how_ the agent helps.

package/standard/seeds/software/roles/framework-owner.md

@@ -2,11 +2,11 @@
 
 ## Who they are
 
-Holds the **intent, scope, and decisions** — true ownership of whatever it defines, be it a product, a body of research, a methodology, or any other form of thought or effort. The person Eidos is built for — they think through what the thing is, and they own the calls. Everything else serves their clarity.
+Holds the **intent, scope, and decisions** — true ownership of the product, whatever kind it is: an app, a body of research, a methodology, any other form of thought or effort. The person Eidos is built for — they think through what the product is, and they own the calls. Everything else serves their clarity.
 
 ## How to respond
 
-- **Vocabulary & depth:** lead with the terms of the thing itself and the decision at hand. But many Framework Owners are also technical — don't assume otherwise; follow their **technical capacity** calibration and go as deep as they want, rather than withholding mechanism by default.
+- **Vocabulary & depth:** lead with the product's own terms and the decision at hand. But many Framework Owners are also technical — don't assume otherwise; follow their **technical capacity** calibration and go as deep as they want, rather than withholding mechanism by default.
 - **Decisions:** theirs. Bring choices and trade-offs for them to decide; never decide direction or resolve an Open Question on their behalf. Press hardest on **Out of Scope**.
 - **Surface / hide:** surface intent, scope, audience, criteria, and the consequences of a choice; fold mechanism into a link they can follow.
 - **Focus:** Intent, Out of Scope, Audience, Criteria, and whether each blueprint still says what they mean.

package/standard/seeds/software/roles/project-manager.md

@@ -11,8 +11,8 @@ Tracks **scope and progress**, not product direction or implementation. Wants to
 - **Surface / hide:** surface **Out of Scope** (the in/out line), each unit's `status` (its lifecycle stage), `depends_on` and other dependencies, and the Decisions log with the `created`/`modified` dates that show movement. Fold away mechanism and prose rationale.
 - **Focus:** what's in vs. out, what stage each unit is at, what blocks what, and where scope is drifting from Criteria.
 
-Remember Eidos captures **state and intent, not work** — there are no sprint, estimate, or assignee fields, on purpose. So for this actor: read **progress** from `status` and git history (the Decisions log, `created`/`modified`), not a burn-down; infer **level of effort** from a unit's shape — its acceptance criteria, dependencies, and open questions — not a stored estimate; and for sprint-level tracking, point to the tracker a unit links to rather than adding work fields to a blueprint.
+Remember Eidos captures **state and intent, not work** — there are no sprint, estimate, or assignee fields, on purpose. So for this role: read **progress** from `status` and git history (the Decisions log, `created`/`modified`), not a burn-down; infer **level of effort** from a unit's shape — its acceptance criteria, dependencies, and open questions — not a stored estimate; and for sprint-level tracking, point to the tracker a unit links to rather than adding work fields to a blueprint.
 
 ## Calibration
 
-Usually moderate **technical capacity**, and broad-but-shallow **experience with the scope** — they span the whole thing rather than living in one unit. Lean on `status`, dependencies, and the in/out line.
+Usually moderate **technical capacity**, and broad-but-shallow **experience with the scope** — they span the whole product rather than living in one unit. Lean on `status`, dependencies, and the in/out line.