>> the whole path
mq-ums already had a working API. It could accept a known command, pass it to PowerShell, and return a result from IGEL UMS. The difficult part was not making that call work. It was making the rest of the repository mean the same thing.
A command catalogue, a browser, an audit log, a cache, and a validation script can all be individually correct and still describe different systems. One filters arguments. Another records a name. A third bypasses the server and calls the runner directly. Every part works. The path does not exist.
The repair was to give the path one shape. The allowlist decides what may run. One service owns execution. The response and audit record share a request identity. Cached reads pass through the same history. The browser displays what the server returns instead of inventing a parallel model. Documentation is checked against the catalogue rather than trusted beside it.
This is less a feature than a change in topology. Before, the repository contained several useful rooms. After, there is a corridor through them: intent, policy, execution, result, evidence. Each transition is visible. Each failure has somewhere honest to stop.
The last stop matters most. Local tests can prove the contracts, the API, the redaction rules, and the audit chain. They cannot prove PSIGEL, a DPAPI credential, or a live UMS server that is not there. When the validation ran on the wrong machine, the local layers passed and the live commands failed. That was not a broken test. It was the boundary becoming visible.
Operational software is complete only when the whole path can be followed in the environment that consumes it. Until then, green means the structure holds. It does not mean the distant machine answered.