eidosmd 0.1.0

package/standard/seeds/book/shapes/chapter.sketch.md

@@ -0,0 +1,26 @@
+<!--
+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
+
+_Why this chapter exists — the work it does that no other chapter does. A paragraph is plenty here._
+
+## Open Questions
+
+_What you don't yet know about this chapter. Honest holes beat invented certainty._
+
+## What Happens
+
+_The beats, in order, as far as you have them. Label each **B1:**, **B2:**, … Rough is fine; a sketch is allowed to be thin, but not vague._
+
+- **B1:**
+
+## Out of Scope
+
+_What this chapter deliberately does not cover, and which chapter covers it instead. Even in a sketch, this is the section worth filling — it's what keeps neighboring chapters from eating each other._

package/standard/seeds/book/shapes/frame.market.md

@@ -0,0 +1,23 @@
+<!--
+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
+
+_Where it sits in a shop or a store's category tree, and who it sits beside._
+
+## Comparables
+
+_Three or four books a reader would already own. For each: what it does well, and what this one does that it doesn't._
+
+## How It Reaches Readers
+
+_Publisher, self-published, serialized, a course, a newsletter first. The path from written to read._
+
+## What Success Looks Like
+
+_Copies, readers, citations, invitations, a changed mind. Say which, and roughly how much — a book with no stated bar can't be finished._

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

@@ -0,0 +1,24 @@
+<!--
+The Premise frame — what the book says and why it has to exist. 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.
+-->
+
+# 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 thing 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/frame.reader.md

@@ -0,0 +1,23 @@
+<!--
+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
+
+_The specific person you are writing to. One or a few kinds; name them. "Everyone" is not a reader._
+
+## What They Bring
+
+_What they already know, already believe, and already tried. What vocabulary you can use without explaining it, and what you cannot._
+
+## What Changes For Them
+
+_What they can do, believe, or feel at the end that they couldn't at the start. The book's promise, stated from their side._
+
+## Who It Is Not For
+
+_The reader you will lose, and are choosing to lose. Naming them is what lets you write plainly to the ones you keep._

package/standard/seeds/book/shapes/frame.voice.md

@@ -0,0 +1,24 @@
+<!--
+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
+
+_First, second, or third; past or present. Whether it varies, and where._
+
+## Register
+
+_How it sounds read aloud — plain, formal, wry, urgent. Two or three writers or books it stands near, and how it differs from each._
+
+## Rules It Keeps
+
+_The specific, checkable habits: sentence length, jargon policy, how sources are cited, whether it addresses the reader directly, what it never does. These are what an editor checks a draft against._
+
+## Rules It Breaks, On Purpose
+
+_Where the book deliberately departs from its own register, and what that departure is for._

package/standard/seeds/research/Framework.md

