Skorpen Academy ยท Gate 2 review surface

LLC curriculum, tests, and exact simulator plots

This compact index covers the accepted 10-module, 56-lesson curriculum in order. It binds 18 tests and 18 quantitative plot jobs to 26 accepted P3 scenario manifests. It is a review candidate, not an acceptance claim.

10 modules56 lessons18 tests18 plots5 no-test rationales

Chapter 1 counterfactual: the hard-switching case is an avoided-cost teaching counterfactual. It is not nominal LLC loss or measured efficiency.

Module 01

Why resonance changes the design problem

les-01-02

The complete LLC power path: bridge, tank, transformer, rectifier, and output filter

Outcome: Classify each power-stage block and state its energy-transfer role.

Decision: Decide where a proposed observation or loss belongs in the power path.

Evidence: no_simulator_evidence

Specific no-test rationale

A static labelled schematic and learner annotation are the direct evidence; numerical interaction would add false precision before interval analysis.

Learner action: Annotate a static power-path schematic.

Observable: Bridge, tank, transformer, rectifier and output-filter boundaries.

Module 02

Follow the energy through a switching period

Module 03

Build the design model and know where it lies

Module 04

Operating regions and soft-switching boundaries

les-04-05

Startup and fault trajectories across region boundaries

Outcome: Trace startup and declared fault movement across frequency region current output and protection states.

Decision: Choose or reject a startup and fault-response sequence based on region crossings current limits and reproducible state order.

Evidence: switched_model

Module 05

Translate requirements into a tank and turns ratio

Module 06

Make the transformer part of the tank deliberately

les-06-03

Integrated versus external resonant inductance

Outcome: Compare integration choices across tolerance loss construction and measurability.

Decision: Choose an integration strategy and list the evidence needed to control it.

Evidence: no_simulator_evidence

Specific no-test rationale

The lesson is an implementation-architecture comparison whose decisive inputs are construction capability tolerance ownership and measurement access, not a numeric plant response.

Learner action: Complete a qualitative architecture trade-off table.

Observable: Construction dependencies, tolerance ownership and measurement access.

les-06-04

Winding arrangement, capacitance, coupling, fringing, and tolerance

Outcome: Trace how winding construction changes parasitics and uncertainty.

Decision: Specify which construction variables and measurements must be controlled.

Evidence: no_simulator_evidence

Specific no-test rationale

The accepted depth is causal construction reasoning and evidence planning; a generic simulator would hide geometry and material assumptions that this lesson must expose.

Learner action: Annotate a winding and field-risk diagram.

Observable: Coupling capacitance fringing and tolerance mechanisms.

Module 07

Secondary rectification and output behaviour

Module 08

Control the nonlinear plant across its whole journey

Module 09

Loss, tolerance, and verification close the design loop

les-09-01

Primary conduction, turn-off, gate-drive, and residual hard-switching loss

Outcome: Build a source-badged primary loss budget across operating points.

Decision: Identify the primary loss term that needs design action or better evidence.

Evidence: component_model

les-09-02

Resonant capacitor, copper, core, fringing, and proximity losses

Outcome: Separate tank and magnetics loss mechanisms by equation model or measurement source.

Decision: Choose which construction or component change addresses the dominant supported loss.

Evidence: component_model

les-09-03

Secondary conduction, switching, and output-capacitor losses

Outcome: Attribute secondary and output losses across rectifier modes and load.

Decision: Select rectifier and capacitor changes based on the supported dominant term.

Evidence: component_model

les-09-06

Probe choice, safe waveform capture, tank measurement, and evidence quality

Outcome: Design a safe measurement plan with bandwidth reference and uncertainty controls.

Decision: Decide whether a proposed capture can support the intended engineering claim.

Evidence: no_simulator_evidence

Specific no-test rationale

The evidence is a safety-critical measurement plan and capture audit; a simulator cannot validate probe isolation loading bandwidth or operator procedure.

Learner action: Complete a probe and capture evidence checklist.

Observable: Safety reference loading bandwidth de-embedding and uncertainty requirements.

Module 10

Decide whether LLC is the right architecture

les-10-01

Efficiency, density, cost, control, and range trade-offs

Outcome: Compare LLC with alternatives using requirement-linked evidence and uncertainty.

Decision: Defend architecture selection or rejection without a hidden weighted winner.

Evidence: comparison_fixture

les-10-02

Wide line/load range, hold-up, transient, paralleling, and bidirectionality limits

Outcome: Identify requirement categories that strain or exclude a basic LLC architecture.

Decision: Decide whether added stages complexity or an alternative architecture deserves evaluation.

Evidence: comparison_fixture

les-10-03

When phase-shifted bridge, dual-active bridge, CLLC, or another stage deserves evaluation

Outcome: State the trigger that makes each named alternative worth a separate evaluation.

Decision: Select which alternative enters a follow-on study and what evidence that study must produce.

Evidence: no_simulator_evidence

Specific no-test rationale

This lesson defines when to commission a separate architecture study; comparing unscoped models would fabricate precision and duplicate courses not accepted at Gate 1.

Learner action: Map requirements to alternative-architecture study triggers.

Observable: Directionality range control device and implementation distinctions.

les-10-04

Independent capstone design review and uncertainty register

Outcome: Produce an evidence-backed architecture and design judgement with explicit unknowns.

Decision: Approve revise reject or request evidence for the proposed LLC design.

Evidence: comparison_fixture

Complete inventory

Required tests

llc-t01-ch1-commutation-comparison Includes Chapter 1 counterfactual

Hard switching counterfactual and nominal ZVS

Question: What cost is avoided when the nominal commutation current slews the switch node to zero before turn-on?

Purpose: Isolate only the sign of commutation current at the frozen nominal point and distinguish avoided counterfactual loss from nominal converter behavior.

Model/evidence level: switched_model

Learner controls

  • scenario_selector: select exactly one frozen case
  • frozen_parameters: inspect values without editing

Observables

vSw [V], iComm [A], residualVdsAtTurnOn [V], chargeShortfall [C], linearOverlapEnergyEstimate [J], zvsAchieved [boolean]

Expected result

  • hard_switching_counterfactual: residualVdsAtTurnOn equals 390 V and zvsAchieved is false
  • nominal_zvs: residualVdsAtTurnOn equals 0 V and clamp time is 58.925711111872716 ns after dead-time start
  • identity: ordered arrays and 191 point count match export exactly

