Hard authority precedence
Safety, legal, and company hard rules cannot be weakened by workspace, user, or session preference without exact delegated authority.
LOADING
Core explanatory content is server-rendered. This state is only for a route segment that is still resolving.
GOVERNANCE
Govern project, application, workspace, user, and session behavior with explicit hard authority, delegation, conflicts, approvals, audit, privacy, and retention.
DEFINITION
Behavior governance determines which rules are authoritative, where they apply, what lower scopes may customize, and what must happen when two authorities conflict. It is not a visual wrapper around latest-wins prompt precedence.
HOW IT WORKS
Resolve the exact active binding for each available scope in the current project and environment.
Build the deterministic ancestor chain without inventing missing intermediate bindings.
Apply hard authority precedence and exact parent-authored delegations before ordinary preferences.
Detect soft, hard, registry, mode, transform, verification, escalation, and delegation conflicts explicitly.
Produce one EffectiveBehaviorProgram with preserved source revision set and deterministic digests.
Carry approvals, audit, privacy, retention, deletion, and stale propagation through downstream evaluation and runtime artifacts.
PRODUCT PROOF
These fields describe the product evidence Vira preserves for this part of the lifecycle.
CONTROL BOUNDARIES
Safety, legal, and company hard rules cannot be weakened by workspace, user, or session preference without exact delegated authority.
Language, tone, length, and permitted presentation preferences remain separate from fraud, safety, legal, or company policy.
Hard conflicts make the composition unservable instead of being hidden behind latest-wins or most-specific-wins behavior.
Changes to Lessons, bindings, delegation, registries, privacy, or deletion can deterministically identify and invalidate affected downstream artifacts.
LIMITATIONS & FAILURE STATES
DEVELOPER HOOK
The control plane resolves the exact scope chain before projection so application code does not have to reproduce precedence or conflict semantics.