Does Veto move money?+
No. Veto does not move money, initiate wires, or touch your bank portal. It records the evidence state and the office's review before a covered instruction is acted on. The office decides and acts under its own escrow instructions and policies.
Does it replace Qualia, SoftPro, or ResWare?+
No. Veto is a control layer that sits on top of the system of record you already run. It integrates with it and writes back Review Records — it does not replace your production system, your email, or your verification vendors.
Isn't this just a checklist?+
No. A checklist can be completed and ignored. Veto models the covered instruction itself: it blocks the action when a record is missing or stale, requires a named approver for exceptions, and produces a reconstructable artifact. No Review Record, no covered instruction.
What is a “covered instruction”?+
It's an action your office policy says cannot proceed without review — for example, releasing seller proceeds, paying a payoff demand, accepting a changed destination account, or treating buyer funds as usable. You choose which instructions are covered.
Is Veto a certification that a file is safe?+
No. Veto never says “certified safe,” “fraud cleared,” or “legally approved.” It reports only what is true: control configured, Review Record present, limitations visible, exception recorded. It does not guarantee safety or clear fraud.
How does the green path stay fast?+
When sources are present and nothing has materially changed, an officer confirms the extracted values, reviews the limitations, and signs — a target of under sixty seconds. AI may prefill source rows, but officers confirm. Low-confidence inputs never silently prefill a record as current.
What happens when something changes after review?+
The prior Review Record is staled or superseded, the affected covered instruction is blocked, and a queue item is generated. A new v2 record or an owner-approved exception is required before the action can proceed.
Who's the buyer — is this developer-first?+
No. Adoption is owner- and policy-led, with product-led daily usage. An owner mandates the first covered instruction; officers use it on real files; the rule expands control by control. The API and developer motion come later.
