™One record connects the work
The project record connects inputs, cohort or disease model, protocol, analysis run, method version, evidence, result, comparisons, reviewer decisions, and separately recorded outcomes. Each source retains its original identity and retrieval date so paths can meet without erasing provenance.
The private workspace includes governed project entry, bounded public-source metadata intake, comparisons, review, run specifications, and outcome tracking. Physical samples, unrestricted uploads, general chemistry execution, and scientifically validated predictions are outside the available project workflow.
Four starting points, different safeguards
A researcher may frame a public-source hypothesis or select a public cohort. A governed researcher-data project requires separate authority, privacy, validation, and retention checks. A Village project requires moderation and contribution rules. None of these paths should inherit another path's permissions.
Project creation and private records require verified, administrator-approved researcher access or authorized admin access. Joining the public waitlist does not grant a workspace account.
Search helps; review decides
Source metadata, citations, and API responses are candidates for human inspection. A researcher must verify relevance, rights, comparability, and scientific meaning before treating them as evidence for a conclusion.