Arbiter/core
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

js-rigor: remove the useCompiled option entirely — clean cut

Browse Source 
The compiled evaluator is gone, so useCompiled: false is inert. Removed
every remaining reference: the TTU matrix pin's redundant fallback check,
the OWA wrapper's useCompiled parameter, the comparator full-path test's
redundant rule-path check, and the compiled-rule-parity campaign (which
existed solely to compare the two paths — now trivially identical).
The RuleCompiler remains as the config validator; _compiled metadata
still rides in snapshots.
This commit is contained in:
John Dvorak
2026-08-02 10:29:54 -07:00
parent dcd90840d7
commit 8037b97bea
3 changed files with 5 additions and 191 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/rigor/comparator-full-path.test.js
+1 -5
View File
@@ -83,11 +83,7 @@ describe('Relational comparator full-path parity (rigor)', () => {
} else if (res.reason !== 'values_compared_comparison_false') {
fail(`${tag}: expected reason=values_compared_comparison_false, got ${res.reason}`);
}
// Rule-path parity
const rulePath = arb.check('user:alice', 'premium', 'doc:secret', { useCompiled: false });
if (Math.abs(rulePath.possibility - expected) > EPS) {
fail(`${tag}: rule path ${rulePath.possibility} vs expected ${expected}`);
}
// Binary decision parity
const bin = arb.check('user:alice', 'premium', 'doc:secret', { binary: true, minAllowPossibility: 0.5 });
if (bin.allow !== (expected >= 0.5)) {