FIELD NOTES & TECHNICAL ARCHIVE
A Field Note has earned publication through a result, artifact, failure, and boundary. A working note offers a useful framework without pretending that a measured case already exists.
New to programming or ML validation? Build the small baseline before reading the longer cases.
FIELD NOTES
These pieces state what was observed, what can be inspected, what failed, and where the authority stops.
Read the Field Notes publication contract →
The first part of a surrogate-model series, defining what pass means in a traceable LLC workflow before expanding design diversity.
DecisionDecide whether a candidate record supports proceed, rework, review, or abstention without confusing software execution with electrical evidence.
Published Field Note backed by a rebuildable simulation-only campaign at one frozen operating point.
WORKING NOTES
Use these to structure a decision or evaluation. Their evidence status remains visible so a framework is not mistaken for a qualified result.
Four practical uses of AI for power-electronics engineers, explained through familiar design, simulation, and waveform work.
DecisionIdentify one bounded engineering task where data-driven assistance may be worth testing.
Introductory synthesis of primary research and official evaluation guidance; figures are original illustrations and equation calculations, not model or hardware results.
A plain-language acceptance path for deciding when a fast engineering estimate may be used, when it needs a warning, and when it must abstain.
DecisionChoose whether to use an estimate, show a warning, request higher-fidelity evidence, or abstain.
Working acceptance framework; it reports no project-specific qualification result.