Reusable
Another person can take the artifact and perform, adapt, or implement the method.
Reusable systems meant to be used, adapted, implemented, or extended by other people—not merely read.
Some work begins as a question. Some becomes an article. Some becomes research. And sometimes the work becomes something another person can actually use.
Open Methods is where I publish those operational artifacts. Each release is intended to preserve enough structure that another person can inspect the method, understand its boundaries, reproduce the workflow, adapt it to a new context, and trace the exact version they used.
Releases may include methodologies, executable prompts, workflow definitions, schemas, implementation notes, worked examples, GitHub source, version history, downloadable artifacts, and DOI-backed archival records.
Another person can take the artifact and perform, adapt, or implement the method.
The operating sequence, inputs, outputs, assumptions, and boundaries are made inspectable.
The release states what it does, what it does not establish, and what remains unvalidated.
A user can identify the exact release, source history, and citable archival object they relied on.
An Open Method is a reusable operational artifact. Inclusion here does not imply peer review, universal applicability, or independent validation. Each release should state its evidence, assumptions, limitations, version, license, and validation status explicitly.