Products and revisions
A product is the device under investigation. A revision is a specific physical configuration of it: the board revision, and where relevant the firmware, enclosure, cables and operating mode used during the test.
Evidence belongs to the revision it was produced on. A new revision does not inherit earlier results. Where a later revision shares facts with an earlier one, the shared facts are recorded explicitly rather than assumed.
Requirements and applicability
A requirement is a rule, the version of that rule, and the basis for applying it to this product. For radiated emissions the basis typically includes the equipment class, the frequency range, the measurement distance and the detector the limit is defined for.
Applicability is recorded, not implied. If the basis for applying a requirement is unknown, for example the equipment class has not been stated, it is shown as missing and the check does not run.
Evidence and provenance
Evidence is a measurement together with its test conditions and a reference to where it came from. A value without its source is not used for evaluation.
| Field | Meaning |
|---|---|
| Frequency | Frequency of the recorded emission, in MHz |
| Level | Field strength as reported, in dBµV/m |
| Detector | Quasi-peak, peak or average |
| Distance | Antenna measurement distance, in metres |
| Polarization | Horizontal or vertical |
| Source | The document the value came from and its location, such as page or table |
Provenance is recorded at the level the source supports. A confirmed value keeps both its source reference and a record that it was confirmed.
Observations and hypotheses
Every item in an investigation carries one of four states. The states describe how something is known. They are not a verdict.
Recorded measurements and physical test results.
Confirmed product facts with supporting sources.
Likely causes requiring investigation.
Information needed before a check or decision can proceed.
Suggested tests, completed tests and confirmed causes
These three are kept separate throughout.
| Item | What it means | What it does not mean |
|---|---|---|
| Suggested test | A proposed next step, awaiting review | That anything has been measured |
| Completed test | A test that was run, with a recorded result and conditions | That the hypothesis it tested is true |
| Confirmed cause | An explanation an engineer has accepted on the basis of completed tests | That the fix holds on other revisions |
Agents, rules and review
A value starts as a proposal. When an agent reads a report, each value it finds is shown beside its source reference and labelled Inferred. A proposed value is never used for evaluation.
An engineer then confirms, corrects or rejects it. A confirmed value keeps its source reference and a record of who confirmed it. Only confirmed values reach the evaluation engine.
The engine applies the published rule to the confirmed values. If a required input is missing, or two readings are not comparable, the check is blocked, with the reason stated. Agents can request an evaluation but cannot change its result.
Results are reproducible: same confirmed inputs + same rule version = same result. The rule version is stored with every result, together with its inputs, revision and sources.
Reviews and historical decisions
A review records a decision, the evidence it relied on and the revision it concerns. Earlier decisions are preserved when new evidence arrives, so the reasoning behind a past next step can still be read.
A historical result stays attached to the revision it was measured on. It is not overwritten by a later retest on a different revision.