| Internet-Draft | Scientific Constitutional Evidence Gates | November 2026 |
| Watts | Expires 20 May 2027 | [Page] |
This document proposes Scientific Constitutional Evidence Gates (SCEG), a JSON exchange profile for recording and evaluating whether evidence-bearing research claims may cross a declared governance boundary. It specifies typed evidence states, an explicit transition decision procedure, provenance and policy bindings, and independently verifiable receipts. The design prevents integrity checks, structural conformance, or matching scientific invariants from being silently promoted into scientific truth, independent reproduction, or institutional authority.¶
The term "constitutional law" denotes internal, machine-checkable governance constraints; this proposal does not create state law, legal rights, institutional authority, scientific certification, or IETF consensus. It is an individual Informational Internet-Draft intended to support interoperable, falsifiable research workflows.¶
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 (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
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. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
Networked scientific workflows distribute claims, models, analysis code, datasets, evaluation records, and decisions among autonomous and human participants. A machine-readable evidence record may be internally consistent while its scientific interpretation remains unconfirmed. A proof of byte integrity cannot establish the truth of a proposition or a person's legal authority to act on that proposition.¶
This document introduces a deliberately narrow transition-boundary profile. An evaluation request binds a specific claim revision to a specific evidence-policy revision, named gate outcomes, and an explicitly requested state change. A receiver independently recomputes the decision and validates the authority and integrity of the receipt before permitting the state change.¶
SCEG is a governance interchange profile for existing systems, not a new transport protocol, a law of physics, a general scientific discovery, or a replacement for professional or legal judgment. No new IANA protocol registration is requested.¶
This text is a proposed individual Internet-Draft, not an RFC, a formal IETF standard, or an endorsed scientific constitution. Any apparent overlap with constitutional or legal vocabulary is metaphorical unless separately authorized under applicable law.¶
In scope are exchange syntax, evidence-state semantics, transition authorization, receipt integrity, version binding, and machine-checkable negative tests. Out of scope are determining empirical truth, judicial admissibility, scientific peer-review competence, patent ownership, human-rights interpretation, and delegating unbounded decision authority to AI agents.¶
The companion individual Internet-Draft on Scientific Admissibility Evidence Records describes research evidence metadata; this proposal adds explicit transition and authority checks rather than superseding that record model.¶
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL are to be interpreted as described in [RFC2119] and [RFC8174] when, and only when, they appear in all capitals.¶
An implementation that claims conformance with SCEG version 1 MUST enforce all the following invariants for its accepted transitions.¶
SCEG messages are JSON objects as defined by RFC 8259. The top-level profile identifier for this draft is the literal string "SCEG-1". The fields below form the receipt core. A proof field, when present, is excluded from the receipt core before canonicalization to prevent circular signing.¶
The mandatory fields are profile, record_id, claim, policy, checks, decision, transition, and event. Implementations MUST reject duplicate JSON member names, unknown mandatory profile versions, invalid enum values, unknown gate names in the required_gates set, and more than one entry for the same gate.¶
Claim contains id, revision, statement, scope, and epistemic_state. Policy contains id, revision, digest, and required_gates. Checks is a set of name, state, and evidence reference tuples. Transition contains from, requested, and committed states. Event contains sequence, previous_digest, issued_at, issuer, and authority_epoch.¶
The policy digest and all required-gate names MUST be obtained from an independently trusted policy record. A self-declared policy digest alone MUST NOT establish authority. Time values MUST use the RFC 3339 format; a consumer MUST apply an explicit freshness and clock-skew policy rather than assuming the timestamp is reliable.¶
JSON syntax follows [RFC8259]. Date-time syntax follows [RFC3339].¶
The policy evaluator MUST first validate syntax, field binding, the current claim revision, the policy digest, event sequence, previous event binding, authority epoch, and evidence references. A malformed object is INVALID and MUST NOT authorize any transition.¶
For every gate declared mandatory in the trusted policy: a FAIL produces DENY; absent any FAIL, at least one UNKNOWN or NOT_RUN produces INDETERMINATE; only an all-PASS gate vector can produce provisional ALLOW. Additional mandatory conditions including independent reviewer qualification MUST appear as explicit policy gates.¶
Provisional ALLOW MUST be downgraded to INDETERMINATE when the trusted signing key, issuer entitlement, independent custody requirement, or required signature is absent or unverified. A demonstrably invalid required signature or revoked authorization produces DENY. An action sink MUST accept a promotion only after a final ALLOW was independently recomputed immediately before effect commitment.¶
For DENY or INDETERMINATE, transition.committed MUST equal transition.from. For a final ALLOW, transition.committed MAY equal transition.requested only if that edge is explicitly authorized by the trusted state-transition policy. Repeated or replayed receipts MUST NOT produce an additional effect.¶
def decision(required, checks, proof, context):
if not context.is_well_formed_and_bound():
return "INVALID"
states = [checks.get(name, "NOT_RUN") for name in required]
if any(state == "FAIL" for state in states):
return "DENY"
if any(state in ("UNKNOWN", "NOT_RUN") for state in states):
return "INDETERMINATE"
if not context.edge_is_authorized():
return "DENY"
if proof.is_invalid_or_revoked():
return "DENY"
if not proof.is_verified_by_trusted_custodian():
return "INDETERMINATE"
return "ALLOW"
# This pseudocode is illustrative: a real validator also enforces
# freshness, replay prevention, and authoritative external gate evidence.¶
The canonical receipt core is the complete SCEG JSON object excluding its optional proof member. A conforming issuer MUST serialize the core using the JSON Canonicalization Scheme defined by RFC 8785 before computing the core digest or signing. Values requiring greater precision than interoperable JSON numbers MUST be represented as strings with declared units.¶
If a digest is emitted, it MUST be the lowercase hexadecimal SHA-256 of the UTF-8 bytes consisting of the ASCII domain-separation string "SCEG-1" followed by a newline and the JCS-serialized core. The lowercase hexadecimal digest MUST be prefixed with "sha256:". Implementations MUST reject mismatched digests.¶
For a JWS-based proof, the JWS payload MUST be exactly the JCS-serialized core. The selected JWS algorithm, key identifier, and issuer authorization MUST be checked against independently provisioned trust material. JWS verification alone proves a statement was signed by a key; it does not prove the signer's scientific competence, independence, or legal authority. A consumer MUST reject signatures whose protected algorithm does not match policy expectations.¶
A consumer SHOULD impose finite limits on JSON message length, nesting depth, number of gates and evidence references, time skew, and verification effort. There is no mandated universal maximum in this informational profile.¶
The base lifecycle states are PROPOSED, EVALUATED, INDEPENDENTLY_REPRODUCED, RETRACTED, and RETIRED. This lifecycle does not assert scientific truth; an EVALUATED claim may be false, and a reproduction report may subsequently be retracted.¶
A claim MAY move from PROPOSED to EVALUATED after all policy-specified method and review gates pass. It MAY move to INDEPENDENTLY_REPRODUCED only when a trusted, distinct custodian documents the independent result and the applicable authorization gate passes. RETRACTED and RETIRED are not interchangeable; the chosen policy MUST specify the distinction and effects.¶
After a superseding policy revision, claim revision, key revocation, or authority-epoch change, a consumer MUST re-evaluate receipts before authorizing new effects. Revocation cannot undo effects already completed; a protocol MUST NOT claim retrospective erasure or external system compliance solely from a new revocation record.¶
Each scientific claim SHOULD carry a falsifier and measurement plan, including sampling and calibration requirements appropriate to the field. Falsifier data MUST be preserved even when it conflicts with the promotion request.¶
For communication-benchmark claims, instruction regimes MUST face the same held-out tasks, matched information budget, independently controlled answer labels, and a preregistered analysis. A local synthetic smoke test, a white-box decoder, or a clean cryptographic receipt MUST NOT be promoted to independent scientific validation.¶
An admissibility record MUST preserve contradictory evidence and identify the decisive test. If that test is NOT_RUN, the claim remains conjectural regardless of other metadata. Scientific novelty is a separate literature and priority assessment and MUST NOT be inferred from new file names, local timestamps, or authorship claims.¶
The following unsigned example demonstrates an indeterminate evaluation. The value of policy.digest is the SHA-256 of a separate illustrative policy object consisting only of id, revision, and required_gates, canonicalized with JCS. This example does not provide a signing proof, an independently qualified evaluator, or trusted policy distribution, and MUST NOT authorize the requested promotion.¶
{
"profile": "SCEG-1",
"record_id": "urn:example:sceg:record:001",
"claim": {
"id": "urn:example:claim:001",
"revision": 1,
"statement": "A synthetic invariance-first curriculum improves held-out decoding.",
"scope": "Synthetic four-dimensional development benchmark",
"epistemic_state": "CONJECTURE"
},
"policy": {
"id": "urn:example:policy:001",
"revision": 1,
"digest": "sha256:f5dd3d611ddecc03f440958fcf4096ab7451b215eb11154f58137ceeace11c98",
"required_gates": [
"integrity",
"method",
"independence",
"authority"
]
},
"checks": [
{
"name": "integrity",
"state": "PASS",
"evidence": [
"urn:example:artifact:hash"
]
},
{
"name": "method",
"state": "PASS",
"evidence": [
"urn:example:run:local"
]
},
{
"name": "independence",
"state": "NOT_RUN",
"evidence": []
},
{
"name": "authority",
"state": "UNKNOWN",
"evidence": []
}
],
"decision": "INDETERMINATE",
"transition": {
"from": "PROPOSED",
"requested": "INDEPENDENTLY_REPRODUCED",
"committed": "PROPOSED"
},
"event": {
"sequence": 1,
"previous_digest": null,
"issued_at": "2026-11-16T00:00:00Z",
"issuer": "urn:example:issuer:local",
"authority_epoch": 1
}
}¶
An implementation claiming SCEG-1 conformance MUST demonstrate the following behavior under the same trusted policy and execution boundary. A positive signature test requires an external, independently provisioned key and is not represented by the unsigned example above.¶
Research records may contain human-subject data, personnel identity, proprietary code, unpublished hypotheses, or legally protected documents. Publishers MUST enforce explicit release authorization and applicable confidentiality restrictions before transmitting protected artifacts. A digest or evidence URI can itself leak a relationship or sensitive fact.¶
Producers SHOULD prefer least-disclosure proofs, pseudonymous actor identifiers where lawful, short-lived authenticated access, and separated public and private record views. Deletion, retention, and redaction policies remain external institutional and legal responsibilities; an append-only ledger is not a privacy-law exemption.¶
Threats include forged evaluator identities, replayed or stale receipts, rewritten policy digests, key substitution, maliciously duplicated JSON keys, malicious evidence URIs, time-of-check/time-of-use races, coerced peer review, prompt-injected research artifacts, and incorrect assumption that a signature implies authorization.¶
A recipient MUST verify policy, key binding, evidence provenance, signatures, replay state, and current authority at the actual action boundary. External artifact dereferencing MUST use established SSRF, content-size, MIME-type, and sandbox protections. The policy MUST govern whether an UNKNOWN state can ever trigger a low-risk diagnostic action; it MUST NOT be silently treated as permission for a scientific promotion.¶
Two implementations agreeing on a forged result is not independent validation. The protocol cannot make false evidence truthful, prevent collusion, or guarantee scientific reliability. Independent review and legal authority must be established separately.¶
This document requests no IANA actions. The JSON profile identifier is a document-local literal, not an allocated URN namespace or registered media type. A future standards-track revision could request suitable IANA registrations after design review.¶
The following remain unresolved for a standards or research claim: a frozen interoperability corpus, independently implemented validators, independently controlled secret-key and policy custody, instrumented action sinks with concurrency and revocation races, evaluation of independent scientific-review competence, jurisdictional restrictions, and a documented IETF Trust and IPR review.¶
Negative test vectors are design requirements, not a completed third-party conformance program. No independent evaluator acceptance, production deployment, or scientific superiority result is implied by this Internet-Draft candidate.¶
In a four-dimensional binary hypercube, A = {0, 1, 2, 12} and B = {0, 1, 6, 7} share the same multiset of six pairwise Hamming distances (1, 1, 2, 2, 3, 3). Their induced distance-one degree multisets differ: (0, 1, 1, 2) for A versus (1, 1, 1, 1) for B. Therefore no coordinate permutation plus bitwise-translation hypercube isometry maps A to B. Equal coarse signatures do not justify an equivalence claim.¶
This is a derived finite combinatorial counterexample; it is not a novel theorem, an extraterrestrial observation, or a legal precedent.¶
Research sponsor and proposed author: Deonté O'dell Watts (ORCID 0009-0005-8586-3650), GoodShyt Group Inc. The text and example profile were assembled with AI assistance and require independent editorial, legal/IPR, and interoperability review before public release. The author's affiliation does not confer IETF endorsement or priority over earlier work.¶