Add standards-backed Sampled Values research gate

[masarray]

Purpose

Create a formal research gate before ARSVIN expands from its current 9-2LE-style workflow into broader IEC 61850 and IEC 61869-9 profile claims.

Added

• Authoritative source hierarchy for standards, tissues, UCAIug guidance, vendor documentation, real-device captures, and lab evidence.
• Current public IEC 61850 catalogue baseline and explicit licensed-standard gaps.
• Separate StationScout and DANEO 400 benchmark roles.
• Product claim levels from research candidate through supported and certified.
• Conformance/interoperability matrix for generic Layer-2 SV, 9-2LE-style workflows, IEC 61869-9, timing, scaling, high-rate operation, and redundancy.
• Fast-track implementation gates with exit criteria.
• Safe SCL/PCAP evidence-intake and anonymization guide.
• Documentation index and changelog updates.

Safety and claim boundaries

This PR adds no protocol constants and no new compliance claim. It explicitly prevents remembered or article-derived profile values from being promoted into production without licensed clause review and deterministic evidence.

Public sources reviewed

• IEC 61850 series public catalogue.
• OMICRON StationScout product page and brochure.
• OMICRON DANEO 400 product page and brochure.
• OMICRON IEC 61850 thematic introduction.

Full clause-level IEC and IEC 61869-9 verification remains a licensed-source task and is recorded as such.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a68bade4a8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Align the evidence package file lists

When a contributor creates a real-device evidence case from this README, this template asks for expected-profile.json but omits the expected-frame.json and expected-detection.json files that the new research gate declares mandatory in docs/sv-research-gate.md. That makes the newly added intake guide produce packages that fail the gate’s own required-file contract before future tooling or reviewers can rely on the layout.

Useful? React with 👍 / 👎.