Limitations: One static commutation edge only; Constant signed current during dead time; Lumped total charge rather than nonlinear capacitance; Linear overlap screen is not device switching-loss integration; Parasitics ringing reverse recovery and driver dynamics are excluded

Prohibited inference: The 52.94802456797902 uJ and 12.48 W values are avoided counterfactual cost, not nominal LLC loss or measured efficiency.

llc-t02-full-period-energy-paths

Full-period LLC current paths at three frequencies

Question: How do bridge, resonant, magnetising and secondary currents change below, at and above series resonance?

Purpose: Connect switching intervals and secondary conduction directly to full-period waveforms, a job the one-edge P2 model cannot perform.

Model/evidence level: switched_model

Learner controls

  • frequency_case: select a validated case
  • plot_periods: choose one or two complete periods
  • bridge_state_overlay: show the categorical state and interval overlays

Observables

vSw [V], iRes [A], iMag [A], iSecReflected [A], currentDecompositionResidual [A], frequencyRegion [enum], secondaryConductionState [enum], secondaryCurrentMode [enum], secondaryCurrentZeroCrossing [event], secondaryZeroCurrentCommutationState [enum], commutationPolarity [enum], bridgeState [enum], deadTimeInterval [boolean], tankExcitationState [enum]

Expected result

  • series_resonance: waveform intervals and current polarity are repeatable on a complete period
  • region_comparison: secondary commutation and circulating-current differences are reported without claiming universal values
  • bridge_state_dead_time_alignment: Every high-to-low and low-to-high dead-time interval is explicitly bounded by its complementary bridge states and carries the concurrent tank-excitation state
  • current_decomposition: At every validated sample iRes equals iMag plus iSecReflected under the declared reference directions and currentDecompositionResidual stays within the P3 numerical tolerance
  • at_resonance_reference: The exact frozen 112539.53951963827 Hz case is classified at_series_resonance and provides the repeatable complete-period reference without claiming universal waveform magnitudes
  • below_resonance_region: A validated frequency below 112539.53951963827 Hz is classified below_series_resonance and its interval and current differences are reported against the at-resonance reference
  • above_resonance_region: A validated frequency above 112539.53951963827 Hz is classified above_series_resonance and its interval and current differences are reported against the at-resonance reference
  • dcm_ccm_state_agreement: secondaryCurrentMode is derived from secondaryConductionState and secondary-current zero intervals with exact state agreement over the complete period
  • secondary_zero_current_commutation: A zero-current commutation claim is aligned to an explicit secondaryCurrentZeroCrossing within the declared solver tolerance or remains unavailable and never becomes reverse-recovery proof

Limitations: GAP-01 is unresolved; Existing shared LLC plant uses a different 300 W tank and cannot be reused without revalidation; No handmade or hand-shaped waveform is allowed; A model waveform cannot prove hardware reverse recovery or safe probing; This test assesses only waveform literacy for les-01-03 and does not assess phasors resonance reflected impedance RMS loss or measurement safety

Prohibited inference: Do not call this switched-model or quantitative plot evidence unless P3 validates the full-period plant against the frozen tank; even after validation it cannot establish the les-01-03 prerequisite pass decision.

llc-t03-fha-operating-map

Build and read the FHA operating map

Question: How do normalized frequency, inductance ratio and effective quality factor move gain and input impedance angle?

Purpose: Build the normalized design map and expose the inductive or capacitive region cue without treating it as a ZVS proof.

Model/evidence level: fha

Learner controls

  • bridge_form: select the excitation form and apply its explicit Fourier factor
  • amplitude_convention: select the displayed fundamental convention without changing physical excitation
  • normalized_frequency: sweep fn
  • inductance_ratio: change Ln
  • effective_quality_factor: change Qe
  • load_fraction: change reflected load

Observables

bridgeForm [enum], amplitudeConvention [enum], bridgeFundamentalFactor [dimensionless], bridgeFundamentalPeak [V], bridgeFundamentalRms [V], Rac [ohm], Qe [dimensionless], fr [Hz], fp [Hz], frNormalized [dimensionless], fpNormalized [dimensionless], gain [dimensionless], inputImpedanceAngle [deg], regionCue [enum]

Expected result

  • bridge_fundamental: At 390 V half bridge produces 248.28171122335672 V peak and 175.56168165063568 V RMS while full bridge produces exactly twice both amplitudes
  • reflected_load_and_quality: With Ro 2.304 ohm and n 4, Rac = (8 / pi^2) * n^2 * Ro = 29.880832910329115 ohm, and Qe = sqrt(Lr / Cr) / Rac = 0.4732845187472114.
  • dual_resonance_placement: fr = 1 / (2 * pi * sqrt(Lr * Cr)) = 112539.53951963827 Hz at normalized position 1, while fp = 1 / (2 * pi * sqrt((Lr + Lm) * Cr)) = 42535.947747241175 Hz at normalized position 0.37796447300922714.
  • frozen_full_load: gain and angle arrays reproduce fha_gain_v1 and the declared impedance equation
  • region_boundary: zero angle marks only an FHA region boundary

Limitations: FHA replaces switched waveforms with fundamental equivalents; Most credible near series resonance; Cannot establish transient behavior switching ripple ZVS or hardware loss

Prohibited inference: Positive FHA angle is an inductive-region cue only; it does not prove that charge moves within dead time.

llc-t04-evidence-layer-comparison

Compare evidence layers without treating them as interchangeable

Question: Which claims can FHA, switched simulation, component models and imported measurements each support?

Purpose: Put aligned outputs beside their evidence badges and limitations so disagreement causes evidence escalation rather than a winner claim.

Model/evidence level: comparison_fixture

Learner controls

  • evidence_layers: show or hide available layers
  • imported_dataset: select only provenance-bound external data

Observables

alignedGainOrWaveform [declared_per_trace], difference [declared], evidenceLevel [enum], evidenceBadge [enum], sourceIdentity [sha256], modelIdentity [string], modelVersion [string], limitation [text], availabilityState [enum]

Expected result

  • no_measurement: measured layer stays visibly unavailable rather than synthesized
  • comparison: every trace carries source model version and limitation
  • per_layer_evidence_binding: Every declared layer emits evidence level badge source identity model identity model version limitation and availability state while an unavailable layer emits no result array

Limitations: No fixed comparison dataset is accepted; Difference magnitude is case-specific; Imported measurements do not validate unmeasured operating points

Prohibited inference: Do not promote the rejected fixed reference gains or a policy fixture as switched-model or measured truth.

llc-t05-zvs-charge-boundary

ZVS charge and dead-time boundary

Question: Is the signed commutation current sufficient to move the declared charge before turn-on?

Purpose: Separate the charge boundary from the FHA region cue and show nominal, marginal and wrong-polarity cases.

Model/evidence level: equation_screen

Learner controls

  • signed_commutation_current_A: select magnitude and polarity including the frozen P2 nominal and its wrong-polarity counterpart
  • dead_time_and_charge: inspect frozen P2 values

Observables

chargeAvailable [C], chargeMargin [C], polarityHelpful [boolean], zvsEligibilityState [enum], residualVdsAtTurnOn [V]

Expected result

  • magnitude_boundary: abs(iComm) times 250 ns equals 200 nC at 0.8 A
  • nominal_p2: minus 3.394104138973014 A produces 848.5260347432535 nC available charge 648.5260347432535 nC unsigned margin and helpful_sufficient classification
  • wrong_polarity: plus 3.394104138973014 A has the same unsigned charge values as nominal but is classified wrong_polarity

Limitations: Equation screen assumes constant current; Signed classification is defined for the declared high-to-low edge only; Qoss is a lumped total charge; Nonlinear capacitance parasitics and timing skew are excluded

Prohibited inference: Passing this screen does not prove device ZVS or hardware margin.

llc-t06-gain-envelope-and-operating-window

Required gain, bridge ratio and operating window

Question: Can the selected bridge and turns ratio meet line, load and overload requirements without leaving the declared frequency and inductive-region limits?

Purpose: Turn requirements into a gain envelope and test reserve, overload and frequency-window boundaries together.

Model/evidence level: fha

Learner controls

  • requirement_corner: execute one required corner from the complete declared set
  • input_voltage_case: expose the selected corner input-voltage dimension
  • output_voltage_case: expose the selected corner output-voltage dimension
  • load_case: expose the selected corner load dimension
  • hold_up_case: expose whether the selected corner is a hold-up condition
  • regulation_case: expose the selected corner regulation dimension
  • bridge_form: compare only with explicit gain-definition transform
  • turns_ratio: evaluate candidate ratio without changing P2 Chapter 1 default

Observables

requiredGain [dimensionless], attainablePeakGain [dimensionless], gainReserve [percent], solvedFrequency [Hz], impedanceAngle [deg], windowPass [boolean], bridgeForm [enum], turnsRatio [dimensionless], gainDefinitionTransform [string], bridgeRatioSelectionPass [boolean], requirementCornerId [enum], inputVoltageCase [enum], outputVoltageCase [enum], loadCase [enum], holdUpCase [enum], regulationCase [enum], cornerExecutionState [enum], requirementSourceIdentity [string]

Expected result

  • p2_full_load_points: solved frequencies are 92107.20028020618 Hz 117851.42223745432 Hz and 145091.65602378445 Hz
  • high_line_light_load: the old 135 kHz policy is not inherited and the P2 FHA finding near 167.081 kHz remains an open Module 5 and 8 reconciliation
  • requirement_corner_census: All seven declared input output load hold-up and regulation corners execute or report unavailable_missing_requirement without silent omission
  • per_corner_traceability: Every executed corner emits its five dimension values required gain execution state and nonempty requirement source identity
  • bridge_ratio_transform: Every gain result retains bridge form turns ratio and gain-definition transform and full-bridge excitation is exactly twice half-bridge excitation under the same amplitude convention before the selected pair is checked across every required corner

Limitations: FHA design screen only; Diode drop loss allowance and temperature must be reinstated beyond Chapter 1; Wider line and load trajectory is not frozen by P2

Prohibited inference: Do not reuse the rejected operating trajectory or silently treat the Chapter 1 supersessions as a settled Module 4 5 or 8 policy.

llc-t07-startup-and-region-trajectory

Startup, pre-bias and region trajectory

Question: Which regions and stresses does the converter cross while startup is sequenced from an unenergized or pre-biased output?

Purpose: Show time-ordered startup movement across operating regions without conflating it with steady-state protection policy.

Model/evidence level: switched_model

Learner controls

  • prebias_case: select initial output condition
  • soft_start_profile: change only a validated sequence parameter
  • startup_case_limits: bind output current and frequency limits to each initial condition before execution

Observables

initialConditionId [enum], switchingFrequency [Hz], switchingFrequencyLimit [Hz], switchingFrequencyPass [boolean], normalizedFrequency [dimensionless], inputImpedanceAngle [deg], regionState [enum], regionCrossing [event], resonantCurrent [A], resonantCurrentLimit [A], resonantCurrentPass [boolean], outputVoltage [V], outputVoltageLimit [V], outputVoltagePass [boolean], startupLimitSourceIdentity [string], startupCasePass [boolean]

Expected result

  • repeat: identical start state and payload produce identical ordered arrays
  • prebias: Both none and declared_prebias initial conditions emit exact ordered region-state and region-crossing arrays and retain output-voltage resonant-current and switching-frequency bounds with their source identity
  • startup_case_decision: startupCasePass is true for an initial condition only when every required output-voltage resonant-current and switching-frequency bound passes and a missing source-bound limit fails closed

Limitations: Startup capability is not established; FHA angle overlay is not switched truth; Device stress and protection thresholds require component data

Prohibited inference: This scenario cannot certify hardware startup safety or establish a controller policy before P3 implements and validates the required model.

llc-t08-tank-design-and-stress

Tank synthesis and first-pass stress check

Question: Which Lr Cr and Lm values realize the selected resonant frequency Ln and Qe, and what first-pass stress follows?

Purpose: Convert normalized choices into physical components and immediately challenge them with frequency gain and stress screens.

Model/evidence level: fha

Learner controls

  • resonant_frequency: choose design target
  • inductance_ratio: choose Ln
  • effective_quality_factor: choose Qe
  • component_rounding: compare solved and candidate parts

Observables

selectedFr [Hz], Ln [dimensionless], Qe [dimensionless], Lr [H], Cr [F], Lm [H], recomputedFr [Hz], inputImpedanceAngle [deg], gainReserve [percent], rmsStress [declared], peakStress [declared], componentRecomputePass [boolean], gainPass [boolean], inductiveAnglePass [boolean], stressPass [boolean], candidatePass [boolean], supportStatus [enum]

