Authentication
Clerk provides account authentication when configured. Server routes verify authenticated user context before protected workspace operations.
IMPLEMENTED BOUNDARIES
This page describes the current product architecture at a bounded level for evaluation and procurement. It distinguishes implemented controls from capabilities that depend on deployment health or configuration.
Clerk provides account authentication when configured. Server routes verify authenticated user context before protected workspace operations.
Model-provider credentials remain on server routes and are not intentionally exposed to the browser bundle.
The selected model determines the provider route. The workspace makes model choice visible rather than presenting all outputs as one undifferentiated system.
Policy-controlled tool actions can pause at explicit approval checkpoints before consequential execution continues.
The owned runtime includes a control plane, durable run state, model routing, policy logic, and approval continuation. Availability is deployment-dependent.
Supported chat and research workflows can continue through hosted fallback when configured. Fallback does not imply full Sovereign Core capability.
Isolated execution is a conditional runtime capability. If the required runtime is unavailable, workflows that depend on isolation remain unavailable rather than silently degrading.
Supported research and execution flows preserve sources or execution state so reviewers can inspect the basis of work rather than receiving only a final answer.
WHAT THIS PAGE DOES NOT CLAIM
EVALUATING TRACEREMOVE EXPERT?
Procurement and security questions can be handled during pilot scoping. We will answer against the current deployed product and documented runtime rather than future roadmap claims.
Review company pilot