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.

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 accept or undo it. Follow-up requests made before that decision accumulate in the same checkpoint and Change Log. The Change Log shows:

• Accept All to keep every accumulated change in the checkpoint.
• Undo All to restore the checkpoint.
• Expandable line diffs for sealed script changes.
• Success and failure indicators for grouped actions.

Auto-Accept

Enable Auto in the composer to accept 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.

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.