Method, coverage and security
Crado is the daily system of record for hardware and regulatory engineers: product facts, component changes, bench and lab measurements and regulatory limits, connected across every board revision. This specification says how it labels values, how it does the arithmetic, what it covers, how it is validated and how your data is isolated.
The four truth states
Every value in Crado carries one of four states. The state is enforced in code, so an estimate can never pass as a measurement.
- ● OBSERVED
- A value read directly from a measurement table or document, with the page and row it came from.
- ✓ KNOWN
- A fact an engineer has confirmed on a specific product revision.
- ≈ INFERRED
- A value or hypothesis the engine derives from observed and known inputs, shown with the rule and inputs behind it.
- ○ MISSING
- An input the evaluation needs that is not in the record. It is shown as missing, never guessed.
Full rules, including the no-silent-defaults guarantee and the confirmation boundary: The four truth states.
Deterministic arithmetic
Code does the math. Peak selection, limit evaluation, margins, harmonic correlation and before/after comparisons run in deterministic functions. The AI step only writes investigation notes, constrained to the sources the engine matched, and post-generation checks verify every number, sign, harmonic ordinal and citation before display. Every run records its rule versions and an input hash, so an old run can be replayed.
The pipeline and its checks: Deterministic arithmetic and coverage.
Coverage
Live today: radiated emissions under 47 CFR 15.109(a), Class B at 3 m, 30 to 1000 MHz, quasi-peak. Inputs outside that scope are refused with a reason rather than guessed.
Limit tables, refusal rules and what is on the roadmap: Coverage: 47 CFR 15.109.
Validation
1,462 passing unit tests across the engine modules, and 34 of 34 comparable readings on public FCC reports match the lab within 0.1 dB.
Suites, method and what is not yet measured: Validation.
Security
Each customer works in an isolated workspace. Crado does not use your schematics, product facts or test reports to train models for other customers, and the public precedent library holds only public regulatory filings.
Isolation, data handling and engineer authority: Security and workspace isolation.