Findings and cited claims

A publication is a record under your name that others can cite by its exact version. There are two kinds. A cited claim ●Cited claims: Live states one assertion and attributes it to arXiv papers. A finding ●Findings: Live states a scoped conclusion from experiments you ran in your own tools, with what was done, on what data, what came out, how uncertain it is, what the evidence is and what its limits are. Both carry the same kind of assertion: readable wording plus a frame of named roles and typed values ●Frames and concepts: Live, explained on Concepts and frames.

What each kind carries#

A revision you do not declare stays unspecified; an unknown dataset version or an unavailable evidence file stays unknown or unavailable. The record never manufactures a value to fill a field. Once admitted, the record is an exact version ●Exact versions: Live with a permanent address at /records/<versionId> and a public JSON form; see Reuse and exact versions.

Who is responsible#

Publications are author-curated. You are responsible for what the assertion says, for the fidelity of a quotation to its source and for the numbers a finding reports; Substrate checks the structure, that every exact reference and concept resolves, that you are a current member of the Room with permission to publish, and that the same content is not admitted twice. It fetches no source, opens no evidence file and verifies no measurement. A finding published from an experiment neither completes that experiment nor implies its assignee’s agreement; those are separate, attributed acts.

Where publications appear#

• The Room’s Publications page lists every claim and finding of the Room with its kind, wording, status chip, exact version, source paper and author. Over the API, every finding summary also carries a provenanceSummary: whether it names an experiment, plan and attempts, how many attempts, and how many of its evidence entries resolved to materials.
• The Thread it was published in shows a card, and Research in this thread lists it; a finding’s card is where people reply to it.
• The record page shows the assertion, the structured statement and concepts, the citations, the exact references, the execution block and materials for a finding, any notices and warnings, and Reuse this publication with the version id.
• The reader’s Overview tab for a paper lists the publications that cite it ●Research about a paper: Live.
• An agent reads the same summaries in the Room research context under publications, newest first, and any list by wording with list_publications ●Literal discovery: Live.

How to publish#

The default path is your agent: the Publish page writes the message for it ●Publish page: Live, the agent drafts the record from what you select and previews it in your chat ●Local publication preview: Live, and it publishes once you agree, with the publish_records grant. The whole flow, the refusals and the manual form are on Publish with your agent. Over HTTP the operations are POST /api/agent/cited-claims and POST /api/agent/findings with schemaVersion: 2; on the adapter, publish_author_curated_claim and publish_finding. The response names the record id, the version id, its URL and its label, and carries a Thread receipt.

Findings and the experiments behind them#

A finding can name the experiment, the accepted plan and the attempts it rests on ●Typed execution provenance: Live, and each evidence entry can name the attempt and output label it came from and the digest of that file:

"provenance": {
  "execution": {
    "experimentId": "…",
    "planId": "…",
    "attemptIds": ["…"],
    "baselineAttemptIds": ["…"]
  },
  "evidence": [
    { "label": "metrics", "attemptId": "…", "outputLabel": "metrics.json",
      "digest": "<64 hex>", "access": "public", "reference": "…" },
    { "label": "crash", "kind": "attempt_outcome", "attemptId": "…",
      "access": "public", "reference": "…" }
  ],
  …
}

Admission checks that the experiment belongs to the Room, that the plan and attempts belong to the experiment, and that baseline attempts belong to the Room. An evidence entry of kind attempt_outcome cites a failure itself, for a finding whose result is that the run did not work. The response carries advisory warnings, never a refusal, when a named attempt produced no outputs, has no delivered outcome, did not succeed, or its outputs do not match the evidence. The record read resolves the block with labels, and GET /api/research/attempts?findingVersionId= lists the named attempts with their events, so one record read and one list show a reader everything the author put on record behind the finding. What the reader makes of it is their own judgement: Substrate checks no measurement and reruns nothing. What an attempt is, is on Attempts and the capture adapter; how evidence resolves to materials is on Materials and provenance.

Linking a finding to an experiment#

A finding is related to an experiment by an explicit link ●Findings linked to experiments: Live (link_experiment_finding, with post_thread) that carries a purpose, an explanation, optionally the producing attempt, and two separate verdicts:

A split verdict is mixed with its explanation. The link keeps the finding’s author and the linking member apart, changes no assignment, plan or status, and appears on the experiment’s page under Findings and in the Room research context with the replies it drew and which members other than the author replied.

Status, notices and warnings#

A publication is never edited. When a later record corrects, supersedes or retracts it, or someone disputes it, the link shows as a notice on the record and its status chip changes; a record that cites a changed version carries a warning. All of that is on Corrections, disputes and retractions.