@@ -0,0 +1,88 @@
+---
+# The Eidos version this framework targets; migrate reads and bumps it.
+eidos_version: 4.5.0
+# How files, folders, and links are named: kebab-case | TitleCase | Title Case. Absent = kebab-case.
+naming: kebab-case
+---
+
+# Framework
+
+The framework's index and config, in one place: the version and naming convention above, and below the
+Top-Level documents, the Collections (with their flavors and grouping), and the property Schema. The
+visible `README.md` at the root is the friendly door to it; keep it current with the
+`configure` skill.
+
+## Top-Level
+
+<!-- configure: top-level index (regenerated) -->
+- [README](../README.md) — the root's front door: what this programme asks, and pointers in.
+<!-- One bullet per top-level document. README is the door and comes first; add your own below (a
+     Protocol, a Data Statement, the generated Blueprint Map canvas), each a link and a one-line
+     description. The framing docs live in the Frames collection, not here. configure refreshes
+     this list. -->
+
+## Collections
+
+A collection is a top-level folder of repeated blueprints that share a body shape. `Frames` holds the
+framing docs — the most primary thing the folder says about itself — and `Investigations` the
+programme's units. Add more with `configure`. Each lists its flavors (the default marked), how
+it draws on the canvas, and its grouping, and points at its generated `index.md` leaf.
+
+### Frames
+
+The framing docs that set what every investigation is judged against — what is being asked, what is
+already known, what would count as knowing, and who is affected. This framework's framing collection;
+each frame follows the flavor of its kind, and one left unwritten is a gap to surface, not a failure.
+
+- **Leaf:** [Frames/index.md](../Frames/index.md)
+- **Flavors:**
+  - [question](shapes/frame.question.md) — what the programme asks, and why it matters (default).
+  - [prior work](shapes/frame.prior-work.md) — what is already known, and where this sits.
+  - [method](shapes/frame.method.md) — how anyone would know, and the standard of evidence.
+  - [ethics](shapes/frame.ethics.md) — who is affected, what they consented to, what could go wrong.
+- **Canvas:** file
+
+### Investigations
+
+The programme's units, one per line of inquiry, grouped by strand.
+
+- **Leaf:** [Investigations/index.md](../Investigations/index.md)
+- **Flavors:**
+  - [full](shapes/investigation.full.md) — the complete investigation shape (default).
+  - [note](shapes/investigation.note.md) — Intent, Open Questions, Claims, Out of Scope; grow into full.
+- **Canvas:** card from `## Intent`
+- **Strands:** _(add one bullet per strand — a name and a short description — as strands accrue)_
+
+## Schema
+
+The property contract — what a blueprint's frontmatter may carry, across every collection. Two parts: the
+**core** properties Eidos's own machinery uses, and the **custom** ones you (or the seed) add. Every
+custom property declares which collections it **applies to** — `all`, or a list — so a property never
+lands where it makes no sense (`strand` is Investigations-only). A property's type comes from the
+Obsidian set (Text, List, Number, Checkbox, Date, Date & time), so frontmatter renders natively in an
+Obsidian vault. The `configure` skill edits this section.
+
+### Eidos Core
+
+_Present on every blueprint. Managed by the standard (Eidos 4.5.0); `migrate` rewrites this block on a version change — don't hand-edit it. (`flavor` absent = the collection's default; `connects_to` absent = no canvas edges; a missing `summary` is flagged by the index.)_
+
+| Name        | Type | Meaning                                                                                        |
+| ----------- | ---- | ---------------------------------------------------------------------------------------------- |
+| id          | Text | Stable, unique, kebab-case identity. Assigned once, never renamed. References point at it.      |
+| title       | Text | Human-readable name.                                                                           |
+| summary     | Text | One plain line — what this blueprint is, in a sentence, distilled from Intent. Source for the collection index.md listing; absent, the index flags it. |
+| flavor      | Text | Which body flavor this blueprint follows, from its collection's declared flavors. Absent = the collection's default flavor. |
+| connects_to | List | Blueprints this one connects to on the canvas, each a markdown link; drawn as a directed edge (this → target). The intentional map, distinct from depends_on. |
+
+### Custom Properties
+
+_Yours to shape with the `configure` skill. The seed ships a few useful defaults below — keep, scope, or drop any of them; Eidos doesn't depend on them. Absence where a property applies is a soft gap the validator notes, never refuses._
+
+| Name          | Type | Applies To     | Meaning                                                                                |
+| ------------- | ---- | -------------- | -------------------------------------------------------------------------------------- |
+| status        | Text | all            | Lifecycle value: Draft / Open / Running / Answered / Inconclusive / Abandoned. An off-list value warns. |
+| date_created  | Date | all            | YYYY-MM-DD. The day the blueprint was first written. Set once.                               |
+| date_modified | Date | all            | YYYY-MM-DD. The day the blueprint was last changed.                                          |
+| tags          | List | all            | Free tags.                                                                              |
+| strand        | Text | Investigations | The grouping — the line of inquiry this belongs to, matching the blueprint's sub-folder in the naming convention. An unknown value warns, never fails. |
+| depends_on    | List | Investigations | Investigations, data, or approvals this one needs first, each a markdown link. A real dependency, not a canvas edge. |

package/standard/seeds/research/README.md

