Write each line of inquiry down once: the question, the claims, and what would change your mind, written before the results. Every exclusion, deviation, and analysis choice is logged against it and confirmed by the person who owns the call, so the lab’s method outlives the student who knew it. It sits beside your lab notebook, not in place of it.
Free for macOS, Windows, and Linux. No account, no subscription.
Sound familiar?
And that someone defends in May.
The protocol is whatever the last postdoc did. It is written down nowhere, and you learn it by standing next to them.
Two copies of the method, the same file name, different thresholds, and nobody sure which one the first sample used.
Seven participants excluded, a recall time moved, a measure swapped. By the time the paper is written, the reasons are a guess.
How it fits
Install the research framework and the programme gets four frames that every investigation is judged against, and one file per investigation, grouped by strand. An investigation says what is being asked and what would settle it. It is not a lab notebook, a protocol, or a task list.
What you will use most
Declare your own kinds of decision (Deviation, Exclusion, Analysis) and log each one against the investigation it touches. A call a student or an agent made waits, unconfirmed, until the person who owns it confirms it.
In a Git repository, every frame and investigation shows its history: who changed it, when, and a diff against today. The method a sample used is a commit, not a guess.
The check lists every investigation missing a section its template asks for, such as the falsifier or Out of Scope, or a property such as its strand, on a laptop and in CI.
Scoring nights, freezing a notebook, uploading tables: tasks on a board, each pointing at the investigation it serves, so the investigation never fills up with to-dos.
Consent forms, ethics approvals, and figures linked to the investigations they belong to. Raw data stays where it lives now.
Claude Code or Codex beside the page, with the open investigation as context. A new student can ask how the lab scores a night and point it at the Method frame.
Pre-registration, kept
Exclusions, deviations, and analysis choices land in one table with the investigation they were made for, who logged them, and their status. An agent’s call arrives as Proposed, assigned to the person who owns it. When the paper needs its deviations section, the list is already there.
History
Keep the root in a Git repository and every frame shows its own history: who changed the standard of evidence, on which day, and the words that changed, with a diff beside the page. Nobody has to keep method_final2.md.
For the computational side
The desktop app is optional. The CLI on npm reads the same root, so the check runs in CI beside your analysis code, and an agent in your terminal can list the calls still waiting.
$ npm install -g eidosmd
$ eidos install @BuildableWorks/research
$ eidos decisions --unconfirmed
unconfirmed (2)
D-K68 Report slow spindles as exploratory, not as a test · Proposed analysis @priya assigned @ana
D-M70 Count spindles from the central average, not Fz · Proposed deviation @claude assigned @ana
$ eidos check
✓ no findingsStart here
Frames for question, prior work, method, and ethics, and investigations grouped by strand. It does not ship a collection for protocols: add one under Framework settings, with the sections your lab’s protocols share, and each protocol is checked against it like any other page.
A question, a study, or a programme
Frames for question, prior work, method, and ethics, and investigations grouped by strand.
$ eidos install @BuildableWorks/researchIn the app: New Root, then pick it from the list.
Download Eidos MD, install the research framework, and write your programme’s question and its standard of evidence. It is free, and the files stay in your lab’s own repository.
Free for macOS, Windows, and Linux. Your files stay plain text in a folder you own.