research: add SYM-ARCH-002A5 differential benchmark validation - #61
Draft
Tristan-Stoltz-ERC wants to merge 10 commits into
Draft
research: add SYM-ARCH-002A5 differential benchmark validation#61Tristan-Stoltz-ERC wants to merge 10 commits into
Tristan-Stoltz-ERC wants to merge 10 commits into
Conversation
This was referenced Aug 25, 2026
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
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.
Summary
Adds SYM-ARCH-002A5 differential/reference validation as a draft sibling of #60, stacked directly on #59 / A3.
A3 establishes internal structural/oracle consistency. A4 attacks trivial learner shortcuts. A5 addresses another failure mode:
A5 adds a separately implemented RuleExpr evaluator, exhaustive finite-domain comparison, projected coverage accounting, and an optional independently frozen train/evaluation partition.
Any discrepancy yields
INCONCLUSIVE_BENCHMARK; it is never converted into an architecture win/loss.Independent reference evaluator
reference_evaluate_ruledoes not call A3'sevaluate_ruleand separately implements:Both implementations are evaluated on every assignment in the frozen finite factor universe.
A disagreement does not decide which evaluator is correct; it invalidates the benchmark until resolved.
Finite reference universe
DifferentialValidityPolicyfreezes:Every RuleExpr feature must be represented in the factor domain. Duplicate domain values, missing factors, overflow, and universes above the cap fail closed.
Factor projection / nuisance handling
Strict mode requires generated examples to expose exactly the declared reference factors.
Relaxed mode permits extra nuisance features, but reference truth, coverage, duplicate detection, and partition identity use only the declared-factor projection. Nuisance features therefore cannot inflate coverage or make the same task assignment look novel.
A regression test specifically guards this behavior.
Generated dataset checks
A5 checks:
The report records a domain-separated digest of the sorted independent reference truth table.
Optional reference partition
A separately frozen
ReferencePartitioncan define the exact expected train/eval assignments. A5 compares generated split membership against it after projection.This catches a generator that keeps labels correct but silently moves examples across the held-out boundary.
For scientific independence, the partition should come from a separately reviewed pure partition specification or other reference path—not be copied from generated output after inspection.
Fail-closed behavior
A5 returns only:
passed;inconclusive_benchmark.Violation categories distinguish:
Malformed benchmark data remains a validity report rather than escaping as an execution error during partition comparison.
Tests
Focused tests cover:
CI
Adds
SYM-ARCH-002A5 Differential Validitywith targeted rustfmt, focused A5 tests, andcargo check -p symthaea-psych-bench --lib.Wording ceiling
A pass supports only:
It is not a formal proof of task correctness and does not establish any Symthaea architecture advantage.
Depends on #59. Sibling of #60. Tracks #55.