feat: add support for params - #418
Open
stefan-gorules wants to merge 2 commits into
Open
Conversation
ivanmiletic
approved these changes
Dec 3, 2025
|
@stefan-gorules @ivanmiletic Is there anything blocking this one? Happy to help if so. We run a large production deployment of JDM graphs for healthcare claims adjudication, and a substantial share of them carry a per-engine sidecar file of policy constants — code sets, effective dates, allowed modifier lists. Today our host merges that into the evaluation input, which means a policy and the constants it depends on are two separate artifacts that can version-drift independently. That has been a recurring source of authoring problems for us.
Two things we can offer, both inside what the contribution policy allows:
Not asking to jump the queue — just wanted to flag that there's a real user waiting on it, and to offer hands if the remaining work is the kind we can pick up. |
phenixrizen
added a commit
to phenixrizen/zen
that referenced
this pull request
Aug 27, 2026
Ports the `params` feature from gorules#418 onto current master. That PR branches from 61465bd (2025-11-24) and master is 93 commits ahead, including the walker rewrite in fe43b4c and the DecisionContent Graph/Policy split, so the original diff no longer applies; this is a reimplementation against the current shape rather than a merge. Params are decision-level constants declared on the graph document and exposed to every node as `$params`. Unlike evaluation input they travel with the decision, so a policy and the constants it depends on cannot drift apart. Following current master's design, `$params` is supplied as an isolate local alongside `$nodes` rather than being written into the input object, and is converted to a Variable once per evaluation. It is registered as a reserved property so it is stripped from results and traces. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
phenixrizen
added a commit
to phenixrizen/zen
that referenced
this pull request
Aug 27, 2026
Ports the `params` feature from gorules#418 onto current master. That PR branches from 61465bd (2025-11-24) and master is 93 commits ahead, including the walker rewrite in fe43b4c and the DecisionContent Graph/Policy split, so the original diff no longer applies; this is a reimplementation against the current shape rather than a merge. Params are decision-level constants declared on the graph document and exposed to every node as `$params`. Unlike evaluation input they travel with the decision, so a policy and the constants it depends on cannot drift apart. Following current master's design, `$params` is supplied as an isolate local alongside `$nodes` rather than being written into the input object, and is converted to a Variable once per evaluation. It is registered as a reserved property so it is stripped from results and traces. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
phenixrizen
added a commit
to phenixrizen/zen
that referenced
this pull request
Aug 27, 2026
Ports the `params` feature from gorules#418 onto current master. That PR branches from 61465bd (2025-11-24) and master is 93 commits ahead, including the walker rewrite in fe43b4c and the DecisionContent Graph/Policy split, so the original diff no longer applies; this is a reimplementation against the current shape rather than a merge. Params are decision-level constants declared on the graph document and exposed to every node as `$params`. Unlike evaluation input they travel with the decision, so a policy and the constants it depends on cannot drift apart. Following current master's design, `$params` is supplied as an isolate local alongside `$nodes` rather than being written into the input object, and is converted to a Variable once per evaluation. It is registered as a reserved property so it is stripped from results and traces. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
phenixrizen
added a commit
to phenixrizen/zen
that referenced
this pull request
Aug 27, 2026
Ports the `params` feature from gorules#418 onto current master. That PR branches from 61465bd (2025-11-24) and master is 93 commits ahead, including the walker rewrite in fe43b4c and the DecisionContent Graph/Policy split, so the original diff no longer applies; this is a reimplementation against the current shape rather than a merge. Params are decision-level constants declared on the graph document and exposed to every node as `$params`. Unlike evaluation input they travel with the decision, so a policy and the constants it depends on cannot drift apart. Following current master's design, `$params` is supplied as an isolate local alongside `$nodes` rather than being written into the input object, and is converted to a Variable once per evaluation. It is registered as a reserved property so it is stripped from results and traces. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
phenixrizen
added a commit
to phenixrizen/zen
that referenced
this pull request
Aug 27, 2026
Ports the `params` feature from gorules#418 onto current master. That PR branches from 61465bd (2025-11-24) and master is 93 commits ahead, including the walker rewrite in fe43b4c and the DecisionContent Graph/Policy split, so the original diff no longer applies; this is a reimplementation against the current shape rather than a merge. Params are decision-level constants declared on the graph document and exposed to every node as `$params`. Unlike evaluation input they travel with the decision, so a policy and the constants it depends on cannot drift apart. Following current master's design, `$params` is supplied as an isolate local alongside `$nodes` rather than being written into the input object, and is converted to a Variable once per evaluation. It is registered as a reserved property so it is stripped from results and traces. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
phenixrizen
added a commit
to phenixrizen/zen
that referenced
this pull request
Aug 27, 2026
Ports the `params` feature from gorules#418 onto current master. That PR branches from 61465bd (2025-11-24) and master is 93 commits ahead, including the walker rewrite in fe43b4c and the DecisionContent Graph/Policy split, so the original diff no longer applies; this is a reimplementation against the current shape rather than a merge. Params are decision-level constants declared on the graph document and exposed to every node as `$params`. Unlike evaluation input they travel with the decision, so a policy and the constants it depends on cannot drift apart. Following current master's design, `$params` is supplied as an isolate local alongside `$nodes` rather than being written into the input object, and is converted to a Variable once per evaluation. It is registered as a reserved property so it is stripped from results and traces. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
phenixrizen
added a commit
to phenixrizen/zen
that referenced
this pull request
Aug 27, 2026
Ports the `params` feature from gorules#418 onto current master. That PR branches from 61465bd (2025-11-24) and master is 93 commits ahead, including the walker rewrite in fe43b4c and the DecisionContent Graph/Policy split, so the original diff no longer applies; this is a reimplementation against the current shape rather than a merge. Params are decision-level constants declared on the graph document and exposed to every node as `$params`. Unlike evaluation input they travel with the decision, so a policy and the constants it depends on cannot drift apart. Following current master's design, `$params` is supplied as an isolate local alongside `$nodes` rather than being written into the input object, and is converted to a Variable once per evaluation. It is registered as a reserved property so it is stripped from results and traces. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
phenixrizen
added a commit
to phenixrizen/zen
that referenced
this pull request
Aug 27, 2026
Ports the `params` feature from gorules#418 onto current master. That PR branches from 61465bd (2025-11-24) and master is 93 commits ahead, including the walker rewrite in fe43b4c and the DecisionContent Graph/Policy split, so the original diff no longer applies; this is a reimplementation against the current shape rather than a merge. Params are decision-level constants declared on the graph document and exposed to every node as `$params`. Unlike evaluation input they travel with the decision, so a policy and the constants it depends on cannot drift apart. Following current master's design, `$params` is supplied as an isolate local alongside `$nodes` rather than being written into the input object, and is converted to a Variable once per evaluation. It is registered as a reserved property so it is stripped from results and traces. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.