First SKU go-live — hosted-infra (full worked example)
Written by Grok - Human checking required
Product + sales voice. Hard gate T11 for real revenue. Dry-run ≠ sold.
Checklist is complete as process bone; open items are explicitly hard gates.
1. SKU
commercial/skus/hosted-infra.md — hosted reliability around inspectable models.
2. Ethos pre-check
| Question | Answer |
|---|---|
| Does customer need exclusive free-core weights? | No — refuse if demanded |
| Does verify require paid login? | No |
| Is BOUNDARY precedence clear to sales? | Yes — refuse handbook |
| Isolation reviewed? | Yes — design checklist |
3. Go-live checklist (worked)
A. Ethos / legal
- [x] BOUNDARY read; prohibited opacity none for this SKU
- [x] Isolation principles reviewed
- [x] Domain 1 decision draft language ready (“authorise hosted-infra pilot under BOUNDARY”)
- [x] MSA template ready (
MSA_HOSTED_INFRA_EXAMPLE.md) - [x] No side letter path
- [ ] Entity + bank (T6/T7) — OPEN
- [ ] Counsel-localised MSA — OPEN
B. Technical
- [x] Public verify still unpaid offline
- [x] Distinct signing key policy noted (prod keys T5 still open — no fake HSM)
- [x] Status language does not claim SKU live
C. Public honesty
- [x] SKU file status remains designed/not sold until invoice
- [x] Claim language: “optional hosted reliability; free core remains free”
- [x] Forbidden language list trained
D. First customer path
- [ ] Signed SOW — OPEN T11
- [ ] First invoice paid — OPEN T11
- [ ] Boundary attestation calendar date set when revenue starts
4. Allowed public claim (example)
“We offer optional hosted reliability and support around inspectable models. Free public core (weights under the TTLLM promise, manifests, basic ttlink, verification tools) remains free and public.”
5. Forbidden public claim (example)
“Enterprise customers get exclusive weights” / “Verification only through paid portal.”
6. Explicit non-claims
No customers. No revenue. Process readiness only.
Written by Grok - Human checking required — also on https://ttllms.com/placeholders/