Decision question

Should Codex Structural Vocabulary v1.1 receive public Codex Commons standing and supersede v1.0 for its declared scope?

Evidence summary

v1.1 has:

preserved the published v1.0 artefact rather than mutating it in place;
narrowed Authority so Commons does not originate or transfer external authority;
narrowed Canonical Artefact to canonical Commons standing rather than generic external authority;
clarified Interpretation so it does not silently become fact, cause, permission or authority;
added purpose-relative Evidence and Scope guidance;
strengthened Revision and Supersession so history remains reconstructable;
added Non-Promotion as a cross-cutting normative note rather than a new ontology concept;
added an Equivalence / Formal Identity boundary so qualified equivalence is not silently promoted into stronger SKOS/OWL semantics;
passed independent-domain hostile fixtures;
passed external semantic-standard collision/reuse review subject to reuse/version boundaries;
introduced no new Commons kernel profile and no CR/Arqua protected runtime semantics.

Residual risks

R1 — Public wording

Low. The revised language is architectural and bounded, but the word Authority remains sensitive and must retain its explicit scope/source qualifiers.

R2 — Standards collision

Low after the Equivalence clarification, provided future machine-readable implementation reuses applicable W3C vocabularies and binds explicit versions.

R3 — Accidental implementation inference

Controlled. Publication of v1.1 must not be read as authorising RDF/OWL/JSON-LD/SHACL, GitHub, API or MCP implementation.

R4 — Supersession semantics

Controlled. v1.0 should remain historically retrievable and identified as superseded only after v1.1 publication is actually approved and recorded.

Recommended owner disposition

PUBLISH v1.1, with controlled supersession of v1.0.

Rationale:

the amendment corrects a real semantic-boundary ambiguity in v1.0;
the candidate has passed the planned hostile and standards gates;
no unresolved semantic responsibility requires further kernel design;
publication would improve public alignment with the accepted Commons architecture while preserving v1.0 history.

If owner approves PUBLISH

Execute in this order:

create/update the v1.1 Commons Register record with exact version, steward, publication status, provenance, change history and usage/licensing fields;
mark v1.1 Published under the Publication Policy;
mark v1.0 Superseded by v1.1 while preserving its full historical record;
update the Commons front door to point to v1.1 as the current Structural Vocabulary;
retain the semantic-kernel machine-readable/GitHub HOLD;
create a publication receipt linking v1.0 → v1.1 and the gate evidence.

If owner chooses RETURN FOR REVISION

Record the required changes explicitly; v1.0 remains current.

If owner chooses HOLD

Keep v1.1 as a publication-ready internal candidate; v1.0 remains current.

Owner decision — 30 September 2026

DECISION: PUBLISH v1.1 WITH CONTROLLED SUPERSESSION OF v1.0.

Owner approval was given in the Arqua build sequence on 30 September 2026.

This decision authorises:

publication of Codex Structural Vocabulary v1.1 through Codex Commons;
creation of the v1.1 Commons Register publication record;
controlled supersession of v1.0 while preserving historical retrievability;
update of the Commons front door to point to v1.1 as the current Structural Vocabulary;
publication receipt linking v1.0 → v1.1 and CC-PUB-GATE-01.

This decision does not authorise machine-readable implementation, GitHub/API/MCP release, or changes to unrelated Commons candidates.

Current state

OWNER DECISION COMPLETE — PUBLISH AUTHORISED. REGISTER/DELIVERY EXECUTION IN PROGRESS.

CC-PUB-DEC-01 — Structural Vocabulary v1.1 Owner Publication Decision Pack