AI safety and review

Kerf treats assistant work as document operations. The goal is that AI edits remain visible, reversible, and tied to the same undoable IR path as manual edits.

Current workflow

While a run is active, streamed operations drive a live preview overlay and the event log shows what the assistant is doing. When the run completes, committed operations land in the document timeline. The turn card then exposes Retry and, when a real pre-run snapshot exists, Revert. Revert rolls the document back to the snapshot before that turn.

This means the current shipped safety control is preview-then-revert, not a separate per-operation accept/reject queue.

Review habits

Before continuing modelling, inspect the feature tree, viewport, dimensions, and export-critical faces. Use the browser preview for quick feedback, then rely on the server render for the authoritative result. If the assistant misunderstood intent, use Revert, edit the prompt, and retry with clearer constraints or a screenshot.

Accept/reject follow-up

A stricter review mode—where assistant edits remain as a diff until the user explicitly accepts or rejects them—is a launch follow-up. Until that lands, do not assume an unseen diff queue exists. Use the visible turn history, live preview, and Revert action as the audit trail.