Controlled inputs
The suite fixes fixture generation, iteration counts, variant code, warm-up procedure, round count and reporting calculations. It records the runtime environment every time the site is rebuilt.
That makes results reproducible enough to audit and rerun, but not universal. ASAMB does not claim to hold CPU frequency, thermal state, neighboring virtual machines or kernel scheduling constant.
A useful local baseline
The goal is a transparent local baseline that helps form a production hypothesis. A high-stakes change should then be tested with representative traffic, concurrency, storage and application code.
Publishing limitations is part of the result. It prevents a controlled script from being mistaken for a complete capacity plan.