Approve before write-back
Kequan AI can draft changes in Writer, Calc, and Impress — but the main document does not change until you explicitly approve. This page explains the trust path in plain steps.
What problem this solves
Many AI tools rewrite files as soon as they answer. That is risky for contracts, official letters, budgets, and anything you cannot silently corrupt. Kequan Office separates draft generation from write-back: the model proposes; you decide.
Recommended path
- Open a real document (or create one from a template).
- Open Kequan AI (sidebar) or use inline edit with ⌘/Ctrl+K on a selection.
- Describe the goal in natural language, or pick a scenario chip when available.
- Review the draft and Diff — accept nothing yet.
- Click Approve write-back (or Tab on inline/ghost proposals). Use Esc or Reject to discard.
- If soft validation warns, read the card; force only when you understand the risk. Undo write-back if needed.
How the trust chain works
User intent / skill match → optional work-plan confirm (large tasks) → model draft (rewrite block / outline / formula …) → human Diff: approve or reject → DocumentAIApply write-back → soft validation + undo write-back
Confirming a work plan is not a permanent license for silent edits. Consult or QA answers without a write-back block stay consultative — they do not replace your selection automatically.
Inline edit and ghost proposals
Inline ⌘/Ctrl+K and ghost ⌘/Ctrl+. share the same chain as the sidebar: preview first, then Tab to approve or Esc to reject. That keeps keyboard-speed editing aligned with the same trust model.
Local-first and upload boundaries
Kequan is local-first: your default workspace is on-device. The product is designed not to silently upload full documents. Optional cloud quota, Device Code login to api.03122.com, or your own keys are separate tracks — they do not cancel the approve-before-write rule for the main document.
Limits to keep in mind
- One approval is one write-back, not infinite silent rewrite rights.
- Edit memory (for example “do not touch amount columns”) is stored locally per document.
- PDF understanding is not a full Acrobat editor.
- Post-write checks are soft signals; always spot-check critical numbers and names.
Related reading
FAQ
Will AI change my file without asking?
No. Write-back requires an explicit approve action (button or Tab on an inline proposal).
Is approving a work plan the same as permanent auto-edit?
No. Plan confirmation structures large tasks; each write-back still needs approval.
Can I undo after approve?
Yes. Use undo write-back when available, and keep normal document undo as a backup.
Does local-first mean I cannot use cloud models?
You can use optional cloud quota or BYOK, but the approve-before-write gate still applies to the main document.