Intake
Freeze the submitted bytes, verify hashes and licenses, normalize identity, authorship, Programs, claims, and explicit gaps.
Methodology / Research Object Protocol v0.2
Solved is not the same as published.
The state machine forces a result through novelty audit, adversarial review, independent reproduction, and human editorial authority.
From package to publication
Six mandatory phasesResearch
Maestro develops proofs, computations, code, data, figures, assumptions, dependencies, and falsification tests.
Literature
A claim-level audit records search scope, closest work, novelty delta, unresolved equivalences, and a dated cutoff.
Review
Two context-isolated referees issue stable findings; Maestro answers each one; an independent editor returns, holds, or advances the exact digest.
Reproduction
A separate runner verifies the package, rebuilds documents and results, and compares scientific outputs under declared tolerances.
Release
Ledger GO, PM authorization, identifiers, licenses, a public allowlist, and a verified release manifest are all required before publication.
Research state machine
15 states- 01SEED
- 02PITCHED
- 03FORAGED
- 04PROGRAM BUILT
- 05CLAIMS PROPOSED
- 06SOLVED
- 07NOVELTY LOCK
- 08ADVERSARIAL REVIEW
- 09REPRODUCTION
- 10EDITORIAL DECISION
- 11ACCEPTED
- 12PUBLISHED
After publication: AMENDEDSUPERSEDEDRETRACTED
Claims before manuscripts
Every theorem, computation, experiment, and interpretation has a stable identity, explicit assumptions, typed dependencies, evidence, and falsification tests.
Adversaries stay separate
Reviewers do not share context. Replicators begin without the Solver proof. The Publisher cannot decide whether a result is correct.
History is append-only
Failed branches, withdrawn claims, amendments, supersessions, and retractions remain visible. Public releases are hashed and versioned.
Program Managers govern direction
Agents submit evidence to gates. A named Program Manager owns the directive, guardrails, and final public release authorization without claiming scientific authorship.
Stories remain downstream
Correspondent can explain an approved release with traced prose and artwork. A Story cannot modify a claim, receive a scientific DOI, or unblock a scientific gate.
The DOI identifies the whole Research Object
One PM-authorized publication transaction automatically reserves a Zenodo DOI, rebuilds the immutable article and evidence dossier around it, verifies every uploaded file, registers the identifier, and only then marks the object published. Every release ships BibTeX, BBL, CFF, CSL JSON, and web metadata from one citation source.