Check that the spec, the program and production still agree — and when they do not, see who owns the number. The dashboard joins every requirement to its test and its production data, reconciles the spec's limits against the program's and the program's against what the latest lot actually ran, and attributes every disagreement to the artefact that owns it. It is the one surface where all four pillars (spec, program, board and production data) are read together.
| Question | Answer |
|---|---|
| Is every requirement tested? | A requirement no test implements, and a program test no requirement asks for, are both listed. |
| Does the program still meet the spec? | Program limits and force conditions are reconciled against the spec. A program looser than the spec is a compliance error. |
| Did production run today's limits? | The limits the latest lot recorded are compared with the program as it stands now, and a difference is reported as drift — never mislabelled as a spec violation. |
| Does the board carry what the program drives? | Program pins are checked against the board's nets, and each requirement is followed through to routed copper. |
Every verdict comes from a deterministic engine: there is no language model in the pipeline, so the same artefacts always give the same answer. It recomputes on every load from the live artefacts and labels which copy of the program it read — the open workbook or the last ingested one. Ask the IG-XL agent whether the spec's guard bands reached the program and production and it calls the same reconcile.
Values are compared by what they mean, so a limit written in milliamps in one artefact and in amps, in scientific notation, in another compares as equal. Test names are allowed to drift between spec, program and lots, because those joins key on test number; board joins key on net names and allow only the usual DUT and tester-side prefixes, so a net renamed any other way is reported as unmatched, never guessed. In a real project the limit sources legitimately differ, and the difference between “the lot ran at a recorded limit” and “the program violates the spec” is the difference between a finding and a false alarm.
On the demonstration project: 16 / 16 requirements joined spec → program → lot (presence on test number, not correctness), and one compliance error — a guard band planted in the demonstration data, tightened in the spec after generation, which the program never picked up. Lots are seeded synthetic data with planted defects.