LOADING
Core explanatory content is server-rendered. This state is only for a route segment that is still resolving.
DEPLOYMENTS
Promote immutable behavior revisions through explicit release states where online health produces evidence but never silently becomes promotion authority.
DEFINITION
A Vira deployment binds an exact behavior revision and its release evidence to an application and environment. Shadow, canary, active promotion, stop, and rollback are separate governed actions.
HOW IT WORKS
Seal the exact candidate and promotion evidence required by policy.
Prepare the deployment without serving the candidate as authoritative traffic.
Run shadow execution when online evidence is needed without changing the served response.
Review shadow health and explicitly authorize a bounded canary.
Collect canary health against the same revision, artifact, scope, and model target.
Promote to active only through explicit release authority, or stop and roll back to a known exact revision.
PRODUCT PROOF
These fields describe the product evidence Vira preserves for this part of the lifecycle.
CONTROL BOUNDARIES
The deployment points to a known behavior revision and artifact identity rather than whatever happens to be latest.
Shadow and canary health inform the next decision but do not auto-promote production authority.
Canary scope is explicit so a candidate can be observed under production conditions without silently becoming universal.
Rollback creates a deliberate release event to a previously known exact revision rather than restoring an ambiguous historic latest.
LIMITATIONS & FAILURE STATES
DEVELOPER HOOK
Deployment operations are strongest when runtime credentials, application scope, evaluation evidence, and rollback targets remain explicit throughout the release.