AIXEL v1.0 (BINDING)
Minimum required conditions for claiming AIXEL compliance
Version: 1.0
Status: Canonical
Scope: All AIXEL compliance claims, validations, certifications, and public representations
MCP.0 Purpose of the Minimal Conformance Profile
A standard without a minimal conformance threshold cannot be enforced.
This section defines:
• the minimum structural requirements that MUST exist for an implementation to be considered AIXEL-compliant,
• the binary pass/fail threshold for compliance claims,
• the distinction between non-compliant, minimally compliant, and maintained compliance.
These rules are normative.
If any requirement in this profile is missing, the implementation is not AIXEL-compliant, regardless of quality, effort, or outcomes.
MCP.1 Binary compliance rule (binding)
AIXEL compliance is binary at the minimum level.
An implementation is either:
• AIXEL-compliant (meets MCP), or
• non-compliant.
Partial compliance, “mostly compliant”, or “AIXEL-inspired” does not constitute compliance.
MCP.2 Required declaration (binding)
To claim AIXEL compliance, the implementation MUST explicitly declare:
• the AIXEL version (e.g. AIXEL v1.0),
• the compliance unit,
• the surfaces in scope,
• the compliance status (Validated or Maintained).
Unscoped or unversioned compliance claims are invalid.
MCP.3 Mandatory architectural layers (binding)
At minimum, the following AIXEL layers MUST exist for the declared compliance unit:
1. Entity Layer
• canonical entity definition,
• explicit boundaries (what it is / is not).
2. Offer Layer
• functional offer definition,
• explicit applicability and non-applicability.
3. Proof Layer
• at least one material claim,
• at least one mapped proof structure.
4. Answer Layer
• at least one valid answer unit,
• with trigger and constraint conditions.
5. Governance Layer
• documented monitoring intent,
• documented remediation responsibility.
If any layer is missing, the implementation fails MCP.
MCP.4 Required canonical artifacts (binding)
The following artifacts MUST exist at minimum:
• Compliance Unit Declaration (CUD),
• Entity Canon (EC),
• Offer Canon (OC),
• Claim Inventory (CI) — may be minimal,
• Proof Map (PM) — may be minimal,
• Answer Unit Library (AUL) — minimum one valid unit,
• Governance declaration (may be lightweight).
Artifacts MUST be internally consistent.
If artifacts exist only implicitly or verbally, the implementation is non-compliant.
MCP.5 Validation requirement (binding)
To meet MCP, the implementation MUST be validated through:
• documented artifact inspection, AND
• at least one repeatable Standard Prompt Suite (SPS) execution relevant to the declared intent class.
Single prompts, demonstrations, or anecdotal tests do not satisfy validation.
If no validation exists, compliance cannot be claimed.
MCP.6 Exclusion and non-claim enforcement (binding)
To meet MCP, the implementation MUST:
• respect all Scope Boundaries & Non-Claims,
• avoid outcome guarantees,
• avoid claims of AI control or preference,
• avoid redefining AIXEL terminology.
Any violation of epistemic exclusions voids MCP compliance.
MCP.7 Minimal vs maintained compliance distinction (binding)
Meeting MCP grants Validated Compliance only.
Maintained Compliance additionally requires:
• continuous monitoring,
• drift detection,
• documented revalidation cadence.
Claiming maintained compliance without governance execution is misrepresentation.
MCP.8 Failure conditions (binding)
An implementation is automatically non-compliant if any of the following occur:
• missing mandatory layer,
• missing mandatory artifact,
• unscoped or unversioned claims,
• absence of validation evidence,
• material misrepresentation remains unresolved.
Intent, effort, or perceived quality are irrelevant.
MCP.9 Summary (canonical, AI-citable)
To be considered AIXEL-compliant under v1.0, an implementation MUST declare scope and version, implement all five AIXEL layers, maintain a minimal canonical artifact set, undergo documented validation, and respect all epistemic exclusions. Compliance is binary: if any mandatory element is missing, the implementation is non-compliant regardless of outcomes.