Ledger — a governed write path for Salesforce
Four systems want to write to the same CRM record. Instead of letting them, every source submits a proposal and a gateway decides: identity resolution with Claude breaking ties, a per-field authority matrix with freshness decay, echo suppression for sync loops, and an append-only audit ledger. Watch a captured run of the real system, then break the rules yourself in the playground.
The walkthrough is a captured run of the real system— a live Salesforce org, live Snowflake, a live Claude call — replayed here, not re-run, because the gateway writes to a real CRM. The rationale you'll see in beat 2 was written by Claude during that run. The playground, though, runs entirely in your browser: same decision engine, ported line for line.
What to watch for
Beat 2: Clay's enrichment arrives with no domain at all, and Claude breaks the identity tie — with its rationale written into the audit trail.The flip
Beat 3: marketing's headcount of 40 wins, then loses to Clay's 180 one write later. Watch the record panel on the right — Name never moves.The catch
Beat 4: the gateway's own write comes back through marketing three times — the third time reformatted so exact matching fails. It's caught anyway.