LOADING
Core explanatory content is server-rendered. This state is only for a route segment that is still resolving.
TEACH
Capture reviewed corrections as governed evidence with scope, registered facts, counterexamples, and provenance before anything can change production.
DEFINITION
Teach turns a human correction into reviewable evidence. It does not grant deployment authority, silently edit an active prompt, or convert one conversation into company policy.
HOW IT WORKS
Start from an exact runtime trace or another source with explicit provenance.
Record what was wrong and what should have happened instead.
Select only registered signal keys that materially affected the judgment; raw signal values are not marketing or teaching metadata by default.
Choose the intended authority scope and state where the correction must not apply.
Preserve the correction, rationale, counterexample, source trace, and reviewer identity as governed evidence.
Review the evidence before it can contribute to a Lesson, candidate, evaluation, or later behavior revision.
PRODUCT PROOF
These fields describe the product evidence Vira preserves for this part of the lifecycle.
CONTROL BOUNDARIES
Teach creates governed evidence. A correction cannot make itself active merely because a reviewer submitted it.
Project or application scope is selected deliberately so a local correction does not silently become broader policy.
Reviewers can state where the correction should not apply, preventing a useful example from becoming an over-general rule.
Source evidence can be traced forward into Lessons, candidates, evaluations, revisions, deployments, and runtime explanations.
LIMITATIONS & FAILURE STATES
DEVELOPER HOOK
Resolve behavior, preserve the returned trace identity, then submit feedback or teaching against that exact execution rather than reconstructing context later.