GoodShyt Group Inc.

San Francisco CA United States of America deonte@goodshyt.fun https://orcid.org/0009-0005-8586-3650

General Independent Submission provenanceresearch dataJSON This informational scaffold sketches a versioned record for tracking scientific claims, source provenance, evidence classes, uncertainty, falsifiers, replication procedures, and artifact hashes. It is not an IETF standard, has not undergone IETF review, and does not define a wire protocol.

Status and scope This document is a working proposal. The format is intended for local archives and possible future interoperability review. It must not be represented as an IETF-approved specification.

Requirements Language 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 when, and only when, they appear in all capitals, as shown here.

Problem statement Research archives frequently separate claims, citations, code, datasets, test results, and revision history. A compact record can link these items while preserving uncertainty and provenance. This proposal is a data model only; it does not prescribe transport, registry, trust authority, or a scientific evaluation method.

Record fields A record SHOULD include a stable identifier, title, project identifier, claim class, evidence tier, source references, timestamp, revision, uncertainty statement, falsifier, replication protocol, status, and artifact hashes where available. Unknown fields SHOULD remain unknown rather than be inferred. Suggested claim classes are ESTABLISHED, DERIVED, CONJECTURE, ANOMALY, and POTENTIALLY_NOVEL. These labels are descriptive metadata, not certification. Suggested evidence tiers are T1 empirical, T2 derived, T3 rigorous conjecture, and T4 speculative. Implementations may add values using a documented extension mechanism.

Security and privacy considerations Records may expose unpublished research, personal information, credentials, proprietary source code, or sensitive experimental data. Implementations MUST avoid publishing secrets and MUST apply access controls appropriate to the data. Hashes support integrity checks but do not establish source truth, authorship, or scientific validity. Signatures, if added, require key-management and revocation rules.

Integrity and scientific limitations A provenance record does not prove a claim. Evidence classes and confidence labels are self-reported unless supported by review procedures. Dataset versions, analysis code, dependencies, random seeds, and negative results should be retained when applicable. Novelty and priority claims require independent prior-art review.

IANA considerations This scaffold requests no IANA actions.

Open issues Open issues include schema formalization, canonical JSON serialization, controlled vocabularies, extension handling, artifact-signature format, privacy classification, retention, interoperability tests, and whether a genuine community need exists.

Changes since -00 Editorial and tooling-conformance changes only; no technical content was changed.

• Added BCP 14 Requirements Language section (document uses uppercase requirement keywords without the boilerplate; idnits error)
• Added RFC 2119 reference entry
• Added RFC 8174 reference entry
• Removed unreferenced bibliography entries (xml2rfc/idnits "unused reference"): RFCJSON
• Normalized author metadata (full name with ASCII form, initials, organization GoodShyt Group Inc., San Francisco CA postal, email, ORCID URI)
• Added title abbrev "Research Evidence Envelope" for page header (title > 40 chars; xml2rfc warning)
• Updated document date and revision number.