The Rule Repository Guide
The Code Effects Rule Repository is a place inside your own application where your organization keeps its business rules. A business rule is a decision written in plain words, such as "check if the order total is greater than 500 and the customer is new". Your application runs these rules on its real data to make decisions automatically. The Rule Repository is where people write those rules, keep every version of each one, test them on sample values, ask for approval, and choose which version your application uses.
You reach the Rule Repository through your application, signed in as you always are. The repository knows who you are, so every change it records names the person who made it, and it shows you only what your application allows you to do.
What you can do with it
- Write rules with the visual Rule Editor, which builds every rule from menus so a rule can never name a field that does not exist.
- Where your application offers the AI features, describe a rule in your own words and let the AI write it, or ask the AI Assistant questions about your rules.
- Keep every version of every rule. A saved version never changes, so you can always see exactly what was in use at any time, and compare any two versions.
- Test a rule on sample values before it is used, save those tests, and run them again whenever something changes.
- Choose which version of a rule is live, the one your application actually runs, and ask someone else to approve a version first.
- See who did what and when, and keep working notes on every record.
- Where your application records them, see every time a live rule ran on real data, what it read and what it decided.
The three parts of the Rule Repository
The Rule Repository comes as three parts. Your application may use one, two or all three of them; this guide has a section for each.
- The Rule Repository itself: the screens described in most of this guide, and the storage behind them. It holds your source objects, rules, versions, drafts, tests, notes and activity.
- Audit: records each time your application runs a live rule in real work, so that the repository can show those runs, replay them step by step, and count them. Without Audit, the Live Evaluations tab stays empty. See Audit.
- The MCP server: lets outside AI agents, such as Claude, work with your rules on your behalf, within the same permissions and approvals as people. See The MCP Server.
Who does what
- Business users and analysts write and test rules, keep drafts, and compare versions.
- Approvers review versions that others have asked to make live, and approve or decline them. Making a version live, taking one offline, approving and deleting are always done by a person, never by an AI.
- Developers add the Rule Repository to the application, describe the data that rules can use, and decide what each person may do. The Setting Up pages of each section are written for them.
How this guide is organized
- Getting Started shows the main screen, how grids and dialogs work, and walks through a first rule from start to finish.
- Source Objects explains the data your rules are written against and how it changes over time.
- Rules, Going Live and Testing cover writing rules, publishing them and checking them.
- AI Assistant and Keeping Track cover the AI features, activity, notes, deleting, permissions, themes and languages.
- Setting Up the Rule Repository is for developers.
- The Audit and MCP Server sections cover the other two parts, each ending with its own setup page.
If you are new, start with Getting Started, then follow Your First Rule.