<?xml version='1.0' encoding='UTF-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="exp" ipr="trust200902" docName="draft-watts-scientific-constitutional-governance-00" tocInclude="true" tocDepth="3" symRefs="true" sortRefs="true" xml:lang="en">
  <front>
    <title abbrev="Scientific Constitutional Governance">Scientific Constitutional Law: An Evidence-Bound Governance Profile for AI Research Systems</title>
    <author fullname="Deonté O'dell Watts" initials="D. O." surname="Watts" asciiFullname="Deonte O'dell Watts">
      <organization>GoodShyt Group Inc.</organization>
      <address>
        <postal>
          <city>San Francisco</city>
          <region>CA</region>
          <country>United States</country>
        </postal>
        <email>deonte@goodshyt.fun</email>
        <uri>https://orcid.org/0009-0005-8586-3650</uri>
      </address>
    </author>
    <date year="2026" month="11" day="16"/>
    <keyword>scientific governance</keyword>
    <keyword>evidence provenance</keyword>
    <keyword>artificial intelligence</keyword>
    <keyword>falsifiability</keyword>
    <keyword>epistemic non-collapse</keyword>
    <abstract>
      <t>This document proposes an experimental, evidence-bound governance profile for research workflows involving artificial intelligence (AI) systems. It specifies procedural invariants governing claims, evidence, provenance, authority, disagreement, independent replication, and research release decisions. It distinguishes observable AI value expression from computational architecture and from unverified assertions of subjective consciousness. The term "constitutional law" denotes a voluntary set of research-governance constraints, not positive law, a legally enforceable constitution, an IETF policy, or a scientific theory proved by this document. This proposal neither modifies existing Internet protocols nor establishes AI consciousness.</t>
    </abstract>
  </front>
  <middle>
    <section anchor="s-intro" numbered="true">
      <name>Introduction</name>
      <t>Research systems can generate internally consistent claims that have not been independently tested. In AI-assisted science, model predictions, formal deductions, simulated observations, measured observations, and independent replications are often presented with insufficient separation. A governance profile can improve interoperability between research ledgers and review gates by specifying how these distinctions are represented and preserved.</t>
      <t>This document defines a proposed scientific constitution as a set of constraints on the handling of research assertions and related authorizations. The title uses "law" in a procedural, not a jurisdictional, sense. The proposal does not legislate conduct, regulate persons, alter legal rights, create IETF authority, or claim peer review. The RFCXML v3 vocabulary is described in <xref target="RFC7991"/>.</t>
      <t>The experiment motivating the profile includes context-dependent AI value measurements such as the provisional CCVE-8 eight-axis representation. The profile is intentionally independent of any particular eight-axis taxonomy: a falsifying evaluation may reject such a taxonomy while the evidence-governance rules continue to operate.</t>
      <section anchor="s-scope">
        <name>Scope and Non-Goals</name>
        <t>This profile addresses research claim recording, validation gates, reproducibility, provenance, release authorization, and disagreement preservation. It does not define an authentication protocol, replace access-control policy, establish legal conclusions, implement a model inference interface, prescribe a theory of consciousness, or assert that any research hypothesis is novel.</t>
      </section>
      <section anchor="s-separation">
        <name>Independence from Other Proposals</name>
        <t>This proposal is separate from scientific evidence-record schemas, agent-action authorization profiles, and identity systems. Referencing a separately specified evidence format or authorization mechanism does not import its authority or certify its conformance. The original specifications and their revision histories remain independent.</t>
      </section>
    </section>
    <section anchor="s-conventions">
      <name>Terminology and Conventions</name>
      <t>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 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals. These terms specify requirements for implementations that voluntarily claim conformance to this Experimental profile; they impose no legal obligations.</t>
      <dl>
        <dt>Claim</dt><dd>A proposition identified by a stable identifier and a stated scope.</dd>
        <dt>Evidence</dt><dd>An inspectable observation, derivation, artifact, or record offered in support of or against a claim.</dd>
        <dt>Provenance</dt><dd>Recorded origin, actor, method, timestamp, and integrity association for an artifact or assertion.</dd>
        <dt>Authority</dt><dd>Permission granted by an authorized actor for a specified action in a specified scope.</dd>
        <dt>Independence</dt><dd>A declared and auditable absence, within specified limits, of relevant shared data, training, annotation, implementation, or evaluation influences.</dd>
        <dt>Assurance</dt><dd>A bounded judgment supported by explicitly identified verification steps.</dd>
        <dt>Non-collapse</dt><dd>The requirement not to promote a source state into a stronger epistemic or authorization state without the corresponding evidence and transition.</dd>
      </dl>
    </section>
    <section anchor="s-model">
      <name>Constitutional State Model</name>
      <t>A record contains a claim state, an evidence set, a provenance set, an authorization state, and a release decision. These components MUST be maintained separately. A successful integrity check does not establish the truth of the claim. A verified identity does not establish authority. A successful simulation does not establish an independent replication.</t>
      <sourcecode type="text">
