Validation evidence for rfx is kept on three pages, split by the question you are asking:
- Which configuration should I start from, and which calculator has narrower limits? Recommended Configuration — the uniform Cartesian Yee starting point, plus the per-calculator restrictions for waveguide, microstrip-line, lumped/wire, coaxial, graded-mesh and differentiable work.
- Is this exact combination supported, and what must fail? Support Boundaries — the status legend, the S-parameter API table, and the combinations that are required to raise rather than return a number.
- What has actually been measured, against what reference, with which pass
criterion? Benchmarks — every case in
validation/crossval/manifest.jsonwith its reference, gate and reproduce command. Cross-Solver Validation explains the exit codes.
A completed run, a clean preflight, and an exported artifact are none of these.