Expected result

  • frozen_default: default parts recompute 112539.53951963827 Hz and Ln 6
  • unsupported_stress: any stress not supported by the model is visibly unavailable
  • component_recomputation: Every candidate retains selected fr Ln and Qe with solved or entered Lr Cr and Lm and recomputes fr and Ln from those physical components before gain angle or stress is judged
  • coupled_candidate_decision: candidatePass is true only when component recomputation gain reserve inductive-angle and every supported RMS and peak stress gate pass together while an unsupported required gate fails closed

Limitations: First-pass FHA and equation stress only; No thermal magnetic saturation insulation or layout certification; Component rounding and tolerance require the separate iteration test

Prohibited inference: Do not present unsupported device or magnetic stress as switched-model or measured evidence.

llc-t09-tolerance-iteration-and-worst-case

Tolerance iteration and worst-case evidence matrix

Question: Which component temperature and controller corners move gain ZVS loss and frequency margins enough to require redesign?

Purpose: Propagate declared corners through all supported metrics and preserve unsupported cells as evidence gaps rather than false numbers.

Model/evidence level: comparison_fixture

Learner controls

  • tolerance_source_values: enter or select component limits
  • temperature_case: select temperature corner
  • candidate_design: compare one traceable iteration
  • required_corner_set: execute the complete declared corner table in stable order

Observables

cornerId [string], cornerOrder [ordinal], cornerSourceIdentity [string], cornerAssumptionIdentity [string], resonance [Hz], resonanceSupportState [enum], gainMargin [percent], gainMarginSupportState [enum], zvsMargin [declared], zvsMarginSupportState [enum], loss [W], lossSupportState [enum], controllerLimit [boolean], controllerLimitSupportState [enum], evidenceGap [enum], controllingConstraint [enum], iterationState [enum], reviewDecision [enum]

Expected result

  • p2_example_only: Lr plus or minus 10 percent and Cr plus or minus 5 percent are labeled an example unless source-backed for a selected component
  • unsupported_cell: missing model or source becomes an explicit gap
  • required_corner_census: Every source-bound corner appears exactly once in stable order with source and assumption identities for both before and after iteration states
  • per_corner_metric_support: Resonance gain ZVS loss and controller-limit cells each carry supported or unavailable state and an unavailable cell remains null
  • controlling_constraint: Each executable corner computes one controlling constraint from supported metrics without treating an unavailable cell as passing
  • iteration_decision: The after candidate is accepted only when all required corners pass their controlling constraints and both before and after records share the same corner identities

Limitations: Corner set depends on source-backed component data; Correlation and manufacturing distribution are not inferred; A completed matrix is not product qualification

Prohibited inference: The rejected resonance-only corner table cannot support current loss or ZVS conclusions, and no unsourced tolerance may be called a device specification.

llc-t10-magnetics-measurement-update

Update the tank from low-energy magnetic measurements

Question: How do measured leakage magnetising inductance and capacitance move resonance gain and the ZVS screen?

Purpose: Replace nominal magnetics with provenance-bound measurements and show exactly which predictions move.

Model/evidence level: measured_data

Learner controls

  • measurement_dataset: select or import a low-energy measurement set
  • fixture_type: select the measurement purpose
  • fixture_connection: declare the exact energized and terminated nodes
  • instrument_identity: enter instrument and calibration identity
  • measurement_frequency_Hz: enter the measurement frequency
  • excitation_amplitude: enter amplitude and unit
  • uncertainty_percent: enter bounded measurement uncertainty
  • leakage_allocation: declare where each provenance-bound leakage contribution enters the series model

Observables

fixtureMetadataComplete [boolean], measurementAdmissionState [enum], admissionFailureReasons [list], measuredLr [H], measuredLm [H], measuredCr [F], leakageAllocationId [enum], measuredLeakageContribution [H], externalLrContribution [H], totalModeledSeriesInductance [H], declaredSeriesInductanceTarget [H], allocationEqualityResidual [H], doubleCountDetected [boolean], allocationPass [boolean], leakageAllocationDecision [enum], fr [Hz], fp [Hz], gainShift [percent], circulatingCurrent [A], circulatingCurrentShift [A], zvsScreenShift [declared]

Expected result

  • accepted_gate1_example: 24 uH with 100 nF gives 102734.07401024998 Hz and the 100 uH Lm case gives fp 45196.96670398005 Hz
  • complete_fixture_metadata: Fixture type connection instrument identity frequency low-energy amplitude units and uncertainty produce admitted before values update the model
  • missing_provenance: Any missing fixture metadata produces rejected_missing_metadata and withholds the measured evidence badge
  • lm_gain_current_zvs_tradeoff: Every admitted Lm update reports gain shift circulating-current shift and ZVS-screen shift together without asserting a universal monotonic design benefit
  • leakage_allocation_equality: Every allocation identifies the measured-leakage and external-Lr contributions exactly once and totalModeledSeriesInductance equals their sum and the declared series-inductance target within the source-declared tolerance
  • leakage_double_count_rejection: Reusing one measured leakage value in both contribution branches sets doubleCountDetected and forces allocationPass false and leakageAllocationDecision rejected_double_count

Limitations: The browser does not perform a physical measurement; Mapping leakage into Lr depends on the declared measurement connection; Capacitance coupling fringing and nonlinear effects may require higher-fidelity models

Prohibited inference: Entered numbers without measurement provenance are comparison inputs, not measured evidence.

llc-t11-rectifier-paths-and-output-response

Secondary rectifier paths, capacitor current and load response

Question: How do rectifier topology and operating region shape secondary conduction output-capacitor current and diode stress?

Purpose: Prevent a primary-only view by tying secondary path states to output ripple and load response.

Model/evidence level: switched_model

Learner controls

  • rectifier_topology: compare only if both models pass P3 capability validation
  • load_case: select a source-declared steady or stepped load with explicit pre-step and post-step operating-point identity
  • operating_region: select a validated frequency-region case
  • diode_parameter_availability: select only a provenance-bound parameter layer
  • output_ripple_voltage_limit: enter the accepted peak-to-peak ripple limit
  • output_capacitor_rms_current_limit: enter the accepted capacitor RMS-current limit

Observables

