<?xml version='1.0' encoding='UTF-8'?>
<?xml-model href="rfc7991bis.rnc"?><!DOCTYPE rfc [
<!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;">
]>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="info" docName="draft-watts-scientific-data-admissibility-00" ipr="trust200902" submissionType="IETF" consensus="false" sortRefs="true" symRefs="true" tocInclude="true" tocDepth="3">

  <front>
    <title abbrev="Scientific Data Admissibility Records">Scientific Data Admissibility Records: A Fail-Closed Layered Model for Research Artifacts</title>
    <seriesInfo name="Internet-Draft" value="draft-watts-scientific-data-admissibility-00"/>

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

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

    <area>General</area>
    <workgroup>Independent Submission</workgroup>

    <keyword>scientific data</keyword>
    <keyword>provenance</keyword>
    <keyword>admissibility</keyword>
    <keyword>verification</keyword>
    <keyword>fail-closed</keyword>
    <keyword>reproducibility</keyword>

    <abstract>
      <t>Automated research pipelines routinely move scientific data and derived claims from ingestion to publication without a machine-checkable record of what has actually been verified. This document defines a Scientific Data Admissibility Record (SDAR): a small, serializable structure that keeps schema conformance, provenance, numerical verification, empirical evidence, and interpretation as separate layers, each with an explicit status. It specifies a fail-closed aggregation rule so that an unverified or not-yet-run layer can never be silently promoted into an accepted result. The document also defines an XML serialization and processing rules, and is intended as a starting point for discussion rather than a proposed standard.</t>
    </abstract>

    <note title="About This Document" removeInRFC="true">
      <t>This is an individual, personal submission. It has no IETF working group and represents the view of its author only.</t>
      <t>Discussion of this document is welcome via the author's contact address given in the Authors' Addresses section.</t>
    </note>
  </front>

  <middle>

    <section anchor="introduction" numbered="true" toc="default">
      <name>Introduction</name>
      <t>Scientific datasets, statistical artifacts, and AI-assisted analyses are now commonly produced by automated pipelines. These pipelines usually report a single outcome, such as "passed", for a result that in fact depends on several distinct kinds of checking: whether the data conforms to its declared schema, where it came from, whether the reported numbers can be recomputed, whether independent evidence supports them, and whether the stated interpretation follows from them.</t>
      <t>When these kinds of checking are collapsed into one flag, a pipeline can quietly promote a claim: a result that was only schema-valid becomes "verified", or a number that was never recomputed is reported as confirmed. A reader of the final artifact cannot tell which checks were performed, in which environment, or whether a check was run at all.</t>
      <t>This document defines the Scientific Data Admissibility Record (SDAR) to make that distinction explicit and machine-readable. The design goals are:</t>
      <ul spacing="normal">
        <li>Separation: each kind of checking is a distinct layer and is never inferred from another layer.</li>
        <li>Explicit absence: a check that has not been run is recorded as such and is never conflated with a passing result.</li>
        <li>Fail-closed aggregation: the overall state is admissible only if every required layer has positively passed.</li>
        <li>Binding: every layer result is bound by digest to the exact artifact and inputs it was computed over.</li>
      </ul>
      <t>This document does not define how any check is performed, does not assert that any particular scientific claim is true, and does not define a trust framework for the parties that produce records.</t>
    </section>

    <section anchor="terminology" numbered="true" toc="default">
      <name>Terminology</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" spacing="normal">
        <dt>Subject:</dt>
        <dd>The artifact a record is about, such as a dataset, a statistical result file, or a derived claim.</dd>
        <dt>Layer:</dt>
        <dd>One independent kind of checking applied to a subject. This document defines five.</dd>
        <dt>Producing environment:</dt>
        <dd>The system, code revision, and configuration in which a layer result was actually computed.</dd>
        <dt>Admissible:</dt>
        <dd>The aggregate state of a record in which every required layer has the status "pass". Admissibility is a statement about the completeness of checking, not about the truth of the subject.</dd>
      </dl>
    </section>

    <section anchor="model" numbered="true" toc="default">
      <name>Model</name>

      <section anchor="layers" numbered="true" toc="default">
        <name>Layers</name>
        <t>An SDAR contains one result for each of the following layers.</t>
        <table align="left" anchor="layer-table">
          <name>Defined Layers</name>
          <thead>
            <tr><th>Layer</th><th>Question answered</th></tr>
          </thead>
          <tbody>
            <tr><td>schema</td><td>Does the subject conform to its declared schema?</td></tr>
            <tr><td>provenance</td><td>Can the subject's origin and transformations be traced, with inputs bound by digest?</td></tr>
            <tr><td>numeric</td><td>Can the reported numerical values be recomputed from the bound inputs?</td></tr>
            <tr><td>empirical</td><td>Is there independent evidence supporting the values, such as an independent reproduction?</td></tr>
            <tr><td>interpretation</td><td>Does the stated interpretation follow from the verified values, as judged by an identified reviewer?</td></tr>
          </tbody>
        </table>
        <t>A layer result MUST NOT be derived from the result of a different layer. In particular, a "pass" for schema or numeric MUST NOT cause the empirical or interpretation layers to be recorded as "pass".</t>
      </section>

      <section anchor="status" numbered="true" toc="default">
        <name>Status Values</name>
        <t>Each layer has exactly one status:</t>
        <dl newline="false" spacing="normal">
          <dt>pass:</dt>
          <dd>The check was run in an identified producing environment and succeeded.</dd>
          <dt>fail:</dt>
          <dd>The check was run and did not succeed.</dd>
          <dt>not-run:</dt>
          <dd>The check has not been run. This is the initial status of every layer.</dd>
          <dt>pending:</dt>
          <dd>The check has been scheduled or requested but no result is available, for example while awaiting independent reproduction.</dd>
        </dl>
        <t>A producer MUST NOT record "pass" for a layer unless it can supply the evidence fields required in <xref target="evidence"/>. The statuses "not-run" and "pending" are first-class values and MUST NOT be presented to consumers as equivalent to "pass".</t>
      </section>

      <section anchor="aggregation" numbered="true" toc="default">
        <name>Fail-Closed Aggregation</name>
        <t>The aggregate state of a record is computed from its required layers as follows:</t>
        <ol spacing="normal" type="1">
          <li>If any required layer has status "fail", the aggregate state is "rejected".</li>
          <li>Otherwise, if every required layer has status "pass", the aggregate state is "admissible".</li>
          <li>Otherwise, the aggregate state is "incomplete".</li>
        </ol>
        <t>A processor that cannot parse a record, cannot resolve a required digest, or encounters an unknown status value MUST treat the aggregate state as "incomplete" and MUST NOT treat it as "admissible". Which layers are required is a matter of local policy; however, a policy that omits the interpretation layer MUST NOT label the aggregate state in a way that implies interpretive review occurred.</t>
      </section>

      <section anchor="evidence" numbered="true" toc="default">
        <name>Evidence Fields for a Passing Layer</name>
        <t>A layer with status "pass" MUST carry:</t>
        <ul spacing="normal">
          <li>an identifier for the producing environment, including a code or tool revision;</li>
          <li>the time at which the result was produced;</li>
          <li>the digest of each input the result was computed over; and</li>
          <li>for the interpretation layer, an identifier for the reviewer.</li>
        </ul>
        <t>A layer with status "pass" in the empirical layer SHOULD identify the party that performed the independent reproduction and SHOULD state whether that party is independent of the producer of the subject.</t>
      </section>

      <section anchor="digests" numbered="true" toc="default">
        <name>Digest Binding</name>
        <t>Digests identify the exact bytes a result was computed over. A digest MUST be expressed as an algorithm name and a value; whitespace inside a serialized digest value is not significant and MUST be ignored by processors. Producers SHOULD use a SHA-2 family algorithm <xref target="RFC6234"/>. Where the subject is structured data, producers SHOULD digest a canonical serialization so that equivalent content yields the same digest; for JSON, <xref target="RFC8785"/> is one such canonicalization.</t>
        <t>If any digest in a record does not match the corresponding artifact at verification time, every layer bound to that digest MUST be treated as "not-run" by the verifier.</t>
      </section>
    </section>

    <section anchor="xml" numbered="true" toc="default">
      <name>XML Serialization</name>
      <t>This section defines an XML serialization of an SDAR. The namespace shown is a placeholder and is not registered; see <xref target="iana"/>.</t>

      <section anchor="xml-structure" numbered="true" toc="default">
        <name>Structure</name>
        <t>The root element is "sdar". It contains one "subject" element, one "layers" element containing exactly five "layer" elements (one per layer name), and one OPTIONAL "aggregate" element. A "layer" element has a "name" attribute and a "status" attribute, and MAY contain "environment", "produced", "input", and "reviewer" child elements. An "aggregate" element, when present, is informational; consumers MUST recompute the aggregate state from the layers using <xref target="aggregation"/> and MUST NOT trust a supplied value.</t>
      </section>

      <section anchor="xml-example" numbered="true" toc="default">
        <name>Example</name>
        <t>The following record describes a dataset whose schema and provenance checks have passed, whose numeric check has failed, and whose remaining checks have not been run. All identifiers, digests, and the namespace are illustrative.</t>
        <sourcecode type="xml" name="sdar-example.xml">
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;sdar xmlns="https://example.org/ns/sdar" version="0"&gt;
  &lt;subject id="dataset-0001" kind="dataset"&gt;
    &lt;digest alg="sha-256"&gt;
      00000000000000000000000000000000
      00000000000000000000000000000000
    &lt;/digest&gt;
    &lt;title&gt;Example measurement series&lt;/title&gt;
  &lt;/subject&gt;
  &lt;layers&gt;
    &lt;layer name="schema" status="pass"&gt;
      &lt;environment&gt;validator rev a1b2c3d&lt;/environment&gt;
      &lt;produced&gt;2026-11-16T12:00:00Z&lt;/produced&gt;
      &lt;input alg="sha-256" ref="dataset-0001"&gt;
        00000000000000000000000000000000
        00000000000000000000000000000000
      &lt;/input&gt;
    &lt;/layer&gt;
    &lt;layer name="provenance" status="pass"&gt;
      &lt;environment&gt;lineage tool rev 4d5e6f7&lt;/environment&gt;
      &lt;produced&gt;2026-11-16T12:05:00Z&lt;/produced&gt;
      &lt;input alg="sha-256" ref="dataset-0001"&gt;
        00000000000000000000000000000000
        00000000000000000000000000000000
      &lt;/input&gt;
    &lt;/layer&gt;
    &lt;layer name="numeric" status="fail"/&gt;
    &lt;layer name="empirical" status="not-run"/&gt;
    &lt;layer name="interpretation" status="not-run"/&gt;
  &lt;/layers&gt;
  &lt;aggregate state="rejected"/&gt;
