You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add a more expressive condition language for controls #88
Add a more expressive condition language for controls so a single control can combine multiple conditions.
Motivation
Some policies need to reason over more than one condition at once, and splitting that logic across several controls is awkward and harder to manage.
Current behavior
A control effectively captures a single condition, so more complex logic has to be modeled across multiple controls or pushed into evaluator internals.
Expected behavior
A control should be able to express multiple conditions in one place with clear composition semantics.
Reproduction (if bug)
N/A
This is a feature request.
N/A
Proposed solution (optional)
Introduce a more expressive control condition model, likely supporting boolean composition such as and, or, and not, while keeping authoring simple.
This shipped in #115 and merged to main in 2ff4c12 on March 17, 2026.
That work introduced recursive condition trees so a single control can express nested and / or / not composition, along with rollout compatibility for legacy flat controls, migration support, recursive validation/evaluation, and SDK/UI contract updates.
Summary
Motivation
Current behavior
Expected behavior
Reproduction (if bug)
Proposed solution (optional)
and,or, andnot, while keeping authoring simple.