Four places where an agent should propose, not commit
The pattern is the same everywhere: the agent reads with read-only access and emits a change set, policy decides what auto-merges, a named human clears the rest, and a separate merge worker holds the only write credential. What changes is which fields are expensive to get wrong.
CRM hygiene
Deduplication, enrichment and normalization at volume — with field-level policy so formatting auto-merges and owner, stage and amount never do.
READ →U2Deal desk & pipeline
Amounts, close dates and stages drafted from the actual thread, routed by risk to the rep or the deal desk, and frozen once the close window ends.
READ →U3Finance & billing records
Reconciliation and corrections with a source document per amount, an approver who is not the proposer, and closed periods that stay closed.
READ →U4Regulated workflows
Policy as versioned code, mandatory evidence, separation of duties, and an append-only hash-chained trail you can export as an evidence pack.
READ →