Industry Terms of Service

Effective date: 2026-02-26 (UTC). Version: 1.0.

These terms define a jurisdiction-agnostic baseline for deployments using Word Orb + HLS-GSTR. Stricter local law controls; otherwise this baseline applies as a minimum contract requirement.

Certification requirement

• Active HLS certification is required before production customer-facing use.
• Certification scope must match deployed surfaces.
• Material changes require re-certification or written provisional approval.

Audit rights and evidence bundle

• On request, provide a complete evidence bundle within 5 business days, or faster for critical incidents.
• Evidence bundle must include decision logs, policy versioning, rules-hash integrity, release provenance, and conformance outputs.
• Preserve immutable safety evidence for at least 24 months.

Mandatory escalation handling obligations

• Any escalate decision must trigger monitored human escalation workflows with tracked receipt.
• Runbooks, response SLAs, and post-incident records are mandatory.
• Do not auto-downgrade escalation outputs without authorized human review.

Prohibition on bypassing safety decisions

• Do not bypass, override, strip, or reinterpret hard_block, soft_block, or escalate outcomes.
• Do not use prompts, middleware, or secondary models to evade HLS outcomes.
• Preserve required HLS decision metadata end-to-end.

Decertification and key revocation policy

• Word Orb may decertify integrations and revoke keys for critical non-compliance.
• Grounds include safety bypass, repeated failed audits, evidence tampering, escalation suppression, or unresolved severe incidents.
• Emergency revocation may occur without advance notice where ongoing risk is credible.

Compliance contact: hello@thedailylesson.com