⚖️

CC-ADM-AAP-01 — Assessment Assertion Profile — Commons Admission Decision Package v0.1

Decision Package ID: CC-ADM-AAP-01

Version: 0.1

Date: 19 September 2026

Candidate: Assessment Assertion Profile

Standing: INTERNAL — COMMONS ADMISSION DECISION PACKAGE. ADMISSION DECISION PENDING. PUBLICATION NOT AUTHORISED.

Decision requested

Choose one:

A — ADMIT AS CODEX COMMONS CANDIDATE SPECIFICATION

Admit the Assessment Assertion Profile into the controlled Commons corpus as a versioned internal candidate specification.

B — HOLD FOR FURTHER RESEARCH

Preserve experiment/specification lineage without candidate standing.

C — REDUCE TO EXPLANATORY GUIDANCE

Retain the semantic distinctions as guidance only.

Executive recommendation

RECOMMEND A — ADMIT AS AN INTERNAL CONTROLLED CODEX COMMONS CANDIDATE SPECIFICATION.

The semantic problem is general, the candidate has survived hostile testing and prior-art reduction, and the remaining issues are publication/adoption/implementation rather than foundational semantics.

Candidate purpose

The Assessment Assertion Profile identifies and qualifies:

the result of assessing a declared subject/aspect against an explicit assessment basis, under declared provenance, scope and time.

It preserves the separation between:

assessment · conformance claim · acceptance · certification · authority · runtime admissibility.

Semantic core proposed for admission

Required

  • assessment assertion identity sufficient for governance/reconstruction;
  • subject_ref;
  • subject_aspect_or_scope;
  • assessment_basis_ref;
  • assessment_outcome_ref_or_value;
  • assessment_provenance.

Required where material

  • subject version/snapshot;
  • basis version/profile;
  • method/procedure;
  • evidence refs;
  • assessment time;
  • evidence time/window;
  • environment/jurisdiction/applicability.

Optional / linked

  • assessor/tool;
  • limitations/qualification;
  • confidence/quantitative result;
  • conflict;
  • invalidation/supersession;
  • revalidation trigger;
  • conformance claim;
  • acceptance decision;
  • exception/waiver;
  • certification/credential;
  • authority reference.

Supporting construct — Assessment Set / Report

An Assessment Set/Report is an identifiable collection of Assessment Assertions sharing a common basis, method, execution/run, provenance, subject scope or release context.

Shared qualifiers may be inherited if reconstructable.

It does not replace assertion-level identity where individual findings require citation, conflict, acceptance or supersession.

Core invariants proposed for admission

  1. Assessment is basis-relative.
  2. Assessment is subject/aspect-relative.
  3. Assessment is time-relative where subject/evidence changes.
  4. Evidence ≠ assessment outcome.
  5. Implementation ≠ conformance.
  6. Observed success ≠ complete conformance.
  7. Assessment ≠ acceptance.
  8. Assessment ≠ certification.
  9. Assessment ≠ authority.
  10. Conformance ≠ runtime admissibility.
  11. Waiver does not rewrite non-conformance.
  12. Conflicting assessments may coexist.
  13. Historical findings remain reconstructable.
  14. Probabilistic result ≠ categorical conformance unless basis licenses it.
  15. Basis change does not silently rewrite historical finding.
  16. Subject change requires bounded identity/snapshot handling.
  17. Automated assessment is permitted with provenance.
  18. Public assessment result does not automatically establish acceptance/authority.

Outcome-vocabulary position

The profile does not define a universal Commons conformance/outcome vocabulary.

Use outcome semantics from the applicable assessment basis/domain where possible.

This avoids false equivalence among SHACL validation, audit findings, test results, certification regimes, AI evaluations and other domains.

Interoperability position

Reuse:

  • SHACL for RDF/data validation where applicable;
  • PROV-O for assessment/evidence/activity/agent provenance;
  • domain test/audit/assurance vocabularies;
  • credential/certification models where applicable.

The candidate adds the cross-domain assertion envelope and anti-collapse discipline.

Relationship to RRAP

