State: modelled. The confirmations are covered by Electron tests on Linux; the module's actions are not yet reported to Neural Inverse Govern.
What you confirm
| Action | What happens first |
|---|---|
| An edit to an SCL file from a command or editor | Applied to the editor's text as one Undo step and not saved: you review and save |
| Add IED from ICD/IID, Upgrade SCL Edition | A preview of every change; nothing changes until you confirm |
| Writing a file (CID, records, reports, test set files, signal lists, COMTRADE exports) | A save dialog; replacing an existing file asks first |
| Import SCD into PCM600 Project | A confirmation naming the IED count and that no PCM600 command takes an import back |
| A write to an IED | A modal confirmation naming the IED, the attribute and the value. Only report control block attributes (RptEna, ResvTms, EntryID, GI, IntgPd, PurgeBuf) are written |
| Reconnect with reports enabled | One confirmation listing the writes |
| Deleting files on an IED | Offered only with neuralInverse.energy.records.allowDelete on; each delete asks, naming the IED and the files |
| Any agent change or connection | See Agent tools: confirmed at every call, whatever auto-approval says |
The module does not load configurations to an IED, operate a control, change a mode, test mode or simulation, or write a setting group to a relay. Those stay with the relay vendor's tool or the station HMI (see What's next).
Credentials
IED credentials are kept only in the Editor's secret storage, never in settings or the workspace, and no agent tool can read them. See MMS over TLS and credentials.
The Energy log
The Energy output channel (View > Output, then pick Energy) records:
- the schema editions loaded;
- the changes of Update IED from IID, Add IED from ICD/IID and edition upgrades, with line numbers;
- vendor tool command lines and their output;
- online associations (with the TLS details and the IED's certificate fingerprint), browses with their requests and time, confirmed writes and disconnections;
- live capture command lines.
Its file is logs/<window>/neuralInverse.energy.log. It is the local log of the Editor window, for the engineer and for troubleshooting. It is not a tamper-evident audit trail.
Support for your issue process
Before a file leaves for site, the module gives you:
- a semantic compare against the previous version;
- a recorded revision in the SCL file's own Header and History, with who, what and why (confRev and the change record);
- a settings report with the SHA-256 of the file's bytes;
- the CID cut byte for byte from the SCD.
These are inputs to your review. Approval to issue, and the record of who issued what to site, stay with your organisation's process. Who may hold which IED credential, role policies, and the audit and evidence of credential use belong to Neural Inverse Govern.