System Utilities & Cross-cutting · Trust & Integrity
M33 · Audit & SHA-256
Proves that the software you received is exactly the one that was released.
Base (always active) Implemented
Proves that the software you received is exactly the one that was released.
Benefits: You can check the integrity of your installation at any time.
Example of use: Run dcos.exe verifica-release with the public key received separately and read VALIDO.
Key capabilities
- Release signature verification
- SHA-256 register of all files
- Detection of altered, missing or extra files
Audit & SHA-256, base module (always active, not licensable). Signed register of sources and builds (dcos/release_signing.py): SHA-256 register of every file, Ed25519-signed manifest, verification by verify_release.py or dcos.exe verifica-release. Release pipeline prepared (dcos/release_pipeline.py: blocking regression, test report from real JUnit results, re-signing, local commit), to be executed in the M35 phase. No ModuleContract: it acts through command-line tools.
Prerequisites
None: always active.
Declared limits
A signature proves origin only if the public key is checked out of band.
Owner's note
The code of every module is fully present and the modules have been verified. Any status shown as “not verified” or “partially implemented” derives solely from test gaps in the laboratory environment (for example the physical absence of a device during the test campaign), not from software limitations. Declared simulations (decision D-24) are deliberate design choices.
Interconnections
The interconnections shown are documented functional relationships (code reuse and data flows) or derive from the architectural role; they are an editorial reconstruction.
Official texts: D-COS NEXUS V130 MASTERWORK Official Documentation and official V130 presentation (November 2026).
This module is part of the integrated ecosystem
D-COS NEXUS does not sell separate modules: every capability lives inside the ecosystem. Contact us to see how it applies to your context.