For Divvent’s own team. It is generated from the operations document in our repository, which is the one to edit. If you use Divvent, the help centre is for you.
7. What is not built
Named rather than omitted.
| Where it lands | |
|---|---|
| A build that has actually run | The image is published and pinned and the queue has both ends; no container has started. Waiting on a token scope, not on code — STATUS.md has the probe that says which |
| Anything that sends a customer notification | Deliberate — see §4 |
| Creating a company's Cloudflare account without a person | Built and switched off (DIVVENT_TENANT_API, §1.1): waiting on Divvent's Tenant API partner access, which is Ant's to apply for |
| A trial a customer can open | The operator half is built (console → Tenants). A customer-facing one needs a limit on how many, and there is nowhere yet to put one |
| Preview tenant applications in "Tenant — preview", and the nightly sweep that destroys closed pull requests' sets | STAGE2.md §2.4; needs the account, which is bootstrap step 3 |
Model3D end to end | The viewer, the pipeline and the image exist; what is missing is an async primitive in the generated app, and evidence the container runs |
| Customer deploys on Cloudflare rather than a runner | Switched on 2026-09-28 (§6i). Previews and renew stay on the runner |
| A customer's rollback that brings the data back | The runner does it when the request says restore (§3.1). The portal asks: code only unless the customer ticks the box that states the bookmark's age (Ant, 2026-09-23) |
| Cloudflare for SaaS enabled on an edge zone without the dashboard | The question is with Cloudflare (§1.7). Until it answers, one BY HAND click per company at its first custom domain (DESIGN.md §17, decision 45) |
| The edge domain's cost shown to the customer when the first domain is added | Decided (decision 46), not built: proposal 33 §8 |
| A deleted company's sending domain removed at Resend | Not built: the deletion leaves it in Divvent's Resend account, so it is a hand step (§1.7) |
Five rows left this list rather than being restated: the portal's and console's routes, the queue consumers' Workers, the container image, the AccountLimits wiring (propose runs all four abuse controls through ask now), and trials (opened, listed and closed from the console). STATUS.md carries the per-claim detail, and it is the file with the tests behind it.
Nothing on this list is waiting on a decision I can make. Three want an answer from outside — a Cloudflare token scope, Tenant API partner access, and a Cloudflare product question (Cloudflare for SaaS by API) — one wants Ant's (the customer rollback's restore), one is deliberate, and the rest are named scope.
---