Why Mend Waits for Approval Before Sending
Mend can prepare useful work inside Amend, but customer messages, financial actions and other consequential steps wait for a person to review and approve them.
This creates a clear boundary between assistance and authority. Drafting an invoice email is reversible. Sending it to a customer is an external action. Preparing a payment-related change is different from committing that change to the business record.
What an approval should show
A useful approval is specific. The user should see the proposed action, the customer or record it affects and the content or values that will be used. The system should not hide several unrelated actions behind a vague confirmation.
After approval, Amend can execute the supported action and record what happened. If the proposal is wrong, the user can reject or edit it before anything leaves the system.
Why this matters
AI output can be incomplete or mistaken. Business records can also contain old information. Approval gates give the person who understands the job a chance to catch the problem before it reaches a customer or changes money.
Routine read-only help does not need the same friction. Mend can search permitted records, summarize activity and prepare drafts while preserving the user's access limits. The gate appears when the next step carries real consequence.