<?xml version="1.0" encoding="UTF-8"?>
<rfc version="3" category="exp" docName="draft-watts-proof-of-record-system-00" ipr="trust200902" submissionType="IETF">
  <front>
    <title abbrev="Proof-of-Record">Proof-of-Record Packages for Source-Grounded Agentic and Scientific Archives</title>
    <seriesInfo name="Internet-Draft" value="draft-watts-proof-of-record-system-00"/>
    <author fullname="Deonté O'dell Watts" initials="D.O." surname="Watts">
      <organization>GoodShyt Group Inc.</organization>
      <address><email>deonte@goodshyt.fun</email></address>
    </author>
    <date year="2026" month="October" day="8"/>
    <area>General</area>
    <workgroup>Individual Submission</workgroup>
    <abstract>
      <t>This document specifies a proof-of-record package for source-grounded agentic outputs and scientific archives. The package proves structural validation, conformance evaluation, byte integrity, sequence integrity, governance authorization, and provenance recoverability. It does not prove scientific truth.</t>
    </abstract>
  </front>
  <middle>
    <section numbered="true" toc="default"><name>Status of This Memo</name><t>This is an internal experimental draft included for archival interoperability. It has not been submitted to the IETF and is not an RFC.</t></section>
    <section numbered="true" toc="default"><name>Boundary</name><t>A proof-of-record system proves what was submitted, validated, attested, signed, stored, retrieved, and governed. It does not prove that a scientific claim is true.</t></section>
    <section numbered="true" toc="default"><name>Proof Layers</name><t>A complete proof pack contains schema, conformance, integrity, sequence, governance, and provenance proof components.</t></section>
    <section numbered="true" toc="default"><name>Authority Classes</name><t>Results are tagged as structural, integrity, diagnostic, admissibility, governance, or provenance. Diagnostic and integrity classes do not imply admissibility.</t></section>
    <section numbered="true" toc="default"><name>Security Considerations</name><t>Signatures provide tamper evidence for canonical event cores under a key. They do not prove the truth or scientific admissibility of claims.</t></section>
  </middle>
  <back>
    <references><name>Normative References</name>
      <reference anchor="RFC8785" target="https://www.rfc-editor.org/info/rfc8785"><front><title>JSON Canonicalization Scheme (JCS)</title><author fullname="Anders Rundgren"/><date year="2020"/></front><seriesInfo name="RFC" value="8785"/></reference>
      <reference anchor="RFC8032" target="https://www.rfc-editor.org/info/rfc8032"><front><title>Edwards-Curve Digital Signature Algorithm (EdDSA)</title><author fullname="Simon Josefsson"/><date year="2017"/></front><seriesInfo name="RFC" value="8032"/></reference>
    </references>
  </back>
</rfc>
