FIELD NOTES / EVIDENCE BEFORE CADENCE
Rafael Collado breaks down one bounded, rebuildable power-electronics workflow: the baseline, the evidence, what was automated, what failed, where the system must abstain, and what another engineer can reuse.
CHOOSE YOUR ENTRY POINT
Every route below is public. Email remains optional and appears only after the case and editorial contract.
ISSUE 001 / PUBLISHED FIELD NOTE
Field Note 001 publishes the result, reusable artifact and preserved method failure from a rebuildable 200-candidate LLC workflow.
VERSIONED, REPLAYABLE SIMULATION CAMPAIGN
The v1.0.0 evidence archive contains 200 deterministic candidate records: 32 FHA rejects and 168 single-point passes from the switched-linear-equivalent model, with a public verifier, replay procedure and reader-facing Quickstart.
The result is bounded to one operating point and a simplified equivalent model. It is not hardware approval, multi-point validation or proof of equivalence to a higher-fidelity solver.
EDITORIAL CONTRACT
The format is designed to expose the decision, evidence, limitations, and reusable output, not to stretch a general principle into an article.
The decision the workflow is intended to improve.
Topology, ranges, power level, frequency, and material constraints.
How an engineer would handle the decision without the proposed system.
Inputs, calculations, rules, simulations, models, and outputs.
What changed, what remained fixed, and how the result was evaluated.
A table, plot, waveform, error matrix, timing result, or equivalent record.
A case where the method produced a wrong, weak, or insufficient answer.
When the system proceeds, warns, requests evidence, or abstains.
A checklist, template, notebook, schema, script, or framework.
A concrete way to apply the method, inspect the artifact, or propose a case.
Traceable to a named source, record, or artifact.
A reasoned reading of the available evidence.
A condition adopted for the work but not independently verified.
Evidence that is still absent or a question that remains open.
The technical archive and runnable resources remain open without email.