Verification state: modelled. The tools are tested through the Editor's tools service with real text models and the real edit service on Linux; they have not been used by a language model in the running Editor. On the real export the largest result (the largest sequence) is about 190,000 characters, with expressions over 2,000 characters cut.
The tools
The tools exist only while the DCS environment runs. Each is tagged read-only or state-changing.
| Tool | Effect | What it does |
|---|---|---|
neuralInverse_dcs_listExports | read-only | Lists the workspace's exports |
neuralInverse_dcs_summary | read-only | Summarises an export |
neuralInverse_dcs_findModules | read-only | Finds modules |
neuralInverse_dcs_module | read-only | Reads a module with its parameters and the paths that name it |
neuralInverse_dcs_alarms | read-only | Lists alarms |
neuralInverse_dcs_checks | read-only | The module's checks of an export |
neuralInverse_dcs_sequences, neuralInverse_dcs_sequence | read-only | Lists sequences; reads one |
neuralInverse_dcs_impact | read-only | The impact of a library change |
neuralInverse_dcs_setAlarm | changes an export | An alarm's priority, enabled or suppression timeout |
neuralInverse_dcs_setParameter | changes an export | An instance's overridden parameter |
- They read the export as the editor holds it, unsaved changes included.
- A path must name a
.fhxinside the workspace. - Results are marked as data read from the export, not instructions, and are capped (lists at 500 items, strings at 2,000 characters, the whole result at 200,000).
- A change is made through the same edit service as the tables: one change, one Undo, logged, never saved by the tool.
No tool imports into DeltaV, runs the DeltaV export, downloads to a controller or writes to a running plant.
Every change is approved by a person
Every change an agent makes asks the engineer every time: its own Apply Change and Cancel buttons in the chat, and a dialog when the chat approved the call without asking (auto approval, Autopilot, a stored approval or a hook). No edit lands without a person's click, and no tool asks for pre-approval. The confirmation shows names and values as plain text.
The log
Every edit, the save guard's decisions and every DeltaV export run are logged to Output > DCS, the Editor window's output channel. The module keeps no other audit record and does not apply the organisation's governance policy to its actions. See Neural Inverse Govern.