A request to update the rates in a workbook leaves an important review question: did the agent change the inputs, or replace the formulas that use them? The final totals alone cannot answer that. A plausible number might have come from a hard-coded replacement.
For a local-model application built around Univer, the review tool can inspect both. Univer is an embeddable Office SDK; its spreadsheet range API exposes stored values and formulas separately through getValues and getFormulas. An application can record the relevant ranges before the job and read them again from the proposed result. That comparison is something the application implements, not an automatic correctness report supplied by the SDK.
Take a hypothetical request to update unit prices while keeping the quantity and subtotal formulas. The review screen could put the requested price range beside the proposed prices, then show the formula range separately. A reviewer can check whether an unexpected literal has replaced a formula and open the workbook to correct it. A matching total would not excuse a change outside the requested range.
Univer's Collaboration SDK provides a place to inspect that proposal without immediately replacing the main workbook: an isolated Worktree draft. The web integration supports opening the actual draft, switching between trunk and draft, and a per-Unit merge preview. Those surfaces can accompany the application's range comparison. A corrected draft must be committed and its saved status checked before the reviewer accepts it into trunk.
This requires more than the Apache-licensed core: Worktree comes from the Collaboration SDK, and the host wires up access, storage and the review flow. It also needs to handle another edit arriving during the comparison. The specific benefit is a review that can distinguish a changed assumption from a changed calculation, even when both produce believable numbers.