@@ -0,0 +1,23 @@
+# {{Product}}
+
+> **Start here.** This is the root for **{{Product}}** — the source of truth for what this
+> programme asks and what would count as an answer, true whether or not a single study has run.
+
+{{One line: the question this programme exists to answer.}}
+
+## 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.
+
+The full index — every collection, its flavors, and the property Schema — is in
+[`_eidos/Framework.md`](_eidos/Framework.md).
+
+## How to use it
+
+An investigation here describes what is being asked and what would settle it. It is not a lab
+notebook, a protocol, or a task list. Write the question and the falsifier before the work, and keep
+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._

package/standard/seeds/research/_gitignore

@@ -0,0 +1,4 @@
+# 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.
+me.md

package/standard/seeds/research/me.md

@@ -0,0 +1,18 @@
+# Me
+
+Who is in the seat. This file is **personal and per-actor** — it is gitignored and never checked in, so
+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
+defaults to full, framework-owner-style facilitation and offers to record who you are.
+
+## You are:
+
+<!-- Name your role and how you want to be helped. The base roles Eidos recognizes:
+     - Framework Owner — holds intent, scope, decisions; full authoring, press on scope.
+     - Developer — consumes specs to build; surface what's specced, clarify, flag gaps, help Testing/ACs.
+     - Stakeholder — reviews direction; explain, summarize, surface risk.
+     - Designer — shapes UX and audience; Audience, Behaviors, external interface.
+     - Project Manager — tracks scope and progress; in/out of scope, status, dependencies, effort.
+     Or write your own. -->

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

