Named Rules
Named Rules for Clearer, More Interpretable Graphs
We have introduced Names Rules, a new optional capability that makes knowledge graphs significantly easier to understand, validate, and maintain, especially as they grow in size or are generated automatically.
By allowing authors to assign descriptive, human-readable names to rules, this update reduces cognitive load, improves handover experiences, and increases trust in both manually authored and automatically generated graphs.
Clearer intent at a glance
Previously, understanding a graph often required decoding rule headers or reverse-engineering logic, particularly when working with auto-generated graphs or graphs created by someone else.
With Named Rules, authors can now label rules with descriptions such as:
“Calculate discount for loyal customers”
“Check if applicant has valid ID”
“Determine eligibility for premium support”
These names make the purpose of each rule immediately clear, allowing users to focus on validating and improving logic rather than deciphering it.
Easier navigation and editing
Named Rules become the primary reference points throughout Studio:
Rules can be found and identified more quickly in relationships with many similar rules.
Search now works across both rule names and rule headers.
Duplicating a rule preserves its name, reducing rework.
Authors can reference rules by name when documenting or reviewing changes, making collaboration and handover far simpler.
If a rule does not have a name, Studio continues to display the existing rule header exactly as it does today.
Seamless authoring in Studio and RBLang
Authors can add rule names in two ways:
In Studio: An optional name field is available when creating or editing a rule, with validation for length and restricted characters.
In RBLang: A
namefield can be added to any<relinst>element. For consistency, facts can include names in RBLang, but these are intentionally ignored by the Studio UI.
Rule names are optional, do not need to be unique, and are fully backward compatible with existing graphs.
Better auto-generated graphs by default
Graphs generated from documentation now include descriptive rule names automatically. These names are editable, giving users a clearer starting point when reviewing or refining the generated graph.
This improves understanding for new users and accelerates validation for logic for experienced users, making the output more transparent and trustworthy.
What stays the same
Rule logic and behavior are unchanged.
Legacy graphs and unnamed rules continue to work without modification.
Facts behave exactly as before in the Studio UI.
Named Rules do not introduce breaking changes or performance degradation.
Why this matters
Named Rules reduce the need for external handover documentation, screenshots, and written explanations. They make complex graphs easier to interpret, simpler to validate, and more approachable for new users—while still benefiting expert authors working at scale.
This is an important step toward making knowledge graphs clearer, more collaborative, and better aligned with real-world workflows.
Last updated