Evidence states are not interchangeable
Every material technical claim should be understood at one of four levels. A source-present capability is not automatically configured; configured is not automatically enabled; enabled is not automatically functionally verified.
- Source present: the relevant implementation or dispatch path exists in the inspected revision.
- Configured: the required settings or generated artifacts are present.
- Enabled: the runtime is loading or exposing the capability.
- Functionally verified: a bounded acceptance test produced the expected result.
Publication checklist
- State the tested revision, date, environment, assumptions and explicit non-goals.
- Use sanitized fixtures; never publish credentials, caller data, recording URLs or runtime identifiers.
- Show failure modes, stop conditions, rollback and an independent verification step.
- Timestamp prices, regulations and vendor capabilities and prefer primary sources.
- Label lab demonstrations honestly; synthetic setup does not prove production capacity.
Corrections and commercial coverage
Material corrections should update the visible review date and explain the changed conclusion when context requires it. Commercial relationships, supplied access and affiliate links must be disclosed on the affected page. Advertising does not determine technical conclusions or rankings.
Use the contact page to report a reproducible error. Include the public URL, the disputed claim and non-sensitive evidence.