A requirement, buried in a document.
“Every approved supplier must have a valid certification on file.”
Example supplier policy · §4.2In development · Open to design partners
FROM REQUIREMENT TO RULE
Your rules deserve
a single source
of truth.
Stop losing business rules in PDFs, spreadsheets and code. Give every rule a source, an owner and a clear path to implementation.
A project by # minibota labs
02 / RULE Approved
One rule. Context included.
01
when supplier status is approved02
then certification must be valid03 / CHECK
Ready for an implementation.
A readable rule that engineering can turn into a test.
Illustrative workflow · product in development
BUILT AROUND THE RULE LIFECYCLE
- 01Define→
- 02Trace→
- 03Review→
- 04Version→
- 05Execute
THE PROBLEMThe rule is clear.
The rule is clear.
Until someone asks where it lives.
A policy says one thing. A spreadsheet checks another. A script quietly adds an exception. When a requirement changes, nobody knows what else needs to change.
The missing piece is a shared home for the rule itself.
Keep the source attached.
Record the document, section or decision behind a rule. A check should explain why it exists.
Make ownership explicit.
Give each rule an owner, a review status and a version. Changes become decisions people can follow.
Connect intent to execution.
Keep business meaning readable, then work toward checks that engineers can implement in the systems they use.
READABLE BY PEOPLE
A rule you can actually discuss.
RuleScript makes data expectations explicit: which fields are required, which values are allowed and how failures should be explained.
Explore the RuleScript referenceRuleScript documentation example · runtime in development
supplier-data.rs
validate "supplier_id": required,
on error "Supplier ID is required";
validate "price": number, min 0, max 10000,
on error "Price must be between 0 and 10000";
validate "country": required, in ["US", "CA", "MX"],
on error "Country must be US, CA or MX";WHERE IT FITSStart with the rules
Start with the rules
that need an explanation.
Standards & certification
Turn requirements into a reviewable set of rules, linked back to the relevant sections.
Supplier compliance
Clarify what a valid supplier record needs, who owns the check and when it should change.
Data contracts
Make expectations about fields, values and failure handling explicit between teams.
PROJECT STATUSA focused project.
A focused project.
An honest starting point.
RuleGenius combines readable validation and transformation rules with a focus on their context: sources, ownership, review and history.
Read about the projectToday
Product and language design, plus the preserved RuleScript reference.
Next
A rule repository, human review, DSL export and an initial local validation prototype.
Later
Production execution, APIs, streaming and integrations. Availability will be announced when ready.
FROM THE BLOG
All articles Better rules. Better conversations.
From a policy PDF to a rule you can trace.
How to turn a policy requirement into a reviewable business rule with a stable identifier, a source reference, an owner and implementation evidence.
Read articleA data contract needs more than a schema.
A practical guide to documenting data expectations, business constraints, ownership and failure handling before a supplier feed reaches production.
Read article