RRAP answers:

What role is this representation/evidence item playing?

Assessment Assertion Profile answers:

What did an assessment conclude about this subject/aspect against this basis?

RRAP may qualify the roles of requirements, implementations and evidence used in assessment.

Relationship to QMAP

QMAP answers:

What relationship is being asserted between source and target resources?

A QMAP mapping may be an assessment subject or assessment evidence/context.

Mapping ≠ assessment.

Relationship to Commons Non-Promotion Rule

Direct applications:

  • IMPLEMENTED ≠ CONFORMANT;
  • OBSERVED SUCCESS ≠ COMPLETE CONFORMANCE;
  • ASSESSMENT ≠ ACCEPTANCE;
  • CONFORMANT ≠ CERTIFIED;
  • CERTIFIED ≠ AUTHORISED;
  • CONFORMANT ≠ RUNTIME ADMISSIBLE.

Experiment lineage

Stage 1 — Decomposition / generality

CC-EXP-C05-CONF-01

8 generality + 12 hostile cases.

Result: PASS.

Finding: reusable core is Assessment Assertion, not monolithic Conformance Profile.

Stage 2 — Standards reduction

CC-EXP-C05-CONF-02

SHACL/PROV/test/audit/certification reduction.

Result: PASS WITH REDUCTION.

Finding: reuse domain outcomes; keep certification separate.

Stage 3 — Semantic stability

CC-EXP-C05-CONF-03

18 hard cases.

Result: PASS.

Findings:

  • outcome is basis/scope/time relative;
  • evidence qualification remains separate;
  • waiver does not rewrite finding;
  • continuous assessment preserves history.

Stage 4 — Candidate specification

CC-AAP-SPEC-01

Specification + 14 hostile review cases.

Result: PASS.

Stage 5 — Generic prior-art / naming

CC-EXP-AAP-04

Generic assessment/result mechanism acknowledged as established.

Result: PASS WITH REDUCTION.

Finding: retain full name; do not standardise acronym yet.

Prior-art / novelty boundary

Do not claim invention of:

  • assessment;
  • test results;
  • validation reports;
  • audit findings;
  • conformance;
  • basis-relative evaluation.

Bounded candidate statement:

The Assessment Assertion Profile packages a tested cross-domain discipline for explicitly identifying basis-bound assessment assertions and preserving their provenance, scope, outcome semantics and separation from downstream governance standing.

No novelty/legal claim is made.

Risk assessment

<table fit-page-width="true" header-row="true"><tr><td>Risk</td><td>Position</td></tr>

</table>

<tr><td>duplicates test/audit/validation models</td><td>Controlled — cross-domain profile only.</td></tr>

</tr>

<tr><td>universal outcome semantics</td><td>Avoided — reuse domain outcomes.</td></tr>

</tr>

<tr><td>finding confused with acceptance</td><td>Explicitly separated.</td></tr>

</tr>

<tr><td>finding confused with certification</td><td>Explicitly separated.</td></tr>

</tr>

<tr><td>conformance confused with authority/admissibility</td><td>Explicitly prohibited.</td></tr>

</tr>

<tr><td>identity too heavy for disposable results</td><td>Identity only needs to be sufficient for governance/reconstruction.</td></tr>

</tr>

<tr><td>AAP acronym overloaded</td><td>Do not standardise acronym yet.</td></tr>

</tr>

<tr><td>premature publication/schema</td><td>Separately gated.</td></tr></table>

</tr>

IP / publication pre-position

This is not formal legal/IP clearance.

The profile is reduced away from:

  • EAA/SCIA internals;
  • customer-specific assessment data;
  • proprietary certification regimes;
  • copied SHACL/domain semantics.

External standards are referenced for interoperability.

Formal publication/IP review remains required before external release.

Proposed admission standing if A is selected

  • Name: Assessment Assertion Profile
  • Acronym: Not standardised
  • Version: 0.1 Candidate
  • Programme: Codex Commons
  • Status: ADMITTED CANDIDATE
  • Classification: Internal — Controlled
  • Publication: Not Approved
  • Namespace: Not Assigned
  • Machine-readable implementation: Not Authorised
  • Conformance programme: None
  • Supporting construct: Assessment Set / Report
  • Owner: Mark Tovey / Codex Commons governance