rectifierTopology [enum], operatingRegion [enum], diodeParameterAvailability [enum], reverseRecoveryEvidenceState [enum], evidenceBadge [enum], loadCaseId [string], loadStepSourceIdentity [string], preStepOperatingPointId [string], postStepOperatingPointId [string], loadCommand [fraction], loadStepEventOrigin [s], secondaryCurrent [A], diodeCurrent [A], diodeVoltage [V], outputCapacitorCurrent [A], outputCapacitorRmsCurrent [A], outputCapacitorRmsCurrentLimit [A], outputVoltage [V], outputRipplePeakToPeak [V], outputRippleVoltageLimit [V], outputLimitPass [boolean], outputResponsePeakDeviation [V], outputResponseDeviationLimit [V], recoverySettlingTime [s], recoverySettlingTimeLimit [s], loadResponsePass [boolean], loadResponseDecision [enum], diodeLossScreen [W]

Expected result

  • topology: conduction paths follow the selected topology and polarity convention
  • region_and_parameter_layer: Every loss screen reports the selected operating region and uses only the selected provenance-bound diode parameters
  • reverse_recovery: no reverse-recovery claim appears unless a validated component model supports it
  • topology_identity: Every scenario trace and exported sample carries centre_tapped or bridge topology identity and comparisons reject an untagged or mismatched topology
  • output_capacitor_limits: outputLimitPass is true only if peak-to-peak output ripple and output-capacitor RMS current both meet their source-backed limits and a missing limit fails closed
  • load_step_response_decision: Every stepped case retains its source identity event origin and pre-step and post-step operating-point identities and loadResponseDecision accepts only when response-deviation settling-time ripple-voltage and capacitor-RMS-current limits all pass

Limitations: Bridge variant capability is unestablished; Ideal or lumped diodes cannot prove reverse recovery; Thermal and layout effects are excluded

Prohibited inference: Do not infer hardware reverse-recovery loss from ideal diode state changes.

llc-t12-synchronous-rectifier-timing

Synchronous-rectifier timing and device trade-off

Question: When do timing delay body-diode conduction reverse current and MOSFET capacitance erase the conduction benefit of synchronous rectification?

Purpose: Compare timing and device trade-offs on a validated secondary waveform rather than a fixed policy table.

Model/evidence level: component_model

Learner controls

  • sr_timing: sweep turn-on and turn-off delay
  • device_candidate: compare Rds on and capacitance data
  • rectifier_mode: compare from common state

Observables

deviceCandidateId [string], deviceSourceIdentity [string], deviceModelIdentity [string], deviceModelVersion [string], deviceTemperature [degC], rdsOn [ohm], capacitanceCharge [C], candidateOutputCapacitance [F], capacitanceReflectionModelIdentity [string], reflectedCapacitanceToTank [F], commonTankOperatingPointId [string], commonSecondaryWaveformId [string], secondaryCurrent [A], tankCurrentBaselineRms [A], tankCurrentCandidateRms [A], tankCurrentBurdenIncrease [A], tankCurrentBurdenLimit [A], tankBurdenPass [boolean], channelConductionTime [s], bodyDiodeTime [s], reverseCurrent [A], conductionLoss [W], bodyDiodeLoss [W], capacitanceLoss [W], timingRisk [enum], deviceTimingDecision [enum]

Expected result

  • timing_sweep: risk labels derive from visible current and gate intervals rather than a fixed threshold policy
  • running_example: no 8 A secondary-current property is asserted
  • device_resistance_capacitance_tradeoff: Every candidate retains source model version temperature Rds on and capacitance charge while conduction body-diode capacitance and reverse-current effects are evaluated from the same timing case
  • reflected_capacitance_tank_burden: Every candidate maps its source-backed output capacitance through the declared reflection model and compares baseline and candidate tank RMS current at the same tank operating point and secondary waveform before computing tankBurdenPass
  • device_timing_decision: deviceTimingDecision accepts a candidate only when supported conduction body-diode capacitance reverse-current and reflected tank-burden limits pass together and missing provenance reflection identity common-case evidence or a required metric returns unavailable

Limitations: Capability requires a validated secondary and SR model; Device capacitance may be voltage dependent; Gate-loop parasitics and thermal feedback require higher evidence

Prohibited inference: The rejected 8 A fixture and low watch high policy labels are not controller truth.

llc-t13-control-mode-trajectory

Frequency-control trajectory and control-mode concepts

Question: How does each supported control action move the operating point on the gain surface across line and load?

Purpose: Map control commands to operating-point movement while keeping conceptual mode comparison separate from unproven controller performance.

Model/evidence level: fha

Learner controls

  • line_and_load: choose operating requirement
  • control_concept: select only an implemented concept or view an explanatory disabled state
  • comparison_dimension: inspect the same dimension for every declared concept

Observables

sensedVariable [enum], commandedVariable [enum], limitingConstraint [enum], conceptComparisonState [enum], commandedFrequency [Hz], operatingPoint [coordinates], gain [dimensionless], impedanceAngle [deg], conceptAvailability [enum]

Expected result

  • p2_full_load: P2 full-load points appear unchanged
  • concept_dimensions: Every concept reports one sensed variable one commanded variable and one limiting constraint under the same line load requirement
  • unavailable_mode: unimplemented control concepts remain disabled and explanatory

Limitations: FHA trajectory does not establish dynamic stability; Current or charge and hybrid models may not be feasible in P3; Controller implementation is not bound to one IC

Prohibited inference: The rejected line and load frequency policy is not a validated controller trajectory.

llc-t14-load-dependent-loop-response

Load-dependent loop response and measurement workflow

Question: How does plant and loop response change across operating points, and which result is model-based versus imported measurement?

Purpose: Compare loop response at multiple operating points with explicit model or measurement provenance.

Model/evidence level: component_model

Learner controls

  • operating_point: select line and load
  • evidence_source: select source with visible badge

Observables

magnitude [dB], phase [deg], crossoverFrequency [Hz], bandwidth [Hz], phaseMargin [deg], sourceIdentity [sha256], evidenceBadge [enum], availabilityState [enum], operatingPointLoopPass [boolean]

Expected result

  • multi_point: each operating point has its own response and identity
  • no_measurement: no measured badge or trace is synthesized
  • per_operating_point_margin_decision: Every operating point emits crossover frequency bandwidth phase margin source identity evidence badge and availability state and operatingPointLoopPass fails closed when a required response or limit is unavailable

Limitations: Dynamic model and perturbation method are not yet established; Measured response requires external safe bench work; A single nominal response cannot establish whole-range stability

Prohibited inference: Model-based Bode response is not a measured loop response.

llc-t15-light-load-mode-transition

