<?xml version='1.0' encoding='UTF-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-watts-scientific-data-record-00" category="info" submissionType="independent" ipr="trust200902" xml:lang="en" version="3" tocInclude="true" sortRefs="true" symRefs="true">

  <front>
    <title abbrev="Scientific Data Record">A Provenance-Bounded Record Format for Scientific Data</title>
    <seriesInfo name="Internet-Draft" value="draft-watts-scientific-data-record-00"/>

    <author fullname="Deonté O'dell Watts" asciiFullname="Deonte O'dell Watts" initials="D." surname="Watts">
      <organization>GoodShyt Group Inc.</organization>
      <address>
        <email>deonte@goodshyt.fun</email>
        <uri>https://orcid.org/0009-0005-8586-3650</uri>
      </address>
    </author>

    <date year="2026" month="11" day="16"/>

    <keyword>scientific data</keyword>
    <keyword>provenance</keyword>
    <keyword>evidence ledger</keyword>
    <keyword>falsifier</keyword>
    <keyword>fail-closed</keyword>

    <abstract>
      <t>This document specifies a JSON record format for scientific data
      and the claims derived from it. Each record binds a claim to an
      immutable source digest, a claim class, an evidence tier, a
      mandatory falsifier, a set of typed check results, and a
      provenance trail. Processing is fail-closed: a missing, unknown,
      or not-run check blocks admissibility. The format proves custody
      and unchanged bytes. It does not certify that a claim is true.</t>
    </abstract>

    <note removeInRFC="true">
      <name>Status of This Draft</name>
      <t>This is an individual, unreviewed design proposal. No
      experimental result, priority claim, or peer-review outcome is
      asserted. The example in <xref target="example"/> uses synthetic
      values and placeholder digests.</t>
    </note>
  </front>

  <middle>

    <section anchor="intro">
      <name>Introduction</name>
      <t>Scientific results are increasingly produced and summarized by
      automated systems. A summary can be repeated across documents
      until it appears independently supported, even though only one
      underlying source exists. This document defines a record that
      keeps the claim, its source, its evidence tier, its falsifier, and
      the results of the checks run against it in a single
      machine-verifiable unit.</t>

      <section anchor="scope">
        <name>Scope</name>
        <t>The format covers: the record data model
        (<xref target="model"/>), canonicalization and digests
        (<xref target="canon"/>), and processing rules
        (<xref target="processing"/>). It is transport-agnostic and
        storage-agnostic.</t>
      </section>

      <section anchor="nongoals">
        <name>Non-Goals</name>
        <ul>
          <li>Certifying that a claim is true. A valid record whose
          integrity check passes can still describe a false claim.</li>
          <li>Defining statistical methods, experimental designs, or
          domain-specific data formats.</li>
          <li>Asserting novelty or priority. The format has no member
          for either.</li>
        </ul>
      </section>
    </section>

    <section anchor="terminology">
      <name>Conventions and Definitions</name>
      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
      "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT
      RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
      interpreted as described in BCP 14 <xref target="RFC2119"/>
      <xref target="RFC8174"/> when, and only when, they appear in all
      capitals, as shown here.</t>
      <dl newline="false">
        <dt>Record:</dt>
        <dd>A JSON object conforming to <xref target="model"/>.</dd>
        <dt>Source:</dt>
        <dd>The immutable bytes (data file, notebook, export) from which
        a claim is drawn, identified by a digest.</dd>
        <dt>Claim:</dt>
        <dd>A statement derived from, or about, a source.</dd>
        <dt>Falsifier:</dt>
        <dd>A stated observation or test result that, if obtained, would
        show the claim to be wrong.</dd>
        <dt>Check:</dt>
        <dd>A named validation step with a result of PASS, FAIL, or
        NOT_RUN.</dd>
        <dt>Authority class:</dt>
        <dd>The kind of question a check answers (see
        <xref target="authority"/>).</dd>
      </dl>
    </section>

    <section anchor="model">
      <name>Data Model</name>
      <t>A Record is a JSON object <xref target="RFC8259"/>.
      <xref target="members"/> lists its members. Unknown members MUST
      be ignored for processing but MUST be included when computing the
      record digest (<xref target="canon"/>).</t>

      <table anchor="members">
        <name>Record Members</name>
        <thead>
          <tr><th>Member</th><th>Type</th><th>Requirement</th><th>Meaning</th></tr>
        </thead>
        <tbody>
          <tr><td>schema_version</td><td>string</td><td>REQUIRED</td><td>Format version. This document defines "1".</td></tr>
          <tr><td>record_id</td><td>string</td><td>REQUIRED</td><td>Identifier unique within the issuing archive.</td></tr>
          <tr><td>source</td><td>object</td><td>REQUIRED</td><td>Source identifier and digest.</td></tr>
          <tr><td>claim</td><td>object</td><td>REQUIRED</td><td>Claim text and claim class.</td></tr>
          <tr><td>evidence_tier</td><td>string</td><td>REQUIRED</td><td>One of the tiers in <xref target="tiers"/>.</td></tr>
          <tr><td>falsifier</td><td>string</td><td>REQUIRED</td><td>Non-empty falsifier statement.</td></tr>
          <tr><td>checks</td><td>array</td><td>REQUIRED</td><td>Zero or more check results. May be empty.</td></tr>
          <tr><td>provenance</td><td>array</td><td>REQUIRED</td><td>Entity, activity, and agent references.</td></tr>
          <tr><td>state</td><td>string</td><td>REQUIRED</td><td>One of the states in <xref target="states"/>.</td></tr>
          <tr><td>created_at</td><td>string</td><td>REQUIRED</td><td>Timestamp in the format of <xref target="RFC3339"/>.</td></tr>
          <tr><td>record_digest</td><td>object</td><td>REQUIRED</td><td>Digest of the record itself (<xref target="canon"/>).</td></tr>
        </tbody>
      </table>

      <section anchor="source-obj">
        <name>The source Object</name>
        <t>The "source" object has a REQUIRED string member "source_id"
        and a REQUIRED object member "digest" with string members "alg"
        and "value". This document defines the algorithm identifier
        "sha-256", with "value" being the lowercase hexadecimal encoding
        of the digest of the source bytes. A source object MAY carry an
        OPTIONAL "description" string.</t>
      </section>

      <section anchor="classes">
        <name>Claim Classes</name>
        <t>The "claim" object has a REQUIRED string member "text" and a
        REQUIRED string member "class". The class MUST be one of:</t>
        <dl newline="false">
          <dt>ESTABLISHED:</dt>
          <dd>The claim restates a result already reported with
          empirical support, with the supporting source identified.</dd>
          <dt>DERIVED:</dt>
          <dd>The claim follows from the identified source by a stated
          calculation or argument.</dd>
          <dt>CONJECTURE:</dt>
          <dd>The claim is a hypothesis not yet tested.</dd>
          <dt>ANOMALY:</dt>
          <dd>The claim reports an unexplained observation or a negative
          result.</dd>
        </dl>
        <t>A record's class describes what kind of statement the claim
        is. It does not describe how likely the claim is to be true.</t>
      </section>

      <section anchor="tiers">
        <name>Evidence Tiers</name>
        <t>The "evidence_tier" member MUST be one of "T1" (empirical),
        "T2" (derived from identified inputs), "T3" (rigorous
        conjecture), or "T4" (speculative). The scale is local to this
        format and is not a clinical or regulatory grading.</t>
      </section>

      <section anchor="checks">
        <name>Check Results</name>
        <t>Each element of "checks" is an object with REQUIRED string
        members "name", "authority_class", and "result". "result" MUST
        be "PASS", "FAIL", or "NOT_RUN". A check object MAY carry
        "tool" and "run_id" strings. A check that was specified but not
        executed MUST be recorded as "NOT_RUN" and MUST NOT be omitted
        or recorded as "PASS".</t>
      </section>

      <section anchor="authority">
        <name>Authority Classes</name>
        <t>The "authority_class" of a check MUST be one of "structural",
        "integrity", "diagnostic", "admissibility", "governance", or
        "provenance". A result of one class MUST NOT be accepted as
        satisfying a requirement of another class. In particular, a
        passing "integrity" check does not establish admissibility, and
        a "diagnostic" result MUST NOT by itself cause a state
        transition.</t>
      </section>

      <section anchor="prov">
        <name>Provenance</name>
        <t>Each element of "provenance" is an object with REQUIRED string
        members "role" and "ref". "role" MUST be "entity", "activity",
        or "agent", following the separation used in
        <xref target="PROV-O"/>. "ref" is an identifier or URI for the
        referenced item.</t>
      </section>

      <section anchor="states">
        <name>States</name>
        <t>The "state" member MUST be "ADMISSIBLE", "BLOCKED", or
        "HISTORICAL". "HISTORICAL" marks a record retained for lineage
        that is no longer active. The processing rule for
        "ADMISSIBLE" is in <xref target="admissible-rule"/>.</t>
      </section>
    </section>

    <section anchor="canon">
      <name>Canonicalization and Digests</name>
      <t>The record digest is computed as follows.</t>
      <ol>
        <li>Remove the "record_digest" member from the record.</li>
        <li>Serialize the remainder using the JSON Canonicalization
        Scheme <xref target="RFC8785"/>.</li>
        <li>Compute SHA-256 over the resulting bytes
        <xref target="RFC6234"/>.</li>
        <li>Encode as lowercase hexadecimal and store in
        "record_digest.value", with "record_digest.alg" set to
        "sha-256".</li>
      </ol>
      <t>Reordering JSON members MUST NOT change the digest. A verifier
      MUST recompute the digest and MUST reject the record on
      mismatch. A digest identifies bytes. It says nothing about whether
      the described claim is correct.</t>
    </section>

    <section anchor="processing">
      <name>Processing Rules</name>
      <t>Processing is fail-closed: an unknown, missing, or not-run
      condition blocks a state transition and is never treated as a
      positive finding.</t>

      <section anchor="validation">
        <name>Validation</name>
        <t>A processor MUST reject a record that:</t>
        <ul>
          <li>lacks a REQUIRED member or has a member of the wrong
          type;</li>
          <li>has a "falsifier" that is empty or consists only of
          whitespace;</li>
          <li>carries a "class", "evidence_tier", "state", "result", or
          "authority_class" value outside the sets defined in this
          document; or</li>
          <li>fails the digest verification of
          <xref target="canon"/>.</li>
        </ul>
      </section>

      <section anchor="admissible-rule">
        <name>Admissibility</name>
        <t>A record MAY be in state "ADMISSIBLE" only if every check
        that the local policy requires has result "PASS" and at least
        one check with "authority_class" "admissibility" has result
        "PASS". A required check that is absent, "NOT_RUN", or "FAIL"
        MUST yield state "BLOCKED". Repetition of the same assertion
        across records that share a source does not count as independent
        support.</t>
      </section>

      <section anchor="log">
        <name>Append-Only History</name>
        <t>Archives SHOULD store records as an append-only sequence of
        events and derive the current state as a projection of that
        sequence. A correction is a new record or event that supersedes
        the earlier one, which is then marked "HISTORICAL". An archive
        MUST NOT silently edit a stored record.</t>
      </section>
    </section>

    <section anchor="example">
      <name>Example</name>
      <t>The following record uses synthetic values. The digest values
      are placeholder strings, not computed digests, so the example is
      illustrative and would fail the digest verification of
      <xref target="canon"/>.</t>
      <sourcecode type="json">
{
  "schema_version": "1",
  "record_id": "urn:example:record:0001",
  "source": {
    "source_id": "urn:example:source:values-v1",
    "digest": {
      "alg": "sha-256",
      "value": "&lt;placeholder: 64 hex characters&gt;"
    },
    "description": "Three synthetic numbers: 1, 2, 3."
  },
  "claim": {
    "text": "The arithmetic mean of the source values is 2.",
    "class": "DERIVED"
  },
  "evidence_tier": "T2",
  "falsifier": "A recomputed mean differs from 2.",
  "checks": [
    {
      "name": "schema-validation",
      "authority_class": "structural",
      "result": "PASS"
    },
    {
      "name": "recompute-mean",
      "authority_class": "admissibility",
      "result": "NOT_RUN"
    }
  ],
  "provenance": [
    {"role": "entity", "ref": "urn:example:source:values-v1"},
    {"role": "agent", "ref": "urn:example:agent:author"}
  ],
  "state": "BLOCKED",
  "created_at": "2026-11-16T00:00:00Z",
  "record_digest": {
    "alg": "sha-256",
    "value": "&lt;placeholder: 64 hex characters&gt;"
  }
}
</sourcecode>
      <t>The record is in state "BLOCKED" because the required
      admissibility check was not run, even though the structural check
      passed.</t>
    </section>

    <section anchor="security">
      <name>Security Considerations</name>
      <t>The format provides custody and tamper evidence, not truth. A
      validly digested record can describe a false claim, and a reader
      who treats a well-formed record as authoritative is exposed to a
      false aura of correctness. Implementations SHOULD display the
      boundary between integrity and admissibility wherever records are
      rendered.</t>
      <t>Canonicalization differences can cause digest mismatches or,
      if implemented incorrectly, collisions between distinct records.
      Implementations MUST use a conforming
      <xref target="RFC8785"/> serializer. Digest algorithm agility is
      handled by the "alg" member. Future versions can add algorithms,
      and verifiers MUST reject algorithms they do not support rather
      than skipping verification.</t>
      <t>Records can be replayed, reordered, or selectively omitted.
      Archives SHOULD use an append-only event log with its own
      integrity protection. This document does not define signatures;
      deployments that need signer attribution can layer them over the
      canonical bytes.</t>
      <t>A diagnostic result that is promoted to a state change, or a
      passing check of the wrong authority class that is accepted as
      satisfying another, would let an unverified claim become
      "ADMISSIBLE". Processors MUST enforce <xref target="authority"/>
      and <xref target="admissible-rule"/>.</t>
    </section>

    <section anchor="privacy">
      <name>Privacy Considerations</name>
      <t>Records can name authors, participants, or third-party
      material in "provenance", "description", or claim text. Authors
      SHOULD omit personal data that is not needed to verify the claim
      and SHOULD confirm rights and consent before publishing a source
      or its digest. A digest of low-entropy personal data can be
      reversed by guessing and SHOULD NOT be published for such
      data.</t>
    </section>

    <section anchor="iana">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>

  </middle>

  <back>
    <references>
      <name>References</name>

      <references anchor="normative">
        <name>Normative References</name>

        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author initials="S." surname="Bradner" fullname="S. Bradner"/>
            <date year="1997" month="March"/>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>

        <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author initials="B." surname="Leiba" fullname="B. Leiba"/>
            <date year="2017" month="May"/>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>

        <reference anchor="RFC8259" target="https://www.rfc-editor.org/info/rfc8259">
          <front>
            <title>The JavaScript Object Notation (JSON) Data Interchange Format</title>
            <author initials="T." surname="Bray" fullname="T. Bray" role="editor"/>
            <date year="2017" month="December"/>
          </front>
          <seriesInfo name="STD" value="90"/>
          <seriesInfo name="RFC" value="8259"/>
          <seriesInfo name="DOI" value="10.17487/RFC8259"/>
        </reference>

        <reference anchor="RFC8785" target="https://www.rfc-editor.org/info/rfc8785">
          <front>
            <title>JSON Canonicalization Scheme (JCS)</title>
            <author initials="A." surname="Rundgren" fullname="A. Rundgren"/>
            <author initials="B." surname="Jordan" fullname="B. Jordan"/>
            <author initials="S." surname="Erdtman" fullname="S. Erdtman"/>
            <date year="2020" month="June"/>
          </front>
          <seriesInfo name="RFC" value="8785"/>
          <seriesInfo name="DOI" value="10.17487/RFC8785"/>
        </reference>

        <reference anchor="RFC6234" target="https://www.rfc-editor.org/info/rfc6234">
          <front>
            <title>US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF)</title>
            <author initials="D." surname="Eastlake 3rd" fullname="D. Eastlake 3rd"/>
            <author initials="T." surname="Hansen" fullname="T. Hansen"/>
            <date year="2011" month="May"/>
          </front>
          <seriesInfo name="RFC" value="6234"/>
          <seriesInfo name="DOI" value="10.17487/RFC6234"/>
        </reference>

        <reference anchor="RFC3339" target="https://www.rfc-editor.org/info/rfc3339">
          <front>
            <title>Date and Time on the Internet: Timestamps</title>
            <author initials="G." surname="Klyne" fullname="G. Klyne"/>
            <author initials="C." surname="Newman" fullname="C. Newman"/>
            <date year="2002" month="July"/>
          </front>
          <seriesInfo name="RFC" value="3339"/>
          <seriesInfo name="DOI" value="10.17487/RFC3339"/>
        </reference>
      </references>

      <references anchor="informative">
        <name>Informative References</name>

        <reference anchor="PROV-O" target="https://www.w3.org/TR/prov-o/">
          <front>
            <title>PROV-O: The PROV Ontology</title>
            <author>
              <organization>W3C</organization>
            </author>
            <date year="2013" month="April"/>
          </front>
          <refcontent>W3C Recommendation</refcontent>
        </reference>
      </references>
    </references>

    <section anchor="acknowledgements" numbered="false">
      <name>Acknowledgements</name>
      <t>None.</t>
    </section>
  </back>
</rfc>