Diagnostic required

Runtime is intentionally gated.

Verellix needs enough company context to route the user safely.

The diagnostic prevents users from landing in the wrong workspace or bypassing readiness checks.

All gates are required and sequential.
Confirmation state
DiagnosticRequired
RoutingPending
Runtime accessPending
Gate active - action required
Next routing

What happens after this page.

Step 01

Complete diagnostic

Answer the operating context questions that determine your route, workspace, and authority level.

Step 02

Resolve commercial state

Paid or trial access is matched against the user account and entitlement boundary.

Step 03

Continue onboarding

Routed to company setup, portfolio readiness, or team assignment based on diagnostic output.

Important notes

Keep expectations precise.

Access

No runtime bypass

Payment or invitation does not bypass diagnostic, onboarding, governance readiness, or local authority. All gates are required and sequential.

Setup

Company baseline first

Users must complete minimum company context before being routed into any execution surfaces. Incomplete baselines cannot be promoted.

Support

Human help if blocked

If access context is incorrect or disputed, contact support rather than creating duplicate accounts. Duplicate accounts cannot be merged retroactively.