Certification Limitations & Warranty

A Certification Forge seal or verdict records that, at a stated time, under stated inputs and policy, automated and/or human-supervised checks produced a signed outcome (e.g., certify, block, or NOT_READY). Evidence may be hash-chained for integrity. Seals are product features of Echo Forge, not government licenses or third-party lab accreditations unless an enterprise agreement attaches a specific accredited scheme.

Default posture is fail-closed: absence of a positive seal, a BLOCK verdict, or a NOT_READY state means promotion should not proceed. A missing or expired seal is not approval. Adapter or model promotion gates may withhold CERTIFY until measured thresholds are met.

• Continuous security of systems after the evidence timestamp (configuration drift, new CVEs, operator error);
• Fitness for every customer environment, load profile, or regulatory regime;
• Legal non-infringement, export compliance, or accessibility certification unless explicitly in scope;
• Physical product safety, EMI, biocompatibility, or shop process quality (see Manufacturing Limitations);
• Outcomes when artifacts or environments differ from the certified identity (hash, version, image digest).

Limited process warranty: For paid Certification Forge usage under an active subscription, Echo warrants that seals will be generated using the documented pipeline controls (intake identity, isolation where advertised, evidence chaining, and signature format) materially as described in product documentation at the time of the run.

Exclusive remedy: Re-run the certification job at no additional platform fee, or a service credit not to exceed fees paid for the affected certification runs in the prior 30 days. This is the sole warranty remedy unless a signed enterprise agreement expands it.

EXCEPT FOR THIS LIMITED WARRANTY, CERTIFICATION OUTPUTS ARE PROVIDED AS-IS. IMPLIED WARRANTIES ARE DISCLAIMED TO THE MAXIMUM EXTENT PERMITTED BY LAW. LIABILITY IS CAPPED AS IN THE Terms of Service.

• Submit correct, immutable artifact identities;
• Keep secrets out of public evidence where not required;
• Do not misrepresent a seal's scope (e.g., claiming regulatory approval);
• Re-certify after material changes to code, config, models, or deployment topology.

Public verification endpoints allow third parties to check seal signatures and hashes. Public pages may be redacted. Cross-tenant private evidence is not exposed (IP Ownership §6).

Certification onboarding: [email protected]. Live API docs: cert-api.echosforge.com/docs.