Claims stop where evidence stops.

This is the shipped product boundary, not a roadmap. “External blocker” means Cerilo has a fail-closed integration boundary but an operator or provider must still complete production setup. No secret values are published here.

1. 01
   Domain registrar — External blocker

   Availability and Claim workflows fail closed until a production registrar connection is configured.

2. 02
   Mail delivery — External blocker

   Provider adapters and verified webhook handling exist; production delivery still needs approved provider credentials and DNS.

3. 03
   Billing — Preview

   Plan selection is recorded, but no public checkout is presented as charging a customer.

4. 04
   DNS activation — External blocker

   DNS records and ownership states are modeled; activation depends on registrar and DNS-provider confirmation.

5. 05
   Social publishing — External blocker

   Publishing is durable and fail-closed, but each channel requires a real OAuth application and connected account.

6. 06
   Metrics — Preview

   First-party outcomes are recorded; platform reach remains explicitly marked as stub data where no provider API is connected.

7. 07
   Managed agents — External blocker

   Provisioning, approval, containment, and shutdown are durable; Ujex and a managed runtime must both be configured.

8. 08
   Demo and stub behavior — Local only

   Demo OAuth and deterministic AI fallback behavior are permitted only in explicit non-production environments.

9. 09
   Workspace export — Live

   The authenticated export path inventories current Firestore data and records external cleanup obligations.