(Informative Only — Not Binding)
EX.0 Purpose (informative)
This section provides a concrete example to reduce misreading.
It does not add requirements and must not be used to override normative text.
EX.1 Example: Minimal compliance unit (informative)
Compliance Unit Declaration (CUD) — Example
• Version: AIXEL v1.0
• Compliance Unit: “Acme Plumbing — Emergency Callout Service”
• Surfaces in scope: acmeplumbing.example/services/emergency, acmeplumbing.example/about, structured entity page
• Compliance status claimed: Validated (not Maintained)
Layer presence (example mapping):
1. Entity Layer
• Entity: Acme Plumbing (organization)
• Boundaries: “Plumbing services only; not electrical; not gas fitting unless licensed.”
• Identifier: stable canonical name + internal ID
2. Offer Layer
• Offer: “24/7 emergency plumbing callout within 20 km”
• Applies when: burst pipe, blocked drain, water leak
• Does not apply when: outside region, structural building damage, insurance claims handling
3. Proof Layer
• Claim: “Response within 2 hours in coverage area”
• Proof: documented on-call rota process + timestamped dispatch logs sample + explicit exceptions
• Constraint: “Traffic/weather may exceed target; customer is informed.”
4. Answer Layer
• Answer Unit:
• When recommended: urgent water leak, within 20 km, needs licensed plumber
• Why: on-call coverage + documented response process
• When not recommended: outside area, needs structural engineer, needs gas certification not held
5. Governance Layer
• Monitoring intent: monthly SPS run for “emergency plumber near me” intent class
• Remediation responsibility: named role + change log requirement for offer constraints
EX.2 Summary (informative, non-binding)
This example illustrates how one compliance unit can be expressed through the five layers without making outcome guarantees or vendor-specific claims.