This page generates a contract-ready SLA clause pack aligned with stability evidence, determinism metadata, and routing transparency. Choose a tier and generate a downloadable SLA draft.
AXSTUDIO.AI SERVICE LEVEL & EVIDENCE ADDENDUM (Tier: ENTERPRISE) 1. Definitions 1.1 "Generation Job" means an image/video/story generation request processed by axstudio.ai. 1.2 "Generation Certificate" means the job-level evidence artifact containing: determinism metadata (seed/hash), routing metadata (provider/model/version), QA metrics, stability class/BI, timestamps, and evidence-chain hashes. 1.3 "Evidence Retention" means storage and retrievability of certificates and logs for the period defined in Section 6. 2. Scope 2.1 axstudio.ai provides creative orchestration, not autonomous control of user systems. 2.2 axstudio.ai does not guarantee zero failure, zero drift, or perfect output. It guarantees auditable evidence of processing and declared constraints. 3. Availability & Support (example terms) 3.1 Monthly availability target: - PRO: 99.0% - ENTERPRISE: 99.5% (or negotiated) 3.2 Support response targets (example): - PRO: next business day - ENTERPRISE: 4–8 hours (or negotiated) 4. Determinism & Version Lock Commitments 4.1 For each Generation Job, axstudio.ai shall record: request_hash, seed (if supported), route_lock (policy + preferred route), and model_versions. 4.2 If a provider does not support deterministic seeds, axstudio.ai shall still provide deterministic orchestration evidence via request_hash + route_lock + model_versions. 5. Quality Assurance (QA) & Bounded Repair 5.1 The service may perform bounded multi-pass attempts to achieve acceptance thresholds. 5.2 The certificate shall record attempts count, metrics, and acceptance reasoning. 6. Evidence Retention & Auditability 6.1 Certificates and evidence-chain hashes shall be retained as follows: - PRO: 30 days (example) - ENTERPRISE: 180–365 days (negotiated) 6.2 Certificates shall be exportable in machine-readable format (JSON). 7. Liability & Attribution 7.1 Where certificates show internal non-compliance with declared constraints, this constitutes a service breach. 7.2 Where certificates show compliance and failure results from external provider faults or user inputs, duty is considered fulfilled. 8. Data & Privacy 8.1 User prompts/outputs are treated according to the privacy policy and content policy. 8.2 Identity references require user confirmation of rights/consent. END OF ADDENDUM