Repository navigation
Conversation
…tic physical evidence
masarray
merged commit Oct 11, 2026
280f294
into
fix/512-goose-event-header-alignment
19 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
P10.3 / P10.4 — GE Edition 1 field evidence, fail-closed (DRAFT)
Base exact validated P10.2 ARSAS
2369c286da6d14dda2470a2854daf2d46d588dfeon staging PR #512. Exact engine lock00ad2819b99ffe6b3f885e59aa24a6afb2b4d8e1unchanged. No runtime MMS/GOOSE/report/control changes.P10.3
Staging
2369c286...already passed 16/16 post fast-forward CI on Actions run family #381057..., including Build ARSAS #38105708427 portable EXE/installer. Reuse this verified existing candidate; no duplicate builds or return to old main.P10.4 delivered as field-proof tooling — not fabricated live acceptance
scripts/verify-p10-ge-field-scl.py: offline, bounded, DTD-rejecting SHA-pinned comparison of independently trustedBCU_GE.iidwith ARSAS Discovery-export SCL. ExactBCUGE/F650/ raw domainBCUGEF650, AP/IP, 8 DataSets and 124 ordered FCDA membership identities, source vs export LN/RCB/GOOSE inspection.r10PromotionAllowedtrue.scripts/test-verify-p10-ge-field-scl.py: 16 synthetic positive and negative fixture tests (changed trusted SHA, endpoint, wire domain, LDevice inst, FCDA ordering, missing source node, ambiguous AP, malicious DTD, source/live LN delta, RCB semantic review). Runs once in existing canonical Build ARSAS Python test phase; zero new artifact uploads.docs/P10_GE_ED1_FIELD_ACCEPTANCE.md: operator workflow, separately recorded SHA256 trusted IID at intake, Save → Open SCL and field evidence requirements.Explicit blocker: physical relay is not accessible from this GitHub-only session
No fresh on-device MMS association to
192.16.1.33:102and no actual originalBCU_GE.iidbytes were provided in the current conversation/project. Physical validation remains PENDING. Avoid contaminating permanently accepted R10 historical evidence with synthetic counts. Do not merge to main or release.Acceptance gates before merging this PR to staging
Canonical Windows build + offline fixture regression green; no report/control/discovery runtime code drift. After tool is ready, operator attaches real trusted source, exported SCL, both ingress diagnostics, and PCAP/RCB continuity evidence. If any fail, fix root cause in a separate target PR, never silently weaken checks.