Solon · AI decision governance
Built in the open
The thinking behind Solon is public: principles, architecture, decisions, and the build log. Every entry is curated, and every publication is merged by a human.
What is public
- Product principles: what Solon is and what it is not.
- Architecture: the packages and the decision loop.
- Dated decisions: context, options, and consequences.
- The build log: curated notes from each work session.
What stays internal
Competitive analysis, legal and trademark work, pricing, partner identities, and customer data stay private. The boundary and the gate are published in the repository, so the line is reviewable, not a promise.
How publishing works
Every change to the open work arrives as a pull request and is merged by a human. Nothing publishes without that merge. The history of the repository is the record.
License
The open work content is licensed CC BY 4.0. The source code is licensed separately; when the code repository opens, its license will be stated there.
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.
- 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.
- 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.