Network Working Group D. Watts Internet-Draft GoodShyt Group Inc. Intended status: Informational 16 November 2026 Expires: 20 May 2027 A Provenance-Bounded Record Format for Scientific Data draft-watts-scientific-data-record-00 Abstract 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. Status of This Draft This note is to be removed before publishing as an RFC. This is an individual, unreviewed design proposal. No experimental result, priority claim, or peer-review outcome is asserted. The example in Section 6 uses synthetic values and placeholder digests. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 20 May 2027. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. Watts Expires 20 May 2027 [Page 1] Internet-Draft Scientific Data Record November 2026 This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Non-Goals . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions and Definitions . . . . . . . . . . . . . . . . . 3 3. Data Model . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1. The source Object . . . . . . . . . . . . . . . . . . . . 4 3.2. Claim Classes . . . . . . . . . . . . . . . . . . . . . . 5 3.3. Evidence Tiers . . . . . . . . . . . . . . . . . . . . . 5 3.4. Check Results . . . . . . . . . . . . . . . . . . . . . . 5 3.5. Authority Classes . . . . . . . . . . . . . . . . . . . . 5 3.6. Provenance . . . . . . . . . . . . . . . . . . . . . . . 6 3.7. States . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Canonicalization and Digests . . . . . . . . . . . . . . . . 6 5. Processing Rules . . . . . . . . . . . . . . . . . . . . . . 6 5.1. Validation . . . . . . . . . . . . . . . . . . . . . . . 6 5.2. Admissibility . . . . . . . . . . . . . . . . . . . . . . 7 5.3. Append-Only History . . . . . . . . . . . . . . . . . . . 7 6. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 9 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 10.1. Normative References . . . . . . . . . . . . . . . . . . 9 10.2. Informative References . . . . . . . . . . . . . . . . . 10 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 10 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10 1. Introduction 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. Watts Expires 20 May 2027 [Page 2] Internet-Draft Scientific Data Record November 2026 1.1. Scope The format covers: the record data model (Section 3), canonicalization and digests (Section 4), and processing rules (Section 5). It is transport-agnostic and storage-agnostic. 1.2. Non-Goals * Certifying that a claim is true. A valid record whose integrity check passes can still describe a false claim. * Defining statistical methods, experimental designs, or domain- specific data formats. * Asserting novelty or priority. The format has no member for either. 2. Conventions and Definitions 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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. Record: A JSON object conforming to Section 3. Source: The immutable bytes (data file, notebook, export) from which a claim is drawn, identified by a digest. Claim: A statement derived from, or about, a source. Falsifier: A stated observation or test result that, if obtained, would show the claim to be wrong. Check: A named validation step with a result of PASS, FAIL, or NOT_RUN. Authority class: The kind of question a check answers (see Section 3.5). 3. Data Model A Record is a JSON object [RFC8259]. Table 1 lists its members. Unknown members MUST be ignored for processing but MUST be included when computing the record digest (Section 4). Watts Expires 20 May 2027 [Page 3] Internet-Draft Scientific Data Record November 2026 +================+========+=============+==========================+ | Member | Type | Requirement | Meaning | +================+========+=============+==========================+ | schema_version | string | REQUIRED | Format version. This | | | | | document defines "1". | +----------------+--------+-------------+--------------------------+ | record_id | string | REQUIRED | Identifier unique within | | | | | the issuing archive. | +----------------+--------+-------------+--------------------------+ | source | object | REQUIRED | Source identifier and | | | | | digest. | +----------------+--------+-------------+--------------------------+ | claim | object | REQUIRED | Claim text and claim | | | | | class. | +----------------+--------+-------------+--------------------------+ | evidence_tier | string | REQUIRED | One of the tiers in | | | | | Section 3.3. | +----------------+--------+-------------+--------------------------+ | falsifier | string | REQUIRED | Non-empty falsifier | | | | | statement. | +----------------+--------+-------------+--------------------------+ | checks | array | REQUIRED | Zero or more check | | | | | results. May be empty. | +----------------+--------+-------------+--------------------------+ | provenance | array | REQUIRED | Entity, activity, and | | | | | agent references. | +----------------+--------+-------------+--------------------------+ | state | string | REQUIRED | One of the states in | | | | | Section 3.7. | +----------------+--------+-------------+--------------------------+ | created_at | string | REQUIRED | Timestamp in the format | | | | | of [RFC3339]. | +----------------+--------+-------------+--------------------------+ | record_digest | object | REQUIRED | Digest of the record | | | | | itself (Section 4). | +----------------+--------+-------------+--------------------------+ Table 1: Record Members 3.1. The source Object 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. Watts Expires 20 May 2027 [Page 4] Internet-Draft Scientific Data Record November 2026 3.2. Claim Classes The "claim" object has a REQUIRED string member "text" and a REQUIRED string member "class". The class MUST be one of: ESTABLISHED: The claim restates a result already reported with empirical support, with the supporting source identified. DERIVED: The claim follows from the identified source by a stated calculation or argument. CONJECTURE: The claim is a hypothesis not yet tested. ANOMALY: The claim reports an unexplained observation or a negative result. A record's class describes what kind of statement the claim is. It does not describe how likely the claim is to be true. 3.3. Evidence Tiers 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. 3.4. Check Results 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". 3.5. Authority Classes 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. Watts Expires 20 May 2027 [Page 5] Internet-Draft Scientific Data Record November 2026 3.6. Provenance 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 [PROV-O]. "ref" is an identifier or URI for the referenced item. 3.7. States 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 Section 5.2. 4. Canonicalization and Digests The record digest is computed as follows. 1. Remove the "record_digest" member from the record. 2. Serialize the remainder using the JSON Canonicalization Scheme [RFC8785]. 3. Compute SHA-256 over the resulting bytes [RFC6234]. 4. Encode as lowercase hexadecimal and store in "record_digest.value", with "record_digest.alg" set to "sha-256". 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. 5. Processing Rules Processing is fail-closed: an unknown, missing, or not-run condition blocks a state transition and is never treated as a positive finding. 5.1. Validation A processor MUST reject a record that: * lacks a REQUIRED member or has a member of the wrong type; * has a "falsifier" that is empty or consists only of whitespace; * carries a "class", "evidence_tier", "state", "result", or "authority_class" value outside the sets defined in this document; or Watts Expires 20 May 2027 [Page 6] Internet-Draft Scientific Data Record November 2026 * fails the digest verification of Section 4. 5.2. Admissibility 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. 5.3. Append-Only History 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. 6. Example 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 Section 4. Watts Expires 20 May 2027 [Page 7] Internet-Draft Scientific Data Record November 2026 { "schema_version": "1", "record_id": "urn:example:record:0001", "source": { "source_id": "urn:example:source:values-v1", "digest": { "alg": "sha-256", "value": "" }, "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": "" } } The record is in state "BLOCKED" because the required admissibility check was not run, even though the structural check passed. Watts Expires 20 May 2027 [Page 8] Internet-Draft Scientific Data Record November 2026 7. Security Considerations 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. Canonicalization differences can cause digest mismatches or, if implemented incorrectly, collisions between distinct records. Implementations MUST use a conforming [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. 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. 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 Section 3.5 and Section 5.2. 8. Privacy Considerations 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. 9. IANA Considerations This document has no IANA actions. 10. References 10.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . Watts Expires 20 May 2027 [Page 9] Internet-Draft Scientific Data Record November 2026 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, . [RFC6234] Eastlake 3rd, D. and T. Hansen, "US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF)", RFC 6234, DOI 10.17487/RFC6234, May 2011, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data Interchange Format", STD 90, RFC 8259, DOI 10.17487/RFC8259, December 2017, . [RFC8785] Rundgren, A., Jordan, B., and S. Erdtman, "JSON Canonicalization Scheme (JCS)", RFC 8785, DOI 10.17487/RFC8785, June 2020, . 10.2. Informative References [PROV-O] W3C, "PROV-O: The PROV Ontology", W3C Recommendation, April 2013, . Acknowledgements None. Author's Address Deonté O'dell Watts GoodShyt Group Inc. Email: deonte@goodshyt.fun URI: https://orcid.org/0009-0005-8586-3650 Watts Expires 20 May 2027 [Page 10]