Journal — Method
What makes a public research tool?
A prototype becomes useful to others when they can install it, inspect a sample, repeat a result, and report a problem.
The August readiness plan identified a gap between a promising project and a usable public research product. A concept, a private prototype, and a proposal document are valuable artifacts, but none demonstrates that an independent contributor can use the system.
A small minimum release
The proposed minimum was deliberately small: a versioned schema, an ingestion tool, quality checks, conservative derived features, a portable observation bundle, permitted sample data, tests, and contributor documentation.
An outside user should be able to understand what a sample contains, run the documented steps, and see how the outputs were produced. The example should not depend on private methods or undocumented data. The release also needs a place to report errors and a process for corrections.
Quality and privacy are features
The quality checks in the plan include timestamp integrity, range and calibration checks, missingness, clipping, dropouts, and device metadata. Privacy provisions include location precision and consent. These are practical parts of the product because they decide whether observations can be combined responsibly.
Treat adoption as evidence
A proposed community is different from a community that has used a tool and improved it. The plan asks for genuine independent use and contribution rather than treating an intended audience as an existing one. The next milestone is a documented outside run, with its failures and corrections preserved alongside its successes.