Tiffany system capabilities (0)

An empty catalogue during discovery is not a gap to be filled with plausible entries. It is the answer.

Laboratory infrastructure capabilities (8)

• Read a scientific claim in full Available Public

  See a claim decomposed into components, each with what actually supports it — including the parts supported by nothing — plus its registered falsifiers, its open evidence debt and everything that changed since the last version.

  Provided by The laboratory · documentation · try it

  Limits: The scientific corpus is empty. Today this works on one clearly-marked demonstration fixture.

  Scientific qualification: not applicable — this is software, and no scientific claim is attached.

• Verify what you received Available Public

  Recompute a record's digest from the record itself, check an artifact's bytes against its published hash, or check the whole site against one manifest.

  Provided by Verification method · documentation · try it

  Limits: Proves you hold the bytes that were published. Proves nothing about whether a claim is true — the site keeps those apart deliberately.

  Scientific qualification: not applicable — this is software, and no scientific claim is attached.

• Call the public API Available Public

  Fetch claims, changes, the status vocabulary, the publication policy and the demonstration records as JSON. No key, no signup, no client library.

  Provided by Public API · documentation · try it

  Limits: Read-only. Scientific endpoints return empty sets by design.

  Scientific qualification: not applicable — this is software, and no scientific claim is attached.

• Resolve a status term Available Public

  Look up exactly what a status term means, in a versioned document, instead of guessing from the word.

  Provided by Status vocabulary · documentation · try it

  Limits: Definitions are versioned. A changed meaning requires a new ontology version, never a silent edit.

  Scientific qualification: not applicable — this is software, and no scientific claim is attached.

• Reproduce a published artifact Available Public

  Follow a published verification recipe and re-derive the outputs yourself from the published fixture.

  Provided by Portable research bundles · documentation · try it

  Limits: Demonstration apparatus only. Reproducing it faithfully reproduces a measurement that was later found invalid — which is the point of the example.

  Scientific qualification: not applicable — this is software, and no scientific claim is attached.

• Build a client against the contract Available Public

  Write software against published schemas and an OpenAPI document generated from the same registry the routes come from.

  Provided by Developer and API portal · documentation · try it

  Limits: The contract is small because the surface is small. It will grow through versioned, announced changes.

  Scientific qualification: not applicable — this is software, and no scientific claim is attached.

• Trace where a record came from Available Public

  Follow a claim's provenance chain step by step, with input and output digests, and see which steps are sanitised attestations rather than inspectable inputs.

  Provided by The laboratory · documentation · try it

  Limits: A sanitised step never discloses its private input. The record declares its own provenance completeness so you know which you are getting.

  Scientific qualification: not applicable — this is software, and no scientific claim is attached.

• Validate records against the schemas Available Public

  Check any document this site serves against its published schema with any draft 2020-12 validator.

  Provided by Published schemas · documentation · try it

  Limits: The build already does this for every emitted document; a failure stops the build.

  Scientific qualification: not applicable — this is software, and no scientific claim is attached.

Machine-readable capabilities →