Light-load rectifier disable, burst and skip transition

Question: What happens to current output ripple frequency limit and mode state as load falls?

Purpose: Show the physical and control transition at light load, including output ripple and mode hysteresis, without claiming audible perception.

Model/evidence level: switched_model

Learner controls

  • load_fraction: ramp down or up
  • light_load_strategy: select only validated continuous SR-disabled burst or skip modes
  • mode_transition_limits: bind entry exit reverse-current and ripple limits before mode evaluation

Observables

switchingFrequency [Hz], burstState [enum], srEnable [boolean], outputRipple [V], outputRippleLimit [V], resonantCurrent [A], reverseCurrent [A], reverseCurrentLimit [A], reverseCurrentPass [boolean], eventRate [Hz], entryLoadThreshold [fraction], exitLoadThreshold [fraction], hysteresisState [enum], transitionPass [boolean], modeLimitSourceIdentity [string]

Expected result

  • frequency_limit: high-line light-load demand above 150 kHz is visible as a design conflict rather than silently clipped into the old policy
  • audible: only event rate is reported and human audibility is not asserted
  • sr_disabled_transition: The explicit sr_disabled case sets SR enable false and records the state transition separately from continuous-frequency burst and skip cases
  • mode_hysteresis: Every supported mode records source-bound entry and exit thresholds and exact hysteresis-state order on descending and ascending load ramps while a missing threshold fails closed
  • sr_reverse_current_decision: The SR-disabled decision retains resonant and reverse current output ripple and their source-bound limits and transitionPass requires reverseCurrentPass plus ripple and mode-state gates

Limitations: Mode policy requires P3 source and implementation; Model event rate cannot prove acoustic output or human audibility; Thermal and EMI consequences are outside this test

Prohibited inference: Do not claim a universal light-load threshold or audible result from the model.

llc-t16-transient-and-protection

Transient, current limit, overload, short circuit and restart

Question: Does the declared controller and protection sequence limit current and recover safely across a traceable set of disturbances?

Purpose: Exercise dynamic protection actions and restart state rather than replaying a declared policy table.

Model/evidence level: switched_model

Learner controls

  • disturbance: apply one accepted scenario
  • policy_parameters: inspect or change within validated bounds
  • case_acceptance_limits: bind output-voltage resonant-current and switching-frequency limits to every required disturbance

Observables

disturbanceId [enum], outputVoltage [V], outputVoltageLimit [V], outputVoltagePass [boolean], resonantCurrent [A], resonantCurrentLimit [A], resonantCurrentPass [boolean], switchingFrequency [Hz], switchingFrequencyLimit [Hz], switchingFrequencyPass [boolean], boundSourceIdentity [string], numericBoundsPass [boolean], caseAcceptanceDecision [enum], normalizedFrequency [dimensionless], regionCue [enum], regionCrossing [event], currentLimitState [enum], protectionState [enum], restartState [enum]

Expected result

  • deterministic_replay: each accepted disturbance replays exact ordered arrays and state transitions
  • fault_region_trajectory: Each load-step overload short-circuit and restart case reports normalized frequency region cue and any region crossing beside current-limit and protection state order
  • source_policy: no OCP burst or restart threshold is treated as technical truth without source and model validation
  • per_case_numeric_acceptance: Each load-step overload short-circuit and restart case retains source-bound output-voltage resonant-current and switching-frequency limits and caseAcceptanceDecision is accepted only when numeric bounds and ordered protection states pass together

Limitations: Controller and protection capability is unestablished; Simulated protection cannot certify hardware fault energy; Parasitics device SOA and thermal behavior require separate evidence

Prohibited inference: The rejected six-point frequency and protection table is not a controller design or proof.

llc-t17-loss-map

Loss map by mechanism and operating point

Question: Which primary tank magnetic secondary and output-capacitor losses dominate at each validated operating point?

Purpose: Separate loss mechanisms and expose missing component evidence instead of hiding it in one efficiency number.

Model/evidence level: component_model

Learner controls

  • operating_point: select line and load
  • component_candidate: select source-backed device magnetic capacitor and rectifier data
  • magnetics_loss_term: inspect one explicit magnetic loss mechanism without collapsing the other terms
  • secondary_loss_term: inspect secondary conduction or switching independently

Observables

lossTermId [enum], lossTermSourceIdentity [string], lossTermModelIdentity [string], lossTermModelVersion [string], lossTermTemperature [degC], lossTermEvidenceBadge [enum], lossTermAvailability [enum], lossTermCompatibilityState [enum], primaryConductionLoss [W], turnOffLoss [W], gateDriveLoss [W], residualHardSwitchLoss [W], primaryLossSubtotal [W], resonantCapacitorLoss [W], copperLoss [W], coreLoss [W], fringingLoss [W], proximityLoss [W], magneticsLossSubtotal [W], secondaryConductionLoss [W], secondarySwitchingLoss [W], secondaryLossSubtotal [W], outputCapacitorLoss [W], unsupportedLoss [None]

Expected result

  • supported_sum: total equals the sum of supported mechanisms and excludes explicit nulls
  • missing_component_data: affected loss remains unavailable
  • primary_loss_disaggregation: Primary subtotal equals the sum of available primary conduction turn-off gate-drive and residual hard-switching terms while an unsupported term remains null rather than zero
  • magnetics_loss_disaggregation: Magnetics subtotal equals the sum of available copper core fringing and proximity terms while an unsupported term remains null rather than zero
  • secondary_loss_disaggregation: Secondary subtotal equals separate available conduction and switching terms while output-capacitor loss remains outside that subtotal and unsupported terms remain null
  • per_term_evidence_identity: Every loss term at every operating point retains source identity model identity model version temperature evidence badge availability and compatibility state or remains unavailable without a numeric value
  • compatible_subtotals_only: Primary magnetics and secondary subtotals include only available terms whose source model version and temperature basis is compatible and reject an incompatible or unidentified required term

Limitations: Loss models depend on component data and temperature assumptions; No thermal solution or measured efficiency is established; Unsupported mechanisms cannot be replaced by zero

Prohibited inference: A partial modeled loss sum is not measured efficiency or production thermal proof.

llc-t18-architecture-evidence-register

Architecture evidence register and independent review

Question: Does the available evidence support LLC, redesign, comparison with another topology or a stop decision?

Purpose: Make the learner defend a decision from requirement and evidence records without an automatic weighted winner.

