How Solon turns overrides into policy
One decision function, four steps, and a human merge. Policy is code, and Git is the review trail.
Step 1: capture every decision
Solon wraps one decision function in your app. Each decision and the override that follows is stored append-only, with PII redacted per your policy. The evidence is audit-ready from day one.
Step 2: cluster the repeats
Similar overrides surface in a rolling window. One override is noise; a cluster is a missing rule. Three similar cases is enough signal to draft one.
Step 3: propose the rule as a pull request
Solon drafts the rule, with the evidence that motivated it, and opens a pull request against your policy repository. Policy is code, so the change is a diff, and the diff is reviewable.
Step 4: a human merges
Your team reviews the rule and merges it, or rejects it. Solon never merges its own proposals. A merged rule applies to every future decision, and the loop keeps compounding.
What you need to run it
- One integration point: the decision function Solon wraps.
- A Git repository for policies. Private is fine.
- Two to four reviewers, typically support managers.
Where the numbers come from
In a four-week simulation, 800 seeded decisions produced weekly escalations that fell from 28 to 0 while the traffic stayed constant. The evidence pack is available on request.
Keep reading
- AI decision governance: AI decision governance governs whether a decision was right, not just what an agent can do. Solon learns from human overrides and turns them into versioned policy.
- Refund and exception decisions, made consistent: Goodwill refunds and exceptions vary by manager and shift. Solon makes the precedent explicit, versioned, and consistent across every reviewer.
- Frequently asked questions: What AI decision governance is, how Solon learns from human overrides, what a design partnership looks like, and what stays a human decision.
- Work with us: A few teams running refund or exception decisions work with us directly. You keep your policy and evidence; your feedback shapes what we build.
- Built in the open: Solon's product principles, architecture, dated decisions, and build log are public. Curated in the open; every entry is merged by a human.
- Privacy note: What the Solon design partner form collects, why, where it lives, and how to have it deleted.
- See the loop on a real case: Walk one recorded refund case end to end: a System One model proposes, Solon escalates, you override as the manager, and three similar overrides become a policy pull request.