Safety & recovery
Review a native approval
Review the exact document, targets and outputs covered by one native approval.
Before you begin
- A fresh native plan for the intended document with no earlier unresolved operation blocking it.
- Authority to make the proposed change and to write any proposed output destination.
Follow the steps
Identify the host and document
Read the host/process, document identity and revision in the approval. Compare with the document currently open in your host.
Checkpoint: The plan belongs to the document you intend to change, not merely a similarly named file.
Inspect the exact targets and units
Review affected object/element identities, counts, dimensions or typed parameter values, coordinate interpretation and warnings.
Checkpoint: The bounded target list and values match your intent; missing units or unsupported targets are not silently inferred.
Review any output separately
Check the granted folder and new filename. Rhino save-copy should preserve the active path; Revit Save As changes the active path and invalidates old bindings. Neither allows silent overwrite.
Checkpoint: You understand both the native change and the distinct file-output effect, if present.
Reject anything you need to edit
Reject a mismatched plan and request a corrected one. A manual document edit, new selection/arguments or expiry requires fresh validation and approval.
Checkpoint: The plan you are reviewing remains current. Approval expires after five minutes in the canonical design.
Approve once and wait for the receipt
Approve only the exact reviewed plan. Read structured dispatch/verification state instead of repeating the action when a response is slow.
Checkpoint: The original operation has a known status and a verified result or an explicit recovery hold.
Check the observed result
Inspect affected identities, values/geometry and any verified artifact against the plan. If anything is uncertain, preserve the original reference and stop further affected writes.
Checkpoint: The host readback supports completion, or the operation remains partial/unknown with a reconciliation path.
Check the result
- Approval authorizes one frozen native intent for the current actor/device, host and document, not an open-ended script.
- Rejecting or expiring an undispatched approval produces no native change; cancellation after dispatch does not guarantee undo.
If something goes wrong
The plan is expired, the document changed or Approve rejects a mismatch.
Refresh context and create a new plan. Do not reuse the old approval with replacement arguments.
Resume from: New immutable plan and fresh review.
A target is locked, unsupported or not eligible.
Stop and review the capability error. Do not unlock, ungroup, detach or alter ownership just to make the operation pass.
Resume from: Supported explicitly selected targets.
You clicked Stop after dispatch or lost the reply.
Read the original native operation and reconcile any uncertainty. Do not infer Undo or a usage refund.
Resume from: Proven original native outcome.
Need help?
Include your step and this reference.
Vector OS guide: /tutorials/native-approval
Guide updates
Review a native approval
Revision a9b5eb1628cb0aa9477bd098766c74b2ce6353296e4c5740a14a3c8d1ee82adf ·