The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →A calculation tool can show a result without showing why its inputs deserve trust. Evgenii Buchinskii’s proposal is to give every decision-relevant input one provenance class: a concise label for where it came from, separate from what quantity it represents. The six labels make standards, manufacturer data, project decisions, assumptions, overrides, and derived values easier to distinguish during review. They are a deliberately simple proposal—not an adopted IEC, ISO, or industry-standard taxonomy.
What provenance classes are meant to show
Provenance answers “where did this value come from?” It does not tell you whether the equation using that value is correct. Buchinskii puts the distinction this way: “Traceability tells you where every number came from; validation tells you whether the method is right.” A calculation can be traceable and still use a wrong equation; conversely, a method can be validated while a reviewer remains unable to inspect the inputs behind a particular result.
As an Amazon Associate I earn from qualifying purchases.
The proposal assigns one class to each decision-relevant input. It is not a graph database or semantic layer, and it does not by itself capture every detail of a value’s history. Its aim is more modest: make the type of source visible enough that a reviewer knows what to check next.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The six classes and the review failures they expose
| Class | What the label means | What a reviewer can investigate |
|---|---|---|
| Normative | A clause in a named standard edition. | Whether the calculation used the intended edition and method, rather than an outdated or unspecified reference. |
| Manufacturer | Information from a datasheet, catalogue, or type-test report. | Whether a value is measured or merely typical, and whether its source document revision is still applicable. |
| Project | A decision recorded for a specific project. | Whether a site-specific limit or choice has mistakenly been treated as a general physical constant or copied into another project. |
| Assumption | A selected value used because the real value was unavailable. | Whether a weakly supported input is being presented with the same apparent certainty as a sourced value. |
| User override | A library value manually replaced by a user. | Whether a changed default is affecting the result, even if it is not obvious in the main calculation view. |
| Derived | A value calculated from other inputs. | Whether dependent values recalculate when a parent input changes. |
The labels identify different review questions, not different engineering quantities. For example, a soil thermal resistivity input could be marked as an assumption if it was selected because the actual value was unavailable. Buchinskii uses this as an example of an input that can strongly affect a cable calculation, but provides no measured distribution or sensitivity study to quantify how often it occurs or how much it changes results. The practical value of the label is that the reviewer can see the uncertainty instead of mistaking the number for a measured project fact. As Buchinskii writes, “Marking it does not weaken the result. It tells the reader where to push.”
#1 Best Overall
Keep normative references edition-specific
A standard name without an edition can become ambiguous when the reference changes. Buchinskii’s example is IEC 60909-0: a saved result that says only “per IEC 60909” does not make clear which edition or calculation method it used. The IEC catalogue lists IEC 60909-0:2016 as withdrawn on 2026-07-23 and identifies the newer IEC 60909-0:2026, Edition 3.0, published on that date.
IEC describes the 2026 document as covering calculation of short-circuit currents in low- and high-voltage three-phase AC systems operating at 50 Hz or 60 Hz. Its catalogue states that systems with highest voltages of 550 kV and above and long transmission lines are outside the document’s scope. Those scope details matter: an edition label helps identify a method, but does not establish that the method applies to every system.
Rank #2
Buchinskii’s recommendation is to record the standard identifier, edition or year, and relevant clause, rather than storing an unversioned standard name. A calculation tool could also flag a cited edition when it has been superseded. That would help reviewers distinguish a result that was knowingly produced against an earlier requirement from one whose reference became unclear over time.
Provenance is not an audit log or a validation result
A provenance class describes the status or source category of a value. An audit log answers different questions: who changed a value, what changed, and when. A robust review may need both. A “user override” label can reveal that a library value was replaced, for example, but a separate change history is needed to identify the person and timing.
Neither mechanism proves the calculation method is valid. Provenance makes inputs inspectable; validation checks whether the method is right. As Buchinskii cautions, “A fully traceable wrong equation is still wrong, and a validated black box is still unreviewable.” The two concerns should be evaluated separately rather than treating detailed input labels as proof of correctness.
What a calculation report could make visible
Buchinskii recommends reporting more than a binary PASS or FAIL. A useful report should identify the criterion that governed, the numerical margin against it, and the weakest input together with its provenance class. This gives a reviewer both the result and a practical starting point for challenging its basis.
- Governing criterion: name the requirement or limit that controlled the outcome, with its edition and clause when it is normative.
- Numerical margin: show the result alongside the requirement, using the relevant units and making clear how much reserve remains.
- Weakest input: identify the input considered least supported and show its class and source status.
The examples in Buchinskii’s article illustrate the idea rather than report measured project outcomes: “Margin: 185 mm² installed against 154 mm² required” and “Weakest input: k = 115 — class assumption, no source recorded.” Likewise, the contrast between a PASS with 3% reserve and one with 40% reserve is illustrative, not a field statistic or controlled-study result. The point is that the same status can conceal materially different margins and input quality.
Use review questions to test the model
Buchinskii frames the design-review question as “what would have to be wrong for this result to be wrong.” A provenance label can direct that question toward a standard edition, document revision, project decision, assumption, manual change, or dependency that failed to update.
Best Value
His motivating cable-schedule scenario describes a listed size changing from 95 mm² to 120 mm² even though, in the scenario, nothing in the project changed and no one knew which input had moved. It is an illustrative framing, not a verified incident report. A tool that exposes changed inputs, their provenance classes, and derived dependencies would make that kind of unexplained change easier to investigate.
The six-class scheme should therefore be treated as a lightweight review aid, not a substitute for engineering judgment or quality controls. Its usefulness depends on recording provenance accurately and pairing the labels with edition-aware references, change history where needed, and method validation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →
