Research — Auto Demo · Precomputed (draft, unvalidated)

One fault, three categories: auto

No controls here: seven short stories play on their own. A voltage dip to 0.65 pu is held longer and longer, and each Category in turn becomes permitted to disconnect while the others are still required to ride through; then a shallow dip, a deep one, a frequency excursion, rate of change, phase jump, unbalance, and the cease-to-energize, return-to-service and restore-output checks that follow an event. Use Pause, or the story and step buttons, to stop on any frame.

Story

One disturbance, three Categories · each DER is either required to ride through or permitted to disconnect

required to ride throughpermitted to disconnectno zone breachedWaveform and DER symbol: illustrative, not a harness outputDraft, unvalidated harnessCategory ICategory IICategory IIIdarker shading = more Categories required to ride through

What the harness floors say at this event · permission, not a prediction

Check being read · click a unit or card on the drawing, or a row below

Actual

Required

Margin

How the harness read it · its own words, verbatim

    Every check at this step · the highlighted row is the one this step changed

    There is deliberately no overall verdict.

    Notes on every result · shown even when nothing is close to a floor

    Every check · before, after, and after the fix

    Event cards are coloured by outcome (required to ride through, permitted to disconnect, no zone breached), never as pass or fail. Post-event cards carry the function's own pass, fail, incomplete or not-applicable verdict; incomplete is never a pass.

    Precomputed results:every verdict, required value and margin on this page was computed by the real Python harness at export time and is played back from a data file. The page runs no harness logic and holds no standards tables, and it never interpolates between exported values. Not a live API call. Precomputed from the Python harness: ugm-agent-harness (recorded commit a1507b2), a draft with no subject-matter-expert sign-off. Nothing here is a compliance determination. Each function compares a DER's demonstrated capability to a floor or ceiling; none maps a grid event to a disconnection. The export asks each one "if a DER disconnected at this point, would that be compliant?": fail means the floor requires riding through, pass means a disconnection is permitted (permission, not a prediction). Which zone an event falls in and the timeline marker (the zone's required seconds) are the demo's own reading of the harness table, tagged demo logic. The waveform and DER symbol are illustrative, not a harness output. Post-event measured values are illustrative scenario inputs; the harness override tables are empty and any override shown is synthetic ("demo override (illustrative)"). Only the voltage and ROCOF floors differ by Category. The Category III voltage ride-through times were corrected after sources disagreed and are the harness's highest-priority item awaiting human review; the IEEE 1547-2018 subclause numbers are single-source.Real functions this maps to:check_der_voltage_ride_through_zone, check_der_frequency_ride_through_zone, check_der_rocof_ride_through, check_der_voltage_phase_jump_ride_through, check_der_voltage_unbalance_ride_through, check_der_cease_to_energize_time, check_der_return_to_service_delay, check_der_restore_output_timing.Not modeled: a DER model or any prediction that a real inverter disconnects (the floors give permission, not behaviour), grid dynamics, protection and anti-islanding detection, overvoltage events, a utility override of any floor (the override tables are empty), and any real device or site. Waveforms and symbols are illustrative.See also:One fault, three categories, interactive with free play · Fast-track screens walk, auto · Ride-through zones, auto