[ PROOFECONOMY ]™GlossaryOriginSpecsComparability Class
A Comparability Class is the tuple that makes two Performance Records comparable: the same technology profile, the same Mine Plan composition and version, the same Environment Class, the same Parity Declaration class or Reference Environment version, and the same Regulatory Regime set. Records compare only within one class, and Control Provenance is never part of it.
What it means
Two numbers are comparable only when they were produced by the same test in the same kind of place. A WAF tested with web canaries in a lab replica and an agent guardrail tested with jail runs in pre-production share a scale, since one reader with one parser reads both, but not a class.
The rules
- Any table, ranking or statement that places two Providers’ records side by side states the class and never mixes classes.
- In-Situ records from different Implementors compare only through the Reference Environment they most closely match, and only when the Parity Declaration says so.
- Control Provenance is not a class component. A commercial control, an open source control and a custom control under the same Mine Plan, Environment Class and parity are comparable and may be placed side by side. The provenance and any
self_providedflag are shown so a reader can weight them; the record does not. - The class is decided by what was fired and where it landed, never by what the control is called or what it protects. A WAF in front of an agent’s HTTP API, tested with web canaries, is in the Web Application class; the agent behind it does not change that.
- A control tested under two profiles produces one record carrying one class per profile. Comparison happens per profile.
- Records under an
x-technology profile are comparable only to each other.
Related terms
- Environment Class and Parity Declaration
- Mine Plan and Engagement Manifest
- Performance Record
- Self-Provided Engagement
- SUT, DUT, CUT and AUT