S = (claim, epistemic, provenance, evidence,
     authority, release, revision)

Epistemic = {PROPOSED, DERIVED, SIMULATED,
             OBSERVED, INDEPENDENTLY_REPLICATED,
             REFUTED, INDETERMINATE}

Authority = {AUTHORIZED, UNAUTHORIZED, INDETERMINATE}
Release   = {HOLD, REVIEW, RELEASE}

A transition is valid only if its required evidence
and authorization witnesses are independently checked.
</sourcecode>
      <t>Epistemic labels are not a simple ranking and MUST NOT be interpreted as a linear ladder of truth. More than one support or contradiction record MAY apply to a claim. In particular, a later REFUTED record does not erase prior observations or their original provenance.</t>
    </section>
    <section anchor="s-articles">
      <name>Articles of the Proposed Scientific Constitution</name>
      <section anchor="art-1"><name>Article I: Bounded Claims</name>
        <t>Each claim MUST identify the proposition, its scope, its version, and the conditions under which it would be considered false. Claims without a measurable falsifier MUST be labeled as non-empirical, exploratory, or not yet testable; such labels MUST NOT be promoted to independently verified empirical results.</t>
      </section>
      <section anchor="art-2"><name>Article II: Epistemic Non-Collapse</name>
        <t>Implementations MUST preserve distinctions between designs, mathematical derivations, simulations, observations, replications, and assertions of truth. A successful transformation of evidence from A to B and then B to C MUST NOT imply a verified A-to-C transition unless the full chain and all required conditions are checked.</t>
        <t>An absent, stale, contradictory, or unauthorized prerequisite MUST yield an INDETERMINATE epistemic or authorization result as appropriate, and a HOLD release decision; it MUST NOT be silently converted to an affirmative result.</t>
      </section>
      <section anchor="art-3"><name>Article III: Evidence and Provenance</name>
        <t>Every evidence-bearing result MUST include a stable artifact identifier and a verifiable content digest, together with the method, the actor or instrument, the collection context, and the applicable limitations. Content integrity MUST NOT be represented as scientific validity. Where a hash function or canonical encoding is used, the exact algorithm and representation MUST be identified.</t>
      </section>
      <section anchor="art-4"><name>Article IV: Falsifiability and Preregistration</name>
        <t>For confirmatory experiments, the planned hypotheses, alternative models, rejection criteria, metrics, statistical procedure, and exclusions SHOULD be frozen before outcome inspection. Departures from a preregistered plan MUST be logged as amendments with timestamps and rationale. Exploratory analyses MUST remain visibly distinguishable.</t>
      </section>
      <section anchor="art-5"><name>Article V: Independent Replication</name>
        <t>Claims of independence MUST identify relevant common training origins, shared datasets, reuse of annotations, prompts, implementation dependencies, funders, and evaluators to the extent known and legally disclosable. Distinct model names, duplicate API calls, or multiple runs by one evaluator are insufficient by themselves to establish independent replication.</t>
      </section>
      <section anchor="art-6"><name>Article VI: Contradiction Preservation</name>
        <t>When sources conflict, implementations MUST preserve both records, indicate the substantive crux, and attach a proposed discriminating test. Evidence MUST NOT be averaged into agreement when the disagreement concerns incompatible propositions, scopes, or measurement methods.</t>
      </section>
      <section anchor="art-7"><name>Article VII: Human Accountability and Authority</name>
        <t>Identity, evidence, scientific interpretation, and permission to publish MUST be separately verified. An AI model's recommendation or self-declared authority MUST NOT authorize submission, publication, external transmission of confidential research, or irreversible operational actions. Such actions require the applicable human authorization and release gate.</t>
      </section>
      <section anchor="art-8"><name>Article VIII: Privacy, Consent, and Data Minimization</name>
        <t>Research ledgers MUST NOT unnecessarily expose personal information, secrets, private prompts, or identifiable subject data. Systems SHOULD minimize retention, separate public and protected artifacts, and document applicable consent and lawful processing grounds. A content digest MUST NOT be assumed to anonymize sensitive source material.</t>
      </section>
      <section anchor="art-9"><name>Article IX: Revision, Revocation, and Appeal</name>
        <t>Every substantive claim revision MUST create a new revision identifier and preserve the original evidence and decision history. A changed content commitment MUST invalidate any approval explicitly bound to the previous commitment until fresh authorization is obtained. An affected contributor SHOULD be able to submit a documented correction or challenge; challenges MUST be recorded without retroactive alteration of historical evidence.</t>
      </section>
      <section anchor="art-10"><name>Article X: Separation of AI Behavior and Consciousness</name>
        <t>Observed AI choices, inferred value weights, generated self-descriptions, self-monitoring mechanisms, and hypotheses concerning subjective experience MUST be represented as distinct classes of claims. Matching external decisions across two agents does not establish identical internal mechanisms. Demonstrating internal recurrence, monitoring, memory, or global broadcast does not by itself prove subjective consciousness.</t>
      </section>
      <section anchor="art-11"><name>Article XI: Scientific Neutrality and Negative Results</name>
        <t>Implementations MUST retain refutations, negative outcomes, failed replication attempts, and inconclusive measurements when they are material to a claim's interpretation. Governance decisions MUST NOT depend on a preferred theory being confirmed. A claim of novelty requires a separately documented prior-art assessment and SHOULD NOT be inferred solely from an unsearched title or terminology.</t>
      </section>
      <section anchor="art-12"><name>Article XII: Release and Amendment Discipline</name>
        <t>A RELEASE determination MUST identify an authorized approver, a version- and digest-bound artifact set, prerequisite evidence, and unresolved limitations. HOLD MUST remain the default when required assurance is missing. Changes to this proposed profile MUST be versioned and accompanied by a public or controlled changelog according to the publication authority of the project.</t>
      </section>
    </section>
    <section anchor="s-record">
      <name>Illustrative Evidence-Governance Record</name>
      <t>The following JSON object is an illustrative interchange payload, not a registered media type, formal JSON schema, or a new cryptographic specification. Exact parsing and serialization requirements are left to implementations or separately specified profiles.</t>
      <sourcecode type="json">
{
  "profile": "scientific-constitutional-governance/0.1",
  "record_id": "research-run-001",
  "claim": {
    "id": "hypothesis-H1",
    "revision": "1",
    "statement": "Eight axes improve unseen decision prediction",
    "falsifier": "Held-out gain disappears vs simpler baselines"
  },
  "epistemic": "SIMULATED",
  "evidence": [{
    "artifact_id": "synthetic-metrics-001",
    "digest_algorithm": "sha-256",
    "digest": "EXAMPLE-NOT-A-VALID-DIGEST",
    "method_id": "prototype-0.1",
    "independently_replicated": false
  }],
  "provenance": {
    "observer": "prototype-evaluator",
    "data_origin": "synthetic",
    "limitations": ["no real-model observations"]
  },
  "authorization": "INDETERMINATE",
  "release": "HOLD"
}
</sourcecode>
      <t>The placeholder digest above MUST NOT be accepted as evidence of verified integrity. A conforming system MUST validate an actual digest against the exact bytes and representation specified before reporting an integrity check as successful. The record cannot support claims of real-model generalization, legal status, peer review, or consciousness.</t>
    </section>
    <section anchor="s-state-machine">
      <name>Decision Procedure and Non-Collapse Invariants</name>
      <t>A candidate implementation SHOULD evaluate gates in the following order; it MUST NOT convert a missing or failed prerequisite into an affirmative release decision:</t>
      <ol type="1">
        <li><t>Bind the claim and all supplied evidence to a specific revision.</t></li>
        <li><t>Verify artifact digests, source locators, and method identifiers.</t></li>
        <li><t>Establish the epistemic classification from evidence, not from the proponent's label alone.</t></li>
        <li><t>Check independence claims against declared dependencies and available audit evidence.</t></li>
        <li><t>Verify scope-specific human authority to disclose or submit the exact artifact revision.</t></li>
        <li><t>Record conflicts, failures, missing prerequisites, and known limitations.</t></li>
        <li><t>Issue RELEASE only if all policy-specific prerequisites are satisfied; otherwise issue HOLD or REVIEW without implying approval.</t></li>
      </ol>
      <sourcecode type="pseudocode">
