README.md

ArIED 61850 Documentation

This directory contains the engineering, validation, licensing, provenance, and operating-boundary documents for the ArIED 61850 Windows application.

Start here

Document	Purpose
Project README	Product overview, feature summary, quick start, build instructions, and public claim boundary.
Architecture	Multi-IED ownership, model identity, report-first acquisition, runtime scaling, and timestamp semantics.
GOOSE Subscriber	Read-only Npcap capture, ARIEC61850 GOOSE decoding, SCL/live-discovery DataSet binding, ordered allData leaf semantics, diagnostics, and field validation.
Validation checklist	Discovery, reporting, monitoring, recovery, and control acceptance checks.
UI validation	Windows scaling, keyboard workflow, accessibility, multi-IED, and command-panel checks.
Engine compatibility	Required ARIEC61850 source contracts and project-reference layout.

Control engineering

Document	Purpose
ARIEC61850 Smart Control integration	Application-to-engine control service integration.
Smart Control feedback audit	Control completion, feedback mapping, and evidence boundaries.
Close feedback event verification	Event-driven feedback confirmation workflow.

Application workflow and progress records

Document	Purpose
Phase progress	Detailed signal-selection behavior and validation record.
Connection diagnostic audit	Example route and connection-failure reasoning.
Changelog	Public application, documentation, website, and release history.

Licensing and provenance

Document	Purpose
Licensing model	GPL community edition, historical boundary, and separate commercial licensing path.
License and provenance audit	Repository-evidence review and remaining manual checks.
Clean-room and interoperability policy	Independent-development, test-fixture, UI, and external-material boundaries.
External IP and provenance review	Repository evidence concerning external implementation and proprietary-asset contamination.

Project policies

• Contributing
• Community conduct
• Security
• Support
• License
• Commercial licensing
• Trademark and branding

Documentation principles

Public documentation should:

• distinguish configured SCL context from the live MMS model;
• distinguish protocol readiness from switching authority and operational safety;
• state whether evidence comes from unit tests, loopback, simulator, laboratory IEDs, or field use;
• avoid universal interoperability or conformance claims;
• use synthetic or contributor-owned examples;
• exclude confidential customer, employer, station, credential, and project material.