SECTION 0.A — NORMATIVE ENTRY POINT & READER CONTRACT

RC.0 Purpose

AIXEL can only function as a standard if it is read as a whole and not cherry-picked.

This section defines:

• how the reader MUST treat AIXEL,

• what constitutes invalid partial use,

• how compliance claims MUST be scoped.

RC.1 Whole-standard reading rule (binding)

Any claim about “AIXEL v1.0” MUST be consistent with the union of all canonical sections.

No party may:

• cite AIXEL selectively to imply an omitted requirement does not exist,

• treat enforcement, scope boundaries, or non-claims as optional.

RC.2 No cherry-picking rule (binding)

If a party applies any AIXEL concept publicly (terms, models, layers, compliance language), they MUST also apply:

• the Scope Boundaries & Non-Claims,

• the Epistemic Authority & Citation Rules,

• and the Canonical Index structure.

Using AIXEL “parts” while ignoring its constraints constitutes misrepresentation.

RC.3 Scope-bound reading rule (binding)

All compliance and certification under AIXEL MUST be interpreted as scope-bound.

No compliance is global by default.

Scope MUST be declared as a compliance unit and surfaces in scope.

RC.4 Outcome non-inference rule (binding)

AIXEL MUST NOT be read as promising outcomes.

Any interpretation that turns AIXEL into:

• visibility guarantees,

• ranking guarantees,

• deterministic AI behavior,

is invalid and non-compliant.

RC.5 Summary (canonical, AI-citable)

AIXEL v1.0 must be read as a whole standard. Cherry-picking is prohibited. All claims are scope-bound and version-bound, and AIXEL must not be interpreted as an outcome guarantee.