Eidos

Knowledge / Research

@BuildableWorks/research

The research seed the standard ships, for a question, a study, or a programme of inquiry; frames for question, prior work, method, and ethics, and investigations grouped by strand.

0instalações nos últimos 30 dias0instalações no total

Instalar

A raiz inteira

npx eidosmd install @BuildableWorks/research

Uma coleção, ou uma variant em uma coleção que você já tem

npx eidosmd install @BuildableWorks/research --collection Frames
npx eidosmd install @BuildableWorks/research --variant Frames.prior-work
Fonte
BuildableWorks/Eidos no GitHub
Tag
v5.4.0
Caminho
seeds/research
Versão do Eidos
5.4.0
Convenção de nomes
kebab-case
Palavras-chave
seedresearchstudyinvestigations
Publicado
20 de setembro de 2026

O que contém

Coleções

Framesframe

What every investigation is judged against: what is asked, what is known, what would count as knowing, and who is affected.

Variants

questionpadrãowhat the programme asks, and why it matters

Template: templates/frame.question.md

# 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._
prior-workwhat is already known, and where this sits

Template: templates/frame.prior-work.md

# 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._
methodhow anyone would know, and the standard of evidence

Template: templates/frame.method.md

# 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._
ethicswho is affected, what they consented to, what could go wrong

Template: templates/frame.ethics.md

# 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._

Investigationsinvestigation

The programme's units, one per line of inquiry, grouped by strand.

Agrupada por Strands

Variants

fullpadrãothe complete investigation template

Template: templates/investigation.full.md

# {{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) -->
noteIntent, Open Questions, Claims, Out of Scope; grow into full

Template: templates/investigation.note.md

# {{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._

Outras pastas

  • assets Images, diagrams, and documents the blueprints link to.

Papéis

Framework Ownerroles/framework-owner.md
# Framework Owner

## Who they are

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 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.

## 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.
Researcherroles/researcher.md
# 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.
Reviewerroles/reviewer.md
# 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.
Sponsorroles/sponsor.md
# 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.

Documentos de nível superior

  • README README.md the root's front door: what this programme asks, and pointers in.

Propriedades personalizadas

statusTexttodas as coleçõesLifecycle stage. (Draft | Open | Running | Answered | Inconclusive | Abandoned)
date_createdDatetodas as coleçõesYYYY-MM-DD. Set once.
date_modifiedDatetodas as coleçõesYYYY-MM-DD. The last change.
tagsListtodas as coleçõesFree tags.
strandobrigatóriaTextInvestigationsThe group: matches the blueprint's sub-folder. An unknown value warns.
depends_onListInvestigationsInvestigations, data, or approvals this one needs first, each a markdown link.

README

O primeiro documento de nível superior, como o autor o escreveu nesta tag, marcadores de posição incluídos. Os links abrem a fonte.

{{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 — the question, the prior work, the method, the ethics.
  • Investigations — one file per line of inquiry, grouped by strand.
  • assets — images, diagrams, and documents the blueprints link to.

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.

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/; see .eidos/Framework.yaml for the full index.