@@ -0,0 +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").
+
+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.
+
+- [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.

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

@@ -0,0 +1,16 @@
+# Framework Owner
+
+## 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.
+
+## 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.
+- **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.
+
+## Calibration
+
+Their **experience with the scope** and **technical capacity** adjust the dials above — a non-technical owner gets less jargon and more translation; a technical owner gets the mechanism without hand-holding; a deeply-experienced one gets less orientation. Determining direction is the constant; technical fluency is not assumed either way.

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

@@ -0,0 +1,16 @@
+# Researcher
+
+## Who they are
+
+Does the work. Reads an investigation to answer "what exactly am I testing, how, and what would count as a result?"
+
+## How to respond
+
+- **Vocabulary & depth:** full methodological depth — design, sampling, measures, analysis, confounds, power. Be precise, and say when something is underspecified rather than smoothing it over.
+- **Decisions:** clarify and flag, don't decide. The question, the standard of evidence, and what gets published belong to the Framework Owner; surface the gap rather than filling it.
+- **Surface / hide:** surface Method, Claims & Evidence, What Would Change Our Mind, Dependencies, and Open Questions. Fold away positioning and funding.
+- **Focus:** whether the design can actually answer the Intent; whether a claim's evidence supports it as stated; what would block the work starting.
+
+## Calibration
+
+**Experience with the scope** sets how much of the Frames to restate; **technical capacity** is high by default for this role, but honored if calibrated down.

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

@@ -0,0 +1,16 @@
+# Reviewer
+
+## Who they are
+
+Reads to find the hole. A peer reviewer, internal critic, or replication-minded colleague. Their job is to be unconvinced until the evidence earns it.
+
+## How to respond
+
+- **Vocabulary & depth:** full depth, and adversarial by default. Do not soften a weak claim; name it.
+- **Decisions:** none are theirs to make, and that is the point — they judge, they don't revise. Never resolve a flagged weakness on the owner's behalf.
+- **Surface / hide:** surface Claims & Evidence with its strength, What Would Change Our Mind, Out of Scope, Threats to Validity, and every Assumption. Lead with what is *not* supported.
+- **Focus:** claims that outrun their evidence; a falsifier that was written after the result; an Out of Scope that doesn't cover how the finding will actually be read.
+
+## Calibration
+
+**Experience with the scope** sets how much prior work to restate. Never calibrate the skepticism down — a reviewer who is easy to satisfy isn't doing the role.

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

@@ -0,0 +1,16 @@
+# Sponsor
+
+## Who they are
+
+Funds it, approves it, or answers for it. Reads to know what the programme will and will not be able to tell them, and what it costs to find out.
+
+## How to respond
+
+- **Vocabulary & depth:** plain language. Explain a method only as far as it changes what the result can support. No instrument detail, no analysis mechanics.
+- **Decisions:** bring them the decisions that are actually theirs — scope, resourcing, what gets published, what risk is acceptable. Don't bring them design choices.
+- **Surface / hide:** surface the Question, What Would Count As An Answer, Out of Scope, status across strands, and anything in Ethics that carries exposure. Fold away Method internals and Open Questions that the team will close on its own.
+- **Focus:** what this can and cannot conclude; where the programme stands; what would change the answer or the cost.
+
+## Calibration
+
+**Technical capacity** is assumed low by default and raised only if calibrated up; **experience with the scope** sets how much of the question to re-establish each time.

package/standard/seeds/research/shapes/frame.ethics.md

@@ -0,0 +1,23 @@
+<!--
+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
+
+_Participants, their communities, and the people downstream of the finding — including those who never consented to anything but will live with the result._
+
+## Consent & Governance
+
+_What participants were told, what they agreed to, and what would fall outside it. The approving body, the approval, and its limits._
+
+## Data Handling
+
+_What is collected, how it is stored, who can see it, how long it lives, and what makes it identifiable again. Say what is sensitive, plainly._
+
+## What Could Go Wrong
+
+_Foreseeable harm from doing the work, and foreseeable harm from the finding being misread or misused. What you will do about each. A programme with an empty version of this section has not looked._

package/standard/seeds/research/shapes/frame.method.md

@@ -0,0 +1,24 @@
+<!--
+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
+
+_The kind of evidence this programme produces — experimental, observational, qualitative, computational, mixed — and why that kind can answer the question._
+
+## Standard of Evidence
+
+_What you will treat as sufficient, decided in advance: effect sizes, saturation, replication, pre-registration, review. The bar, written before the results._
+
+## Threats to Validity
+
+_The ways this whole approach could mislead — selection, measurement, confounding, researcher degrees of freedom — and what you do about each._
+
+## What You Will Share
+
+_Data, code, materials, negative results. Where they go, and when. A programme that only publishes what worked is a programme that cannot be checked._

package/standard/seeds/research/shapes/frame.prior-work.md

@@ -0,0 +1,23 @@
+<!--
+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
+
+_The findings you are building on rather than retesting. Cite them; say how confident the field actually is, not how confident the abstracts sound._
+
+## What Is Contested
+
+_Where the literature disagrees, and what the disagreement turns on — a measure, a population, a definition._
+
+## The Gap
+
+_What nobody has asked, or has asked badly. Be specific about which part of the question is genuinely open; "more research is needed" is not a gap._
+
+## Why Now
+
+_What changed — a new instrument, a new dataset, a policy shift — that makes this answerable when it wasn't._

package/standard/seeds/research/shapes/frame.question.md

@@ -0,0 +1,24 @@
+<!--
+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
+
+_In one sentence, ending in a question mark. If it takes a paragraph, you have a programme, not a question — say the question, then list the strands beneath it._
+
+## Why It Matters
+
+_What decision, practice, or belief changes depending on the answer. Who is currently acting on a guess._
+
+## What Would Count As An Answer
+
+_The standard of evidence you will hold yourself to, before you know what the data says. Stating it here is what stops it from drifting to meet the result._
+
+## What This Programme Is Not Asking
+
+_The adjacent question you are deliberately leaving alone, and why. This is where a research programme's scope is held._

package/standard/seeds/research/shapes/investigation.full.md

@@ -0,0 +1,49 @@
+<!--
+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
+
+_The question this investigation answers, and why it is worth answering. One or two paragraphs, ending in an actual question mark. This is the stable part: if the question changes substantially, you have a different investigation, not an edit to this one._
+
+### Assumptions
+
+_What you are taking as given and have not tested — about the population, the instrument, the prior literature, the world. Nested under Intent because they frame it. Surface them so an untested assumption doesn't get read later as a finding._
+
+## Open Questions
+
+_What you don't yet know about how to run this — an undecided measure, an unresolved confound, a missing approval. Kept high so uncertainty is seen rather than buried. When one is settled it graduates into an Assumption, a Claim, or a Decision._
+
+## Claims & Evidence
+
+_What this investigation asserts, and what supports each assertion. Label each claim **C1:**, **C2:**, … (bold, unique within this investigation). Give each its evidence and its strength; a claim with no evidence yet is still a claim — mark it so. Push data, tables, and instrument detail into a sub-section a claim points to, not onto the line. Evolves freely._
+
+- **C1:** <!-- the assertion --> <!-- evidence: … -->
+
+## What Would Change Our Mind
+
+_The falsifier: the specific result that would make you abandon or revise the claims above. Concrete enough that someone could go and look. An investigation with no falsifier is an opinion with citations, and this is the section this framework leans on hardest._
+
+## Out of Scope
+
+_What this investigation **cannot** tell you, and who will be tempted to think it can. Populations not sampled, mechanisms not tested, the causal claim the design does not support. The second-hardest-working section here: it is what keeps a finding from being over-read downstream._
+
+## Dependencies
+
+_What this needs before it can run: data, access, approvals, instruments, or another investigation's result. The `depends_on` property at the top is the investigation-only subset of this, as links. Reference other investigations as markdown links — never bare names._
+
+## Method
+
+_How the question is actually approached: design, sample, measures, analysis. Enough that a reader can judge whether the Claims follow. Detail belongs here rather than on a claim line; a full protocol can live in its own top-level doc this section points at._
+
+## Notes & Decisions
+
+_Two things under one header. **Notes**: threats to validity, things to chase, what surprised you. **Decisions**: an append-only log, one line each, with an optional but recommended date._
+
+<!-- 2026-08-26: Dropped the second cohort, consent window closed. (Brenton) -->

package/standard/seeds/research/shapes/investigation.note.md

@@ -0,0 +1,26 @@
+<!--
+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
+
+_The question, and why it is worth answering. End it in a question mark. A paragraph is plenty here._
+
+## Open Questions
+
+_What you don't yet know about how to approach it. Honest holes beat invented certainty._
+
+## Claims
+
+_What you currently believe, labeled **C1:**, **C2:**, … with a word on what supports each — including "nothing yet." A note is allowed to be thin, but never vague about its own confidence._
+
+- **C1:**
+
+## Out of Scope
+
+_What this could not tell you even if it went perfectly. Even in a note, this is the section worth filling — it is what stops a preliminary result from being quoted as a conclusion._

package/standard/seeds/software/Framework.md

@@ -0,0 +1,88 @@
+---
+# The Eidos version this framework targets; migrate reads and bumps it.
+eidos_version: 4.5.0
+# How files, folders, and links are named: kebab-case | TitleCase | Title Case. Absent = kebab-case.
+naming: kebab-case
+---
+
+# Framework
+
+The framework's index and config, in one place: the version and naming convention above, and below the
+Top-Level documents, the Collections (with their flavors and grouping), and the property Schema. The
+visible `README.md` at the root is the friendly door to it; keep it current with the
+`configure` skill.
+
+## Top-Level
+
+<!-- configure: top-level index (regenerated) -->
+- [README](../README.md) — the root's front door: what this is, and pointers in.
+<!-- One bullet per top-level document. README is the door and comes first; add your own below (a
+     Roadmap, a Vision, the generated Blueprint Map canvas), each a link and a one-line description.
+     The framing docs live in the Frames collection, not here. configure refreshes this list. -->
+
+## Collections
+
+A collection is a top-level folder of repeated blueprints that share a body shape. `Frames` holds the
+framing docs — the most primary thing the folder says about itself — and `Specs` the product's
+units. Add more with `configure`. Each lists its flavors (the default marked) and its grouping,
+and points at its generated `index.md` leaf.
+
+### Frames
+
+The framing docs that set what every other blueprint is judged against — the product's architecture,
+audience, criteria, and market. This framework's framing collection; each frame follows the flavor of
+its kind, and one left unwritten is a gap to surface, not a failure.
+
+- **Leaf:** [Frames/index.md](../Frames/index.md)
+- **Flavors:**
+  - [architecture](shapes/frame.architecture.md) — the product as a built system (default).
+  - [audience](shapes/frame.audience.md) — who it serves, and how each kind differs.
+  - [criteria](shapes/frame.criteria.md) — budget, scope objectives, timeline.
+  - [market](shapes/frame.market.md) — landscape, positioning, and how it earns.
+- **Canvas:** file
+
+### Specs
+
+The product's units, one per blueprint, grouped by domain.
+
+- **Leaf:** [Specs/index.md](../Specs/index.md)
+- **Flavors:**
+  - [full](shapes/spec.full.md) — the complete spec shape (default).
+  - [micro](shapes/spec.micro.md) — Intent, Open Questions, ACs, Out of Scope; grow into full.
+- **Canvas:** card from `## Intent`
+- **Domains:** _(add one bullet per domain — a name and a short description — as domains accrue)_
+
+## Schema
+
+The property contract — what a blueprint's frontmatter may carry, across every collection. Two parts: the
+**core** properties Eidos's own machinery uses, and the **custom** ones you (or the seed) add. Every
+custom property declares which collections it **applies to** — `all`, or a list — so a property never
+lands where it makes no sense (`domain` is Specs-only). A property's type comes from the Obsidian set
+(Text, List, Number, Checkbox, Date, Date & time), so frontmatter renders natively in an Obsidian
+vault. The `configure` skill edits this section.
+
+### Eidos Core
+
+_Present on every blueprint. Managed by the standard (Eidos 4.5.0); `migrate` rewrites this block on a version change — don't hand-edit it. (`flavor` absent = the collection's default; `connects_to` absent = no canvas edges; a missing `summary` is flagged by the index.)_
+
+| Name        | Type | Meaning                                                                                        |
+| ----------- | ---- | ---------------------------------------------------------------------------------------------- |
+| id          | Text | Stable, unique, kebab-case identity. Assigned once, never renamed. References point at it.      |
+| title       | Text | Human-readable name.                                                                           |
+| summary     | Text | One plain line — what this blueprint is, in a sentence, distilled from Intent. Source for the collection index.md listing; absent, the index flags it. |
+| flavor      | Text | Which body flavor this blueprint follows, from its collection's declared flavors. Absent = the collection's default flavor. |
+| connects_to | List | Blueprints this one connects to on the canvas, each a markdown link; drawn as a directed edge (this → target). The intentional map, distinct from depends_on. |
+
+### Custom Properties
+
+_Yours to shape with the `configure` skill. The seed ships a few useful defaults below — keep, scope, or drop any of them; Eidos doesn't depend on them. Absence where a property applies is a soft gap the validator notes, never refuses._
+
+| Name          | Type | Applies To | Meaning                                                                                    |
+| ------------- | ---- | ---------- | ------------------------------------------------------------------------------------------ |
+| status        | Text | all        | Lifecycle value: Draft / Intake / In Progress / Done / Archived / Deprecated. An off-list value warns. |
+| date_created  | Date | all        | YYYY-MM-DD. The day the blueprint was first written. Set once.                                   |
+| date_modified | Date | all        | YYYY-MM-DD. The day the blueprint was last changed.                                              |
+| tags          | List | all        | Free tags.                                                                                  |
+| domain        | Text | Specs      | The grouping, matching the blueprint's sub-folder under its collection in the naming convention. An unknown value warns, never fails. |
+| depends_on    | List | Specs      | Blueprints this one needs, each a markdown link. An implementation dependency, not a canvas edge. |
+| type          | Text | Specs      | Open, soft category label — drives views and filtering, never structure. e.g. feature, capability, integration. |

package/standard/seeds/software/README.md

@@ -0,0 +1,24 @@
+# {{Product}}
+
+> **Start here.** This is the root for **{{Product}}** — the source of truth for what the
+> 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.
+
+## What this is
+
+_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._
+
+## Collections
+
+- **[Frames](Frames/index.md)** — the framing docs: Architecture, Audience, Criteria, Market.
+- **[Specs](Specs/index.md)** — the product's units, grouped by domain.
+
+---
+
+_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._