Safety, verification, and change review

Xorin combines plan review, structured tool validation, persistent checkpoints, and post-change verification. These controls reduce risk but do not remove the need for source control and project testing.

Use Plan mode before a large change

Plan mode creates a reviewable checklist before mutating tools run. You can disable steps, edit or reorder them, add instructions, answer required questions, execute the approved version, or cancel it.

The approved plan becomes the execution record; Xorin does not silently rewrite it after approval.

Verified Plan progress

A Plan step advances only when Xorin receives evidence that matches the approved action and target. A read-only inspection cannot complete a mutation step, an unrelated result cannot complete a verification step, and multiple required outcomes can be checked before a step is marked complete.

When a model requests several tool actions together, Xorin preserves and runs them sequentially. If a required action fails or cannot be verified, the Plan remains incomplete and identifies the failed action instead of presenting the request as successful.

Pending checkpoints

Before a supported mutation runs, Xorin snapshots the affected project state. The checkpoint is designed to survive script-triggered domain reloads and Editor restarts.

A checkpoint remains active until you keep or undo it. Follow-up requests made before that decision accumulate in the same checkpoint. The Changes applied section shows:

• View changes to inspect the affected targets and available script diffs.
• Keep changes to retain every accumulated change and release the checkpoint.
• Undo changes to restore the checkpoint baseline.
• Expandable line diffs for sealed script changes.
• Success and failure indicators for grouped actions.

Auto-approve

Enable Auto-approve in the composer to keep the active checkpoint after a normally completed request when every accumulated entry is successful. A cancellation, request error, or any recorded failed entry falls back to manual review.

Work activity and results

While a request runs, Xorin shows one current user-facing action. After ordinary success, low-level execution history is retained but hidden so the response and reversible outcome remain prominent. Enable Show detailed work activity in Settings to expose a collapsed execution record for successful turns. Failures, interruptions, and recovery information remain available without this setting.

Each request-owned task also provides Report. Reporting a task does not cancel, continue, retry, keep, or undo it. See Report a task.

Verification layers

• Structured tools validate inputs before mutation and verify important state afterward.
• Contextual warnings identify some incomplete component, physics, animation, and rendering setups.
• Script changes require a fresh Unity compilation and can enter a bounded repair loop.
• Play & Check and visual captures provide optional runtime and visual evidence.