Experiment ID: CC-EXP-C01-01

Version: 0.1

Date: 19 September 2026

Candidate: CC-C01 — Standing-Preservation Distinction Set

Standing: INTERNAL — EXECUTED DECOMPOSITION & GENERALITY TEST. NO COMMONS ADMISSION OR PUBLICATION AUTHORISED.

Question

Do the repeatedly observed distinctions:

• Evidence ≠ Representation
• Representation ≠ Reality
• Representation ≠ Institutional Standing
• Standing ≠ Authority
• Authority ≠ Technical Permission
• Conformance ≠ Acceptance
• Conformance ≠ Runtime Admissibility
• Qualified Understanding ≠ Authority to Act
• Capability ≠ Implementation
• Reference Definition ≠ Customer Implementation
• Observed Evidence ≠ Accepted Model
• Publication ≠ Institutional Authority

form one reusable Commons semantic artefact, or are they several different semantic families that should not be bundled?

Executive result

PASS WITH DECOMPOSITION — DO NOT CREATE ONE MONOLITHIC “STANDING PRESERVATION ONTOLOGY”.

The candidate decomposes into four reusable semantic boundary families plus one cross-cutting anti-promotion principle.

The repeated pattern is real, but the objects on either side of each inequality belong to different concerns.

Family SP1 — Epistemic / Representational Boundary

Candidate distinctions:

• Reality ≠ Evidence
• Evidence ≠ Representation
• Representation ≠ Interpretation
• Observed Evidence ≠ Accepted Model
• Qualified Understanding ≠ Truth

Core question:

What is the relationship between what exists/occurs, what is evidenced, what is represented, and what is understood?

This family is close to active CR epistemic/reality research.

Disposition: GENERAL but RESEARCH-SENSITIVE. Do not admit yet.

Family SP2 — Institutional Standing / Authority Boundary

Candidate distinctions:

• Representation ≠ Institutional Standing
• Standing ≠ Authority
• Publication ≠ Institutional Authority
• Availability ≠ Permitted Reliance
• Role/record ownership ≠ universal authority

Core question:

What makes a representation institutionally operative or authoritative for a particular proposition?

This is highly general but intersects legal, organisational, sovereign and Indigenous/custodial authority.

Disposition: GENERAL but AUTHORITY-SENSITIVE. Specialist/research review required.

Family SP3 — Design / Implementation / Conformance Boundary

Candidate distinctions:

• Capability ≠ Implementation
• Reference Definition ≠ Customer Implementation
• Designed ≠ Implemented
• Implemented ≠ Observed
• Implementation ≠ Conformance
• Conformance ≠ Acceptance

Core question:

What is intended/referenced, what is realised, what is observed, and what has been assessed as conforming?

RRAP already addresses part of this family.

Disposition: HIGH maturity. Reuse RRAP; investigate conformance/acceptance separately.

Family SP4 — Understanding / Execution Boundary

Candidate distinctions:

• Qualified Understanding ≠ Authority to Act
• Technical Permission ≠ Institutional Authority
• Conformance ≠ Runtime Admissibility
• Policy/semantic coherence ≠ Execution Permission
• Capability to execute ≠ admissibility of execution

Core question:

What prevents knowledge, technical capability or design conformance from being promoted into permission to cause consequence?

This is strongly evidenced through EAA/authority work but is partially Arqua-specific in its current expression.

Disposition: GENERAL PRINCIPLE candidate; requires reduction away from EAA terminology before Commons consideration.

Cross-cutting principle — Semantic Non-Promotion

Across all four families, a common pattern survives:

A representation, claim, role, capability or finding does not acquire a different semantic standing merely because it is available, transferred, mapped, published, implemented, observed or passed across a boundary. Any promotion in standing requires an explicit rule/authority/evidence process appropriate to the target standing.

Working name:

Semantic Non-Promotion Principle (SNPP)

This is a candidate explanatory/research principle only.

Do not admit/canonise from this experiment.

Generality tests

G1 — Clinical health

Population evidence ≠ individual observation.

Observation ≠ diagnosis/accepted interpretation.

Guideline ≠ authority to treat a particular patient.

Treatment capability ≠ treatment permission.

PASS across SP1/SP2/SP4.

G2 — Software engineering

Reference architecture ≠ implemented system.

Deployment ≠ observed behaviour.

Observed behaviour ≠ conformance.

Technical permission ≠ business authority.

PASS across SP3/SP4.

G3 — Construction

Building code/reference ≠ design.

Design ≠ constructed state.

As-built representation ≠ physical observation.

Inspection result ≠ acceptance/certification unless appropriate process grants it.

PASS across SP1/SP3/SP2.

G4 — Financial control

Control framework ≠ control design.

Control design ≠ configured control.

Configured control ≠ effective operation.

Test result ≠ management acceptance.

System access ≠ delegated authority.

STRONG PASS.

