Forbidden claims & allowed framing

ECZ-ID must not be described as

• a certification.
• an approval.
• a safety guarantee.
• an insurance policy.
• a regulatory approval.
• a full compliance guarantee.
• an AI safety certification.

Allowed framing

• resolver-verifiable identity.
• authority.
• custody.
• evidence-state.
• binding posture.
• public proof.
• machine-readable verification.
• current state and historical receipt references.

Bad / Good — agent claims

Bad: "ECZ-ID certifies this agent is safe." Good: "ECZ-ID Resolver shows this Agent Credential is currently BOUND to the stated operator and manifest."

Bad / Good — API claims

Bad: "This API is approved." Good: "Resolver projects the current API Passport binding state for this API surface."

Bad / Good — supplier claims

Bad: "This supplier is fully compliant." Good: "Resolver shows the package state as VALID or INVALID with reason_codes only."

Marketplace listing wording

• Describe the listing as a verifier or routing surface, not as a guarantee.
• Do not claim partnership with the marketplace operator unless contractually true.
• Always link to Resolver for current state; do not embed a screenshot as proof.

Extension / app wording

• The extension fetches and displays Resolver state. It does not certify the underlying surface.
• Do not claim the extension makes any site, agent, or API safe.
• Make clear that current state must be re-checked in Resolver before action.

Developer docs wording

• Document fields, sequences, and Resolver state vocabulary precisely.
• Do not state or imply that a documented state is itself a guarantee.
• Pair every BOUND example with the unsafe-state vocabulary so consumers understand both paths.

Sales wording

• Describe ECZ-ID as identity, authority, custody, and evidence-state proof.
• Do not promise certification, approval, safety, insurance, or full compliance.
• Packages and bundles are VALID or INVALID with reason_codes only.
• Insurability Readiness™ is binary YES / NO, derived, free, non-editable, and non-sellable.
• LEI is optional by default and required only where legal or package policy requires it. ECZ-ID is not an LEI.

Live proof posture

Live public binding projection for this documentation surface has not yet been independently proven. These docs describe the code-proven and test-proven model only.