Frequently asked questions

Questions and answers

What is AI decision governance?

AI decision governance is the practice of making the business decisions behind an AI workflow explicit, reviewable, and consistent. Guardrails decide what an agent can do; governance decides whether what it did was right.

How does Solon learn from human overrides?

Every decision and override is recorded. Similar overrides cluster in a rolling window, and once three similar cases surface, Solon drafts a rule and opens it as a pull request.

Does the AI make the final decision?

No. Solon drafts rules and opens pull requests, and your team reviews and merges them. Merging policy is always a human action.

Where does the policy live?

In your Git repository, as versioned policy code. Every change is a pull request with its evidence attached, so the review trail is the audit trail.

What workflows can Solon govern?

Refund and exception decisions are the starting point. Integration is one decision function in your app, so a design partnership begins with the workflow you already run.

What is a design partnership?

A focused 30 days on one workflow. We help you get set up, work with you to encode your current exception practice as policy, and review the loop together as real decisions run through it. It is a collaboration, not a purchase.

Is the source code public?

The thinking is public: product principles, architecture, dated decisions, and the build log live at github.com/rubenabarron/solon-open. The source code repository is not public yet; when it opens, its license will be stated there.

How is our customer data handled?

Decisions are stored append-only, and PII is redacted per your policy. Justification text is best-effort scrubbed before it reaches a pull request, and the scope of that scrubbing is stated on the pull request itself.

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.
• How Solon turns overrides into policy: Capture every decision, cluster repeated overrides, draft a policy pull request, and keep the merge a human decision. The loop, step by step.
• 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.
• 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.