Model/evidence level: comparison_fixture

Learner controls

  • criterion: execute every required criterion for each declared candidate
  • architecture_candidate: add or select a traceable architecture candidate
  • criticality: mark whether the criterion can gate the decision
  • evidence_records: attach evidence and limitations
  • decision: record a justified outcome

Observables

criterionId [enum], architectureCandidateId [string], criticality [enum], criterionStatus [enum], evidenceRecordIds [list], evidenceLevel [enum], sourceIdentity [string], limitation [text], criticalGateState [enum], conclusionId [string], conclusionTraceabilityState [enum], openUncertainty [text], decision [enum], decisionRationale [text]

Expected result

  • open_evidence: unresolved high-risk evidence can produce a stop or comparison decision
  • automatic_winner: no weighted score or architecture winner is computed
  • required_criterion_census: Every declared architecture candidate has exactly one record for each of the nine required criteria and no required criterion can be omitted or replaced by an unlisted weighted score
  • critical_requirement_gate: Any critical contradicted or high-risk open criterion prevents support_llc and produces redesign compare_another_topology or stop_pending_evidence without averaging
  • conclusion_traceability: Every conclusion links to one or more accepted catalog test IDs or an explicit lesson no-test rationale and retains source identity limitation and criterion status or the review is rejected

Limitations: This is a decision fixture not a multi-topology physics comparison; Cost density bidirectionality and paralleling inputs require external evidence; Saved rationale does not certify a product

Prohibited inference: The rejected 14 17 24 27 rank and CLLC winner are not technical truth and must never be displayed as such.

Exact accepted arrays

Quantitative plot catalog

llc-p01-ch1-commutation-overlay Hard-switching trace is counterfactual

Compare the hard-switching counterfactual with nominal ZVS on the frozen Chapter 1 edge.

Evidence level: switched_model

Expected reading: Wrong-sign current leaves 390 V at turn-on; nominal negative current reaches the zero clamp at 58.925711111872716 ns.

Compare the hard-switching counterfactual with nominal ZVS on the frozen Chapter 1 edge.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: ffa496b7dd2cf4bbd5d31442543931ae67be1856f798155728a4c901a01122d5

Limitations: Static one-edge comparison; Constant current; Lumped charge; Not a full-period waveform; Not measured evidence

llc-p02-prerequisite-full-period

Assess only reference direction, polarity and complete-period waveform reading after the separate five-part prerequisite diagnostic.

Evidence level: switched_model

Expected reading: Learner can identify current polarity primary-secondary interval correspondence and each dead-time interval between complementary bridge states with the concurrent tank-excitation state without treating this plot as evidence of phasor resonance reflected-impedance RMS-loss or safe-measurement readiness.

Assess only reference direction, polarity and complete-period waveform reading after the separate five-part prerequisite diagnostic.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: f77f9ed2fda08ead7e6c833e54b874384892eae80faf222060dea2ea245d00b8

Limitations: Blocked by GAP-01; Existing shared 300 W plant cannot be inherited; No handmade waveform; Not hardware reverse-recovery evidence

llc-p03-three-frequency-current-paths

Compare resonant, magnetising and reflected-secondary current paths below, at and above series resonance.

Evidence level: switched_model

Expected reading: Current decomposition resonance-region classification DCM or CCM state and any zero-current secondary commutation remain explicit for each validated complete-period case under GAP-01.

Compare resonant, magnetising and reflected-secondary current paths below, at and above series resonance.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: 9def562b8bafa31d68fb279c5e89cd1403cf42cca9adc0fa658e184ea1f91153

Limitations: Blocked by GAP-01; Existing shared 300 W plant cannot be inherited; No handmade waveform; Not hardware reverse-recovery evidence

llc-p04-fha-gain-angle-map

Verify bridge-form fundamental amplitude and then read normalized gain and FHA input-impedance angle on the same frequency grid.

Evidence level: fha

Expected reading: Half-bridge and full-bridge fundamentals use the explicit factor-of-two transform while Rac Qe and exact fr and fp placements remain visible beside gain and region cues.

Verify bridge-form fundamental amplitude and then read normalized gain and FHA input-impedance angle on the same frequency grid.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: 728288cdd9672eb26d7e1d6d05a44389310d419ffd3adb98f5d228373c094a16

Limitations: FHA only; Most credible near series resonance; Cannot prove switching commutation transient behavior or hardware loss

llc-p05-evidence-layer-comparison

Compare available evidence layers with explicit source badges and missing layers left absent.

Evidence level: comparison_fixture

Expected reading: Disagreement triggers evidence escalation every layer retains source model version badge limitation and availability and no trace gains authority from visual proximity.

Compare available evidence layers with explicit source badges and missing layers left absent.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: 2a32f22559f48cf0e6457fa3e58b9bdaf3a8d1cc399246ebb3b3f1b86e87a5c9

Limitations: No accepted fixed reference dataset; Difference is case-specific; Bench data cannot validate unmeasured points

llc-p06-zvs-charge-margin

Compare the frozen P2 nominal current, magnitude boundary and equal-magnitude wrong-polarity cases with an explicit eligibility classification.

Evidence level: equation_screen

Expected reading: Minus 3.394104138973014 A is helpful_sufficient, minus 0.8 A is helpful_marginal, and equal positive magnitudes are visibly wrong_polarity despite identical unsigned margin.

Compare the frozen P2 nominal current, magnitude boundary and equal-magnitude wrong-polarity cases with an explicit eligibility classification.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: caa7ba4af8963efe3eb9cc3664682e2b8eb427f5946ef68bba69fbd876cd6fe4

Limitations: Algebraic constant-current screen; Lumped Qoss; Not device or hardware proof

llc-p07-gain-envelope-window

Compare required gain, attainable FHA gain, angle and accepted frequency limits.

Evidence level: fha

Expected reading: Full-load P2 points are reproducible bridge form turns ratio and transform stay bound to every result all seven requirement corners execute or remain visibly unavailable and the 167.081 kHz conflict remains explicit.

Compare required gain, attainable FHA gain, angle and accepted frequency limits.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: c935c28676410789afd3c59ade6b1fb5dd724735a961899ade8f53babc277509

Limitations: FHA design screen; P2 Chapter 1 does not settle the wider Module 4 5 and 8 trajectory

llc-p08-startup-region-trajectory

Show the time-ordered startup path for no-prebias and declared-prebias cases.

Evidence level: switched_model

