The Rules Copilot is designed so you stay in control:
- Nothing is created without your confirmation. Across chat, spreadsheet import, and manual extraction, no rule is saved until you confirm and save it.
- Business language only. The Copilot uses business language and does not expose Python or internal trigger syntax.
- It asks when unsure. When input is ambiguous, the Copilot asks a clarifying question, and it keeps context across the conversation.
- Safe defaults. New rules default to Hard Reverse off, Agency Exceptions set to None, and Transaction Type set to All.
- Conflict warnings. If a new or imported rule conflicts with an existing one, the Copilot warns you before you confirm.
- Validation before save. Each rule is validated against BriteCore's rule schema and the existing rules for the scope before it is saved, so an invalid or duplicate rule is reported rather than created.
- Your permissions apply. The Copilot acts as you. It cannot create or change rules you could not create or change yourself.
- Full audit trail. Every change is attributed to you and recorded in Notes as made through the Copilot. Conversations are retained so an administrator can review what was asked and what was done.
Recommended Practice
- Build and import rules in your UAT environment first.
- Test the rules with sample quotes, claims, or invoices that should and should not trigger them.
- Promote the validated configuration to production following your normal release process.
