403/403 baseline
The final beta.6 feature baseline passed the deterministic test suites before release metadata publication.
Machine-readable evidence
Scenario IDs point to exact source and test methods.
Version: the scenario document is synchronized to
0.1.0-beta.6 and remains deterministic-software evidence only.Foundational scenarios
Measurement, protection, voltage, direction, and trust.
| Scenario | Claim | Expected result |
|---|---|---|
| SIG-001 | Balanced fundamental RMS and positive sequence | RMS and positive sequence match synthetic nominal-frequency inputs. |
| P50-001 | Normal-load security | Balanced normal load restrains with no phase/earth pickup or virtual trip. |
| P50-002 | 50P definite-time operation | Phase overcurrent picks up, completes the configured delay, and latches virtual trip. |
| TRUST-001 | Trust-before-trip | Pickup remains visible while a trip-blocked trust state prevents a new virtual trip. |
| V27-001 | 27 undervoltage operation | 27 operates after its configured delay from the intended phase-voltage quantity. |
| V59-001 | 59 overvoltage operation | 59 operates after its configured delay from the intended phase-voltage quantity. |
| V59N-001 | 59N residual overvoltage | 59N operates from the modeled 3V0 quantity after configured timing. |
| DIR-001 | 67P forward operation | Forward directional quantity operates with adequate V1 polarization. |
| DIR-002 | 67P reverse restraint | Reverse directional condition restrains. |
| DIR-003 | 67N independent residual provenance | Explicit residual-current/voltage channels are preferred and the intended direction operates. |
Beta.6 metrology scenarios
Closed-loop timing has dedicated regression evidence.
| Scenario | Regression | What it protects |
|---|---|---|
| MET-001 | CmcStyleProfileUsesMicrosecondClockAndTenKilohertzBinarySampling | 1 µs clock, 10 kHz BI, 100 µs sample period, and deglitch/debounce profile contract. |
| MET-002 | CausalRelayFrontEndStartsFromSettledPreFaultHistoryAndRespondsWithoutOneCycleBlackout | No empty-window startup artifact; causal instantaneous-sample relay front end. |
| MET-003 | DesktopDefaultA_B_GRunHasNoUnexplainedTripTimingGap | Desktop-style full setting group, generic pickup separation, operated-element timing, and external BI1 path. |
| MET-004 | MetrologyTimelineOrdersPhysicalClosedLoopEvents | Chronological T0/pickup/trip-request/BI/stop event causality and self-consistent event-derived timing. |
| MET-005 | OpenTripWireStillPreventsMeasuredTripInMetrologyMode | Relay internal trip cannot bypass an open BO1→BI1 external path. |
Release-level evidence
Publication adds more than unit-test pass/fail.
Build and security gates
.NET CI, release build/test/audit, CodeQL, and Windows/macOS/Ubuntu protection-core checks passed.
Package provenance
Installer/portable validation, no-admin/single-file checks, release asset verification, SHA-256, CycloneDX SBOM, and build-provenance attestations completed.
Not yet validation of hardware equivalence
Software regression evidence has a defined ceiling.
The current scenario set can demonstrate deterministic behavior of the referenced ARVREL code and fixtures. It cannot establish traceable test-set calibration, manufacturer-specific relay timing, IEC 60255 type-test compliance, IEC 61850 conformance, protection-grade hard-real-time execution, commissioning acceptance, or operational suitability.
Reproducibility rule
Do not publish a scenario without an exact executable reference.
Public deterministic scenarios should point to a source file, test file, exact test method, declared input, expected result, and bounded evidence class. New research claims require new fixtures and tests before documentation is expanded.