G5 — Research/publication

Research finding ≠ settled theory.

Paper publication ≠ institutional authority.

Citation ≠ validation.

Public availability ≠ permission to rely operationally.

STRONG PASS.

G6 — Regulation

Published regulation may independently carry authority.

A representation of regulation ≠ regulation itself.

A compliance mapping ≠ legal determination.

Technical conformance ≠ legal permission.

PASS WITH AUTHORITY GUARDRAIL.

G7 — AI agent

Model output ≠ evidence.

Evidence ≠ accepted representation.

Agent confidence ≠ authority.

Tool permission ≠ execution admissibility.

Successful action ≠ legitimate action.

STRONG PASS.

G8 — Indigenous/custodial context

Published representation of Indigenous knowledge/authority ≠ custodial authority.

Availability/publication ≠ permission to reuse.

External mapping ≠ legitimacy.

PASS — demonstrates why SP2 cannot be naively universalised.

Bundling test

Would one vocabulary containing Reality, Evidence, Representation, Standing, Authority, Conformance and Admissibility be coherent?

REJECT.

Reasons:

1. mixes epistemology, governance, legal/institutional authority, architecture and runtime execution;
2. would create false hierarchy;
3. risks Arqua terminology becoming Commons universal semantics;
4. authority semantics require domain/cultural sensitivity;
5. existing standards already cover parts;
6. different families mature at different rates.

Relationship to RRAP

RRAP already operationalises one slice of SP3:

REFERENCE / DESIGNED / IMPLEMENTED / OBSERVED as contextual representation roles.

Therefore CC-C01 should not duplicate those distinctions.

Potential future Commons architecture:

RRAP
representation-role assignment
        │
        ├── future Conformance Profile?
        │
        ├── future Institutional Standing Profile?
        │
        └── future Epistemic Qualification Profile?

Do not assume all profiles are needed or admissible.

Semantic Non-Promotion Principle test

The cross-cutting pattern survived all eight domains.

But test whether it is genuinely a “principle” or merely a family resemblance.

Counterexample:

A signed contract may become legally effective by crossing a formally defined signature/execution boundary.

Resolution:

The standing did not increase merely because of boundary crossing; the boundary crossing was itself part of an explicit rule/authority process that changes standing.

Counterexample:

A document becomes public when published.

Resolution:

Publication changes its publication status, but does not automatically change unrelated authority, truth, conformance or admissibility standing.

Counterexample:

A build becomes “deployed” when deployment completes.

Resolution:

Deployment process can explicitly establish IMPLEMENTED standing for a declared aspect, but not OBSERVED behaviour/conformance/admissibility.

SNPP survives with wording refinement.

Refined candidate principle

Semantic standing does not transfer or promote by implication. A change from one role, status or standing to another requires an explicit qualifying relation, process or authority appropriate to the target semantic claim.

This avoids saying standing can never change at a boundary.

Experiment result

<table fit-page-width="true" header-row="true"><tr><td>Question</td><td>Result</td></tr>

<tr><td>Is the recurring anti-collapse pattern real?</td><td>YES — STRONG PASS</td></tr>

<tr><td>Is it one ontology?</td><td>NO — REJECT</td></tr>

<tr><td>Can it decompose into stable families?</td><td>YES — four families</td></tr>

<tr><td>Does RRAP already cover part?</td><td>YES — SP3 subset</td></tr>

<tr><td>Is there a cross-cutting principle?</td><td>YES — candidate SNPP</td></tr>

<tr><td>Is SNPP ready for Commons admission?</td><td>NO — needs independent prior-art/theory test</td></tr></table>

Decision

CC-EXP-C01-01 — DECOMPOSITION & GENERALITY PASS.

1. Reject monolithic Standing-Preservation vocabulary/ontology.
2. Preserve four semantic boundary families SP1–SP4.
3. RRAP remains the mature Commons candidate for part of SP3.
4. Extract Semantic Non-Promotion Principle (SNPP) as a separate candidate for research/testing.
5. Hold SP1 for CR epistemic/reality research.
6. Hold SP2 for authority/cultural/legal specialist reconciliation.
7. Investigate conformance/acceptance as a possible future narrow Commons profile only if useful.
8. Reduce SP4 before any Commons consideration.
9. No admission/publication authorised.

Recommended next experiment

Test SNPP independently:

• prior art in type systems, provenance, trust/authority, evidence and policy models;
• counterexamples where status legitimately changes through process;
• distinguish semantic promotion from explicit transformation/qualification;
• determine whether SNPP is a useful formal principle, a design rule, or merely explanatory language.

Linked

• 🧬CC-EXTRACT-ARQUA-01 — Commons Candidate Extraction from Recent Arqua–CR Work v0.1
• ⚖️CC-ADM-RRAP-01 — Representation Role Assignment Profile — Commons Admission Decision Package v0.1
• Codex Commons