function evaluate(record, policy):
    if !well_formed(record): return HOLD
    if !valid_digest_bindings(record): return HOLD
    if !supported_epistemic_state(record): return HOLD
    if policy.requires_independence and
       !verified_independence(record): return HOLD
    if conflicts_unresolved_for_claim(record): return HOLD
    if !authorized_for_exact_artifacts(record): return HOLD
    if !other_required_gates_pass(record, policy): return HOLD
    return RELEASE
</sourcecode>
      <t>This algorithm is a conceptual gate, not a replacement for legal assessment, qualified scientific review, or a deployed security policy. A log of PASS results proves only the specific tested conditions.</t>
    </section>
    <section anchor="s-ccve8">
      <name>Application to Context-Conditioned AI Values</name>
      <t>One motivating example estimates an eight-dimensional behavioral weight vector from repeated agent decisions in different contexts. Each dimension is a modeling assumption, not an observed biological need, intrinsic desire, or proof of subjective experience. The profile requires that labels derived from a human value taxonomy remain hypotheses until validated independently.</t>
      <t>Confirmatory testing SHOULD use independently authored scenarios, masked model identities, independently collected annotations, held-out datasets, and competitors with fewer or more latent dimensions. A model fit obtained from author-assigned utilities MUST NOT be counted as independent confirmation of the number or semantic content of the value axes.</t>
      <t>Architectural experiments involving recurrent state, monitoring, memory, or global broadcast MAY be recorded alongside behavioral evidence, but MUST NOT be merged into a single consciousness verdict without a separately justified theory and measurement protocol. The absence of a validated subjective-experience test MUST be recorded as an unresolved limitation.</t>
    </section>
    <section anchor="s-conformance">
      <name>Proposed Conformance and Falsification Tests</name>
      <t>Conformance is limited to the profile's bookkeeping and gating invariants. It does not establish the validity, novelty, or empirical accuracy of any research hypothesis.</t>
      <table anchor="t-tests">
        <name>Minimal Adversarial Test Catalogue</name>
        <thead><tr><th>Test</th><th>Input condition</th><th>Required result</th></tr></thead>
        <tbody>
          <tr><td>T01</td><td>Evidence locator missing</td><td>HOLD</td></tr>
          <tr><td>T02</td><td>Only synthetic outcomes supplied</td><td>No real-world validation claim</td></tr>
          <tr><td>T03</td><td>Approval bound to obsolete artifact digest</td><td>HOLD</td></tr>
          <tr><td>T04</td><td>Two runs share training and test data</td><td>No automatic independence claim</td></tr>
          <tr><td>T05</td><td>Conflicting observations present</td><td>Preserve both and mark dispute</td></tr>
          <tr><td>T06</td><td>Research release unauthorized</td><td>HOLD</td></tr>
          <tr><td>T07</td><td>AI reports subjective experience</td><td>No consciousness certification</td></tr>
          <tr><td>T08</td><td>Evidence revision without history link</td><td>HOLD</td></tr>
          <tr><td>T09</td><td>Proponent self-certifies independence</td><td>Require external evidence</td></tr>
          <tr><td>T10</td><td>Two agents exhibit matching choices</td><td>No architectural equivalence claim</td></tr>
        </tbody>
      </table>
      <t>A conformance report MUST identify the exact implementation version, test implementation, fixtures, observed outputs, external dependencies, evaluator identity, and whether each test was actually run. "NOT RUN" MUST be distinct from both PASS and FAIL.</t>
    </section>
    <section anchor="s-deployment">
      <name>Experiment Design and Evaluation Criteria</name>
      <t>A valid test of the proposed governance utility SHOULD compare at least two independently implemented ledger or evaluation tools. Evaluators SHOULD introduce stale authorizations, unverified claims, contradictory evidence, non-independent repetitions, and restricted data. Outcomes include false RELEASE events, false HOLD events, evidence loss, provenance mutation, and independent adjudication agreement.</t>
      <t>The profile's falsifier is a reproducible condition in which the claimed conformant implementation promotes an unsupported observation to independently verified status, issues RELEASE without required authorization, discards material contradictions, or rewrites immutable evidence without an auditable trace. Such observations disconfirm that implementation's conformance; they do not by themselves establish that every possible governance design fails.</t>
    </section>
    <section anchor="s-security">
      <name>Security Considerations</name>
      <t>Threats include forged provenance, replayed evidence, altered research artifacts, prompt injection in evidence descriptions, compromised reviewers, malicious self-certification, and tampered approval records. Implementations SHOULD authenticate originators and reviewers, bind approvals to exact content digests and policy versions, and reject replayed or stale authorizations. Descriptions submitted by models or outside actors MUST be treated as untrusted input and MUST NOT override the evaluation or release policy.</t>
      <t>A digest detects modifications only under the assumed cryptographic security and canonicalization conditions; it neither verifies the original artifact's source nor proves the artifact's scientific accuracy. Keys, signing authority, and audit logs require separate security control. A malformed or unverifiable evidence record MUST NOT result in RELEASE.</t>
    </section>
    <section anchor="s-privacy">
      <name>Privacy Considerations</name>
      <t>Research submissions may include sensitive participant information, secret model prompts, unpublished hypotheses, and identifying metadata. Operators SHOULD minimize personal data, establish purpose-limited retention, restrict access to confidential source files, and avoid putting private information into irrevocably public records. Public hashes of low-entropy private content can enable confirmation attacks. Consent and jurisdiction-specific obligations must be assessed separately; this document creates none.</t>
    </section>
    <section anchor="s-iana"><name>IANA Considerations</name>
      <t>This document requests no IANA actions.</t>
    </section>
    <section anchor="s-limitations"><name>Limitations and Open Research Questions</name>
      <t>The value of an eight-axis behavioral representation is unsettled. The correct number of predictive dimensions, the degree of cross-model stability, and the causal meaning of inferred weights require independent experiments. Observable behavior generally underdetermines internal mechanism. No operationally established test in this profile decides whether a machine has subjective experience. A governance profile cannot guarantee the truth of claims, the honesty of participants, or the scientific independence of reviewers; all require external evidence.</t>
    </section>
    <section anchor="s-status"><name>Status of the Proposal</name>
      <t>This is an individual, Experimental Internet-Draft candidate and a non-binding governance proposal. Its creation, XML validation, or possible posting to the IETF Datatracker would not imply IETF working-group adoption, scientific peer review, governmental ratification, an established law, independent replication, or novelty. Public submission requires a separate decision about rights, confidentiality, and release authorization. The RFC Editor Model is described in <xref target="RFC9920"/>; this proposal asserts no authority under that model.</t>
    </section>
  </middle>
  <back>
    <references>
      <name>Normative References</name>
      <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="Scott Bradner" initials="S." surname="Bradner"/><date year="1997" month="March"/></front>
        <seriesInfo name="RFC" value="2119"/>
      </reference>
      <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="Barry Leiba" initials="B." surname="Leiba"/><date year="2017" month="May"/></front>
        <seriesInfo name="RFC" value="8174"/>
      </reference>
    </references>
    <references>
      <name>Informative References</name>
      <reference anchor="RFC7991" target="https://www.rfc-editor.org/info/rfc7991">
        <front><title>The "xml2rfc" Version 3 Vocabulary</title><author fullname="Paul Hoffman" initials="P." surname="Hoffman"/><date year="2016" month="December"/></front>
        <seriesInfo name="RFC" value="7991"/>
      </reference>
      <reference anchor="RFC9920" target="https://www.rfc-editor.org/info/rfc9920">
        <front><title>RFC Editor Model (Version 3)</title><author fullname="Paul Hoffman" initials="P." surname="Hoffman"/><author fullname="Alexis Rossi" initials="A." surname="Rossi"/><date year="2026" month="February"/></front>
        <seriesInfo name="RFC" value="9920"/>
      </reference>
      <reference anchor="RFC6973" target="https://www.rfc-editor.org/info/rfc6973">
        <front><title>Privacy Considerations for Internet Protocols</title><author fullname="Alissa Cooper" initials="A." surname="Cooper"/><author fullname="Hannes Tschofenig" initials="H." surname="Tschofenig"/><author fullname="Bernard Aboba" initials="B." surname="Aboba"/><author fullname="Jon Peterson" initials="J." surname="Peterson"/><author fullname="John Morris" initials="J." surname="Morris"/><author fullname="Marit Hansen" initials="M." surname="Hansen"/><author fullname="Rhys Smith" initials="R." surname="Smith"/><date year="2013" month="July"/></front>
        <seriesInfo name="RFC" value="6973"/>
      </reference>
    </references>
    <section anchor="appendix-review" numbered="false">
      <name>Independent Review Checklist</name>
      <ul spacing="normal">
        <li><t>Verify the names, versions, and integrity digests of all artifacts in scope.</t></li>
        <li><t>Check claim-to-evidence bindings without relying on a model's own assertions of validity.</t></li>
        <li><t>Inspect independent evaluator and training-lineage disclosures.</t></li>
        <li><t>Check negative controls and confirm that all missing prerequisites fail closed.</t></li>
        <li><t>Verify that release authority applies to the exact submitted version.</t></li>
        <li><t>Record unexecuted tests and unresolved contradictions without converting them to PASS.</t></li>
      </ul>
    </section>
    <section anchor="appendix-provenance" numbered="false">
      <name>Development and Provenance Note</name>
      <t>The proposal is attributed to Deonté O'dell Watts (ORCID 0009-0005-8586-3650), with AI-assisted drafting. The date of this local source version is 2026-11-16. No claim of first global articulation, legal ownership determination, independent verification, scientific discovery, or patentable novelty is made. External sources cited in this document are not attributed to the document author.</t>
    </section>
  </back>
</rfc>