Static assessment
Inspect an artifact, version, configuration or dependency without claiming that the software has been executed.
Software, firmware & configuration
Test the change.
Understand the limits.
Yerokom’s validation model connects a proposed change to its prerequisites, dependencies, test environment, approval and independent after-state verification.
Choose the right test
Different questions require different evidence.
Simulation or emulation
Use a supported model or runtime to explore behavior. Record what the model does—and does not—represent.
Virtual or physical lab
Use a supported hypervisor, vendor lab or real equipment when actual execution or hardware behavior is required.
Artifact compatibility
A customer-provided image is a starting point—not a promise of execution.
The proposed evaluation should identify the exact vendor, product, version, architecture, image format and license. It must also identify the supported runtime, required peripherals and dependencies, and how close the test environment is to the target environment.
Uploading arbitrary software, firmware or an operating system does not establish that it can be safely or legally executed. A simulated result is not represented as a hardware-certified result.
Do not email proprietary images or credentials. Agree the secure transfer route and test scope before providing artifacts.
A governed sequence
Baseline → test → authorize → verify.
- 01
Baseline
Record the target, versions, dependencies and expected behavior.
- 02
Test
Select the supported method and capture both results and limitations.
- 03
Authorize
Bind approval to the intended targets, artifact, action and time window.
- 04
Verify & recover
Independently inspect the result and follow the agreed recovery path if it fails.
Talk to Yerokom
Bring a change you need to understand.
Describe the equipment, version and operational question. We will confirm the applicable release, test method and evidence requirements before requesting an artifact.