&lt;/sdar&gt;
</sourcecode>
        <t>In this example, a processor following <xref target="aggregation"/> computes the aggregate state "rejected" because the numeric layer has status "fail". Had the numeric layer been "not-run", the aggregate state would have been "incomplete".</t>
      </section>
    </section>

    <section anchor="processing" numbered="true" toc="default">
      <name>Processing Rules</name>
      <ol spacing="normal" type="1">
        <li>A consumer MUST verify all digests against the artifacts they name before using any layer result bound to them.</li>
        <li>A consumer MUST recompute the aggregate state and MUST ignore any supplied aggregate value for decision purposes.</li>
        <li>A consumer MUST reject a record that contains more than one layer with the same name, or that lacks any of the five layer names, by treating the aggregate state as "incomplete".</li>
        <li>A producer that later changes a layer result MUST issue a new record rather than altering the existing record in place, so that earlier states remain auditable.</li>
      </ol>
    </section>

    <section anchor="iana" numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions. The namespace used in the examples is a placeholder, and no registration is requested.</t>
    </section>

    <section anchor="security" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>An SDAR is only as trustworthy as the party that produced it. This document does not define signing, authentication of producers, or a trust framework; a record that is unsigned can be forged or altered. Deployments that rely on records for decisions SHOULD protect them with an integrity mechanism appropriate to their environment and SHOULD record which party signed each layer result.</t>
      <t>Digest binding detects substitution of artifacts only if the digest was obtained over an authenticated channel. A producer who controls both a record and the artifact it names can make them consistent while both are wrong.</t>
      <t>The "admissible" aggregate state describes completeness of checking only. Consumers MUST NOT read it as a statement that the subject is correct or that the interpretation is true. Presenting "admissible" in a user interface without the underlying layer statuses invites exactly the silent promotion this document aims to prevent.</t>
      <t>Records can contain environment identifiers, reviewer identifiers, and timestamps that may be sensitive. Implementations SHOULD consider whether these fields should be disclosed beyond the parties that need them.</t>
      <t>General guidance on writing security considerations is given in <xref target="RFC3552"/>.</t>
    </section>

  </middle>

  <back>

    <references anchor="normative-refs">
      <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 fullname="S. Bradner" initials="S." surname="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 fullname="B. Leiba" initials="B." surname="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>
    </references>

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

      <reference anchor="RFC3552" target="https://www.rfc-editor.org/info/rfc3552">
        <front>
          <title>Guidelines for Writing RFC Text on Security Considerations</title>
          <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
          <author fullname="B. Korver" initials="B." surname="Korver"/>
          <date year="2003" month="July"/>
        </front>
        <seriesInfo name="BCP" value="72"/>
        <seriesInfo name="RFC" value="3552"/>
        <seriesInfo name="DOI" value="10.17487/RFC3552"/>
      </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 fullname="D. Eastlake 3rd" initials="D." surname="Eastlake 3rd"/>
          <author fullname="T. Hansen" initials="T." surname="Hansen"/>
          <date year="2011" month="May"/>
        </front>
        <seriesInfo name="RFC" value="6234"/>
        <seriesInfo name="DOI" value="10.17487/RFC6234"/>
      </reference>

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

    <section anchor="acknowledgements" numbered="false" toc="default">
      <name>Acknowledgements</name>
      <t>The layered separation described here follows the author's ongoing work on evidence-to-consequence governance for research and AI-assisted claims.</t>
    </section>

  </back>
</rfc>