Expected reading: Both no-prebias and declared-prebias cases retain ordered region states and crossings with visible output current and frequency limits and a fail-closed per-case decision.

Show the time-ordered startup path for no-prebias and declared-prebias cases.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: 690f763e04808e4726cafe8ee72beb10a019b1a20b3109ff0cb9642492a394c1

Limitations: Plant and soft-start policy are P3 requirements; Not hardware startup proof

llc-p09-tank-design-stress

Connect candidate tank variables to gain reserve and component stress screens.

Evidence level: fha

Expected reading: A valid first-pass design preserves fr Ln Qe and physical components and passes recomputation gain inductive-angle and supported stress gates together; one formula output is not a design decision.

Connect candidate tank variables to gain reserve and component stress screens.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: d6f7c861883598b3c086068764929d527c99c693ab1c96c6ef3ba66c84f7af53

Limitations: First-pass analytical and FHA screens; Component temperature and construction require later evidence

llc-p10-tolerance-margin-envelope

Expose which declared corner drives gain, frequency, charge margin and stress.

Evidence level: fha

Expected reading: Every source-bound corner preserves metric support states and computes its controlling constraint before a shared-identity before or after candidate decision is accepted or rejected.

Expose which declared corner drives gain, frequency, charge margin and stress.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: 28d34066ee1fa3c4fd5270f5b2f9d3b776f29e7ee51219b13cb1bd3f484740e8

Limitations: Coverage only matches the declared corner set; Monte Carlo claims require an explicit distribution and seed

llc-p11-magnetics-model-update

Show how provenance-bound measured Lm and leakage update predicted frequencies and ZVS screens.

Evidence level: comparison_fixture

Expected reading: Only an admitted source-backed allocation that maps each leakage contribution once and makes total modeled series inductance equal the declared target can update resonance gain current and ZVS screens; double counting is visibly rejected.

Show how provenance-bound measured Lm and leakage update predicted frequencies and ZVS screens.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: 01f115fd7e85fc888578c1ceff8a642585d0de6e938a543cbc6deaa264734c46

Limitations: P2 freezes no measured magnetics; Imported values are unavailable until provenance is supplied; Detailed magnetic design is out of scope

llc-p12-rectifier-output-response

Relate rectifier conduction intervals to output-capacitor charging and loss screens.

Evidence level: switched_model

Expected reading: Rectifier topology and source-declared load-step identity stay bound to pre-step and post-step operating points and event origin; output response settling ripple and capacitor-current limits jointly gate a fail-closed load-response decision.

Relate rectifier conduction intervals to output-capacitor charging and loss screens.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: ac32a6e8ec154ac51a39b5f3d97d0648e63bf5acc53562f2df443a532900f218

Limitations: Requires validated secondary and output plant; Device reverse recovery needs component or hardware evidence

llc-p13-sr-timing-device-currents

Expose body-diode, channel-conduction and reverse-current intervals as SR timing moves.

Evidence level: switched_model

Expected reading: Device identity Rds on and capacitance stay bound to one common timing and tank case; reflected capacitance and baseline-versus-candidate tank-current burden remain visible so low resistance cannot hide tank body-diode capacitance or reverse-current rejection.

Expose body-diode, channel-conduction and reverse-current intervals as SR timing moves.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: 8af93e7e95a65031ba65c7f5f89486072f7224ef786cee35601fa2aee486e459

Limitations: Timing screen depends on the declared secondary model; Driver propagation and PCB effects require component or bench evidence

llc-p14-control-operating-trajectory

Map frequency, line and load movement onto the gain surface for each declared control concept.

Evidence level: fha

Expected reading: Each concept exposes what it senses commands and limits before its trajectory is compared; the P2 high-line light-load 167.081 kHz finding still prevents inheritance of a 135 kHz endpoint.

Map frequency, line and load movement onto the gain surface for each declared control concept.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: 468ffd214177dd1a13511cfc0ac4c3f3b7dfb342e7738cce6869916dd73d404b

Limitations: FHA trajectory; Wider operating policy is unresolved; Not loop-stability evidence

llc-p15-load-dependent-loop-response

Compare load-dependent loop response with model and measurement evidence kept distinct.

Evidence level: comparison_fixture

Expected reading: Crossover bandwidth and phase margin move with operating point while source badge and availability keep model and measured decisions distinct and absent bench data remains absent.

Compare load-dependent loop response with model and measurement evidence kept distinct.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: 84b1b1b55cc5a78da335fa1415bb5cda1a7e9455b0aeb2283b6cb3e6bfd1ff57

Limitations: No measured loop data is frozen; Measurement fixture and injection limits are P3 or later obligations

llc-p16-light-load-mode-transition

Compare continuous-frequency, SR-disabled and burst or skip transitions at light load.

Evidence level: switched_model

Expected reading: Each supported mode preserves entry and exit thresholds and hysteresis order while SR-disabled acceptance is tied to reverse-current and ripple bounds without claiming audible or EMI compliance.

Compare continuous-frequency, SR-disabled and burst or skip transitions at light load.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: f71662595d9ef55775b93cdc023a60f72fae058df0ac6958a69d0b56cd9d75e5

Limitations: Audible and EMI behavior require physical evidence; Controller-specific policies are not frozen

llc-p17-transient-protection

Show transient, current-limit, overload, short-circuit and restart event order with assertions.

Evidence level: switched_model

Expected reading: Every disturbance reports source-bound voltage current and frequency comparisons beside exact region protection and restart order and fails closed when a required bound is unavailable.

Show transient, current-limit, overload, short-circuit and restart event order with assertions.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: f619963214cb262d26f4e82a969037b65cbcea4fe7857fb03bec3bd7ec2ab0a5

Limitations: Controller and thermal behavior are abstracted; Simulation cannot establish safe hardware fault energy

llc-p18-loss-map

Attribute primary, tank, magnetics, secondary and auxiliary losses by declared operating point.

Evidence level: comparison_fixture

Expected reading: Every separated loss term retains its source model version temperature badge availability and compatibility tuple and subtotals accept only compatible available terms.

Attribute primary, tank, magnetics, secondary and auxiliary losses by declared operating point.
Complete delivery overviewOpen full-size plot

Rendered SHA-256: 2795a51619f39d335d1425006a9a93d77f82fc8ce9c3f04488a58b7617356a5b

Limitations: No complete measured loss map is frozen; Temperature and parasitics require provenance-bound models or hardware