What admission authorises

  1. maintain the profile as controlled Commons candidate;
  2. preserve experiment/specification lineage;
  3. formal IP/publication review;
  4. further interoperability/comprehension testing;
  5. later publication decision package;
  6. later decision on machine-readable need.

What admission does not authorise

  • public Commons/website publication;
  • public GPT inclusion;
  • standardisation/certification claims;
  • namespace/URI;
  • RDF/OWL/JSON-LD/SHACL implementation;
  • GitHub implementation;
  • customer adoption claims;
  • novelty/patent claims.

Decision recommendation

RECOMMEND A — ADMIT AS CODEX COMMONS CANDIDATE SPECIFICATION.

Further semantic experimentation is now producing diminishing returns. Remaining issues are primarily publication, adoption and implementation.

Owner decision

PENDING.

No admission action occurs until explicit owner approval.

Linked

Owner Decision — ACCEPTED — 19 September 2026

Decision: A — ADMIT AS CODEX COMMONS CANDIDATE SPECIFICATION

Owner: Mark Tovey

Admission decision

The Assessment Assertion Profile v0.1 Candidate is admitted into the controlled Codex Commons corpus.

Admitted standing

  • Name: Assessment Assertion Profile
  • Acronym: Not standardised
  • Version: 0.1 Candidate
  • Programme: Codex Commons
  • Status: ADMITTED CANDIDATE
  • Classification: Internal — Controlled
  • Publication: NOT APPROVED
  • Namespace: Not Assigned
  • Machine-readable implementation: Not Authorised
  • Conformance programme: None
  • Supporting construct: Assessment Set / Report
  • Owner: Mark Tovey / Codex Commons governance

Semantic core admitted

An Assessment Assertion records the result of assessing a declared subject/aspect against an explicit assessment basis under reconstructable provenance and applicable scope/time.

Minimum:

  • assessment assertion identity sufficient for governance/reconstruction;
  • subject;
  • subject aspect/scope;
  • assessment basis;
  • assessment outcome reference/value;
  • provenance.

Subject/basis version, method, evidence, time, environment and jurisdiction are included where material.

Invariants retained

  • assessment is basis-relative;
  • assessment is subject/aspect-relative;
  • evidence ≠ assessment outcome;
  • implementation ≠ conformance;
  • observed success ≠ complete conformance;
  • assessment ≠ acceptance;
  • assessment ≠ certification;
  • assessment ≠ authority;
  • conformance ≠ runtime admissibility;
  • waiver does not rewrite non-conformance;
  • conflicting assessments may coexist;
  • historical findings remain reconstructable;
  • probabilistic result does not become categorical conformance unless the basis licenses it;
  • basis/subject changes do not silently rewrite historical findings;
  • automated assessment is permitted with provenance;
  • public findings do not automatically establish acceptance or authority.

Outcome-vocabulary decision

The profile does not establish a universal Commons conformance/outcome vocabulary.

Applicable domain/basis semantics remain authoritative for outcome meaning.

Scope of approval

Authorised:

  1. maintain the Assessment Assertion Profile as controlled Commons candidate;
  2. preserve full experiment/specification lineage;
  3. conduct formal IP/publication review;
  4. conduct further interoperability/comprehension testing;
  5. prepare a later publication decision package;
  6. later decide whether machine-readable representation is needed.

Explicitly not authorised

  • public Codex Commons/website publication;
  • public GPT inclusion;
  • external standardisation/certification claims;
  • namespace/URI;
  • RDF/OWL/JSON-LD/SHACL implementation;
  • GitHub implementation;
  • customer adoption claims;
  • novelty/patent claims.

Governance receipt

Assessment Assertion Profile v0.1 Candidate is admitted to Codex Commons as an internal controlled candidate semantic specification. Publication and implementation remain separately gated.

Decision status: ACCEPTED / ADMITTED CANDIDATE.