Codex Resonance
/
Codex Commons
/
📚
Codex Structural Vocabulary v1.1 — Revision Candidate
📚

Codex Structural Vocabulary v1.1 — Revision Candidate

Artefact: Codex Structural Vocabulary

Candidate Version: 1.1

Date: 29 September 2026

Standing: INTERNAL — REVISION CANDIDATE. NOT PUBLISHED. Does not supersede v1.0.

Prior published version: 📚Codex Structural Vocabulary v1.0

Revision purpose

Prepare a minimal semantic-boundary revision of the published Structural Vocabulary so it aligns with the accepted Commons kernel without importing internal CR/Arqua theory or changing the three-profile kernel.

Proposed changes

1. Authority

Proposed v1.1 definition

Authority is externally or institutionally constituted standing to make, maintain or govern a specified class of claim, interpretation, decision or artefact within a declared scope. A representation of authority does not itself create, transfer or expand that authority.

Normative note

Authority should be attributed to its applicable source, proposition, scope and context. Publication or stewardship within Codex Commons establishes Commons publication/stewardship standing only; it does not establish legal, regulatory, clinical, cultural, operational or enterprise authority.

2. Canonical Artefact

Proposed v1.1 definition

A canonical artefact is a published artefact that holds canonical Codex Commons standing for its identified semantic content, scope, version and publication status.

Normative note

Canonical Commons standing establishes the published identity and version of the artefact within Codex Commons. It does not by itself establish external institutional, legal, regulatory, clinical, cultural or operational authority.

3. Interpretation

Retain the v1.0 concept, with proposed additional normative note:

Interpretation remains attributable to the representation, context and basis from which it is derived. Interpretation does not, by itself, establish fact, cause, authority, permission or universal applicability.

No separate Interpretation profile/object is introduced.

4. Evidence

Retain the v1.0 concept, with proposed additional normative note:

Evidence should be assessed relative to the claim, purpose, scope and context for which it is relied upon. Evidence sufficient for one declared use is not automatically sufficient for another.

5. Scope

Retain the v1.0 concept, with proposed additional normative note:

Applicability within one declared scope does not automatically extend to another scope or intended use.

6. Revision

Retain the v1.0 concept, with proposed additional normative note:

A later revision creates a new recognised state. It must not retroactively rewrite the historical standing of an earlier identified version.

7. Supersession

Retain the v1.0 concept, with proposed clarification:

Supersession is purpose- and scope-relative and should preserve the identity and reconstructability of the superseded artefact.

8. New cross-cutting normative note — Non-Promotion

No semantic role, publication status, mapping, assessment result, sufficiency determination, represented authority or lifecycle state should be treated as establishing another standing unless an explicit applicable basis supports that transition.

This is a vocabulary-level normative note, not a new canonical concept unless separately admitted.

Explicit non-changes

Do not add at v1.1 solely from the 29 September tests:

  • Representation Sufficiency as a standalone canonical concept;
  • Boundary Standing as a standalone canonical concept;
  • Authority Preservation as a separate concept;
  • Governed Revision as a separate concept;
  • Interpretation Assertion;
  • Standing Profile;
  • Authority ontology;
  • epistemic-state ontology;
  • CR Resonance/Spiral terminology;
  • Arqua RCA/EAA/SCIA terminology.

Publication gate

Before v1.1 may be published:

  1. compare every changed definition with v1.0;
  2. perform public-language/IP review;
  3. test against non-health independent examples;
  4. confirm no collision with established external semantic standards;
  5. verify register metadata, steward, version and change history;
  6. owner publication decision;
  7. only then mark v1.0 superseded where the declared publication policy requires it.

Candidate change history

v1.1 candidate — Narrow authority semantics; distinguish Commons canonical standing from external authority; strengthen interpretation, evidence, scope, revision and supersession notes; add Non-Promotion as cross-cutting normative guidance.

Decision state

PREPARED — NOT PUBLISHED / DOES NOT SUPERSEDE v1.0.

9. Equivalence / Formal Identity Boundary

Retain the v1.0 Equivalence concept, with proposed v1.1 clarification:

Codex equivalence is qualified equivalence for a declared purpose and scope unless a stronger external equivalence relation is explicitly asserted under that relation's own semantics.

Normative note:

A Codex equivalence assertion must not be treated as owl:sameAs, owl:equivalentClass, owl:equivalentProperty, skos:exactMatch, or another stronger formal relation unless that specific relation is explicitly intended, applicable and supported. Mapping similarity or purpose-qualified interchangeability does not by itself establish formal identity.

This implements the Commons Non-Promotion rule at the external-semantic boundary:

qualified semantic equivalence ≠ formal identity.

Publication-gate status — 29 September 2026

Source: 🧪CC-PUB-GATE-01 — Structural Vocabulary v1.1 Publication Gate Test v0.1

The candidate passed independent-domain and external-standard tests with one required amendment: the Equivalence / Formal Identity boundary above.

Current state after amendment: PUBLICATION-READY CANDIDATE — OWNER PUBLICATION DECISION STILL REQUIRED.

This status does not publish v1.1, supersede v1.0 or authorise machine-readable implementation.

10. Public Access / Commercial Rights Boundary

Proposed v1.1 publication note:

Codex Commons is publicly accessible, but public availability does not itself grant unrestricted implementation, redistribution, commercialisation, branding, conformance or derivative-product rights. Each artefact is used under its declared usage/licensing terms.

Short form:

Public access ≠ unrestricted reuse ≠ implementation rights ≠ Arqua commercial licence rights.

This boundary keeps the Structural Vocabulary publicly intelligible while preserving the separate Arqua licence boundary for protected Profiles, specifications, methods, maintained packages, partner/practitioner rights, vendor alignment rights, assessment rights and executable software.