The product portal can be public. Operator, customer and control-plane authority cannot. Every later live effect must pass doctrine, scope, validation and rollback checks before it is considered safe.
Autonomy is allowed only inside a defensive operating model. Protected routes stay closed, external writes require approval, and undefined scope is treated as a reason to fall back, not to guess.
The system uses before-state evidence, primary metrics, neighboring signals, abort criteria and observation windows to decide whether a later pilot is healthy or requires rollback.
The current reference run already demonstrates the read-only baseline: status 200, response 236.9 ms, HTML 183,759 bytes, sitemap 200.
Public content may include product pages, gated download explanations, support entry and documentation entry pages. Operator, customer, license and protected download paths remain blocked or non-public.
No. Licensing can enable eligibility, but it cannot remove doctrine, validation or rollback guardrails.
The system falls back to observe_only, blueprint_ready or approval_required instead of applying uncertain changes.
No. Route separation remains strict and protected prefixes stay blocked.
Continue into the plugin model to see how safe_mode, conflict checks and coexistence logic work together.