<?xml version="1.0" encoding="UTF-8"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="info" docName="draft-watts-scientific-admissibility-01" ipr="trust200902" submissionType="IETF">
<front><title>Scientific Admissibility Evidence Records: A Research Data Exchange Proposal</title><seriesInfo name="Internet-Draft" value="draft-watts-scientific-admissibility-01"/><author fullname="Deonté O'dell Watts" asciiFullname="Deonte O'dell Watts" initials="D. O." surname="Watts">
      <organization>GoodShyt Group Inc.</organization>
      <address>
        <postal>
          <city>San Francisco</city>
          <region>CA</region>
          <country>United States of America</country>
        </postal>
        <email>deonte@goodshyt.fun</email>
        <uri>https://orcid.org/0009-0005-8586-3650</uri>
      </address>
    </author><date year="2026" month="October" day="30"/><abstract><t>This document proposes interoperable evidence record fields for reproducible research workflows. It is an independent working draft and is not an IETF publication or standard.</t></abstract></front>
<middle><section numbered="true"><name>Introduction</name><t>Research archives need immutable source identifiers and typed evidence claims. This proposal is informational.</t></section>
    <section anchor="requirements-language"><name>Requirements Language</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" 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>
    </section><section numbered="true"><name>Record Fields</name><t>Each record carries source_id, locator, digest, claim_id, evidence_tier, falsifier, validation_status, and release_status. Missing fields are represented explicitly as unknown.</t></section><section numbered="true"><name>Processing</name><t>Implementations MUST NOT convert an unknown result to a false result or a passing integrity check into an empirical validity claim. A revision MUST preserve the prior record and link to it.</t></section><section numbered="true"><name>Security and Privacy Considerations</name><t>Implementations SHOULD minimize personal data and MUST NOT publish credentials. Digests are integrity checks, not proof of truth or ownership.</t></section><section numbered="true"><name>IANA Considerations</name><t>This document requests no IANA actions.</t></section></middle><back><references><name>References</name>
        <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>
        <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></references>
    <section anchor="changes-since-00" removeInRFC="true"><name>Changes since -00</name>
      <t>Editorial and tooling-conformance changes only; no technical content was changed.</t>
      <ul><li>Added submissionType="IETF" to &lt;rfc&gt;</li><li>Added BCP 14 Requirements Language section (document uses uppercase requirement keywords without the boilerplate; idnits error)</li><li>Added RFC 2119 reference entry</li><li>Added RFC 8174 reference entry</li><li>Normalized author metadata (full name with ASCII form, initials, organization GoodShyt Group Inc., San Francisco CA postal, email, ORCID URI)</li><li>Updated document date and revision number.</li></ul>
    </section>
  </back></rfc>
