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
Support descriptive and executable rules as schema metadata #16
Extend the schema format so that qualitative guidance lives alongside structural validation, rather than only in documentation or agent prompts.
Motivation
JSON Schema validation (via AJV) answers "is this file structurally valid?" but not "is this content good?" There is a class of rules — particularly around planning quality — that are hard or impossible to express in JSON Schema but are important to capture somewhere inspectable.
Examples:
"Only one opportunity should be active at a time"
"An opportunity should be framed in the customer's voice, not as a business goal"
"Test the riskiest assumption across all candidate solutions before committing"
Proposed approach
Add a rules (or similar) key at the entity level in schema files — an array of rule objects.
Executable: an expression that tooling can evaluate against a set of nodes — for rules that can be mechanically checked (e.g. count(type='opportunity', status='active') <= 1). Format TBD (JSONLogic, a simple custom DSL, or similar).
Start with descriptive rules only. Design the structure to accommodate executable expressions later without breaking changes.
Activity
feat: executable rules and hierarchy validation (#21, #16)
feat: executable rules and hierarchy validation (#21, #16)
feat: executable rules and hierarchy validation (#29)