THE EVIDENCE LAB
Evidence before enthusiasm.
A useful software explanation separates what was observed, what a provider documents, what is inferred, and what remains unknown.
THE EDITORIAL CHAIN
A claim has to survive five steps
- 01
Claim
Name the practical question without starting from a product pitch.
- 02
Official source
Check provider documentation for facts that can change.
- 03
Controlled test
When access and scope allow it, run one observable workflow.
- 04
Limitation
Keep the scenario, conditions, and unresolved facts beside the result.
- 05
Reader decision
Give the reader enough context to choose a safe next step.
READ THE LABEL
What the labels on a guide mean
Pages may use a short label and a fuller evidence alias. Both point to the same reader question: what can this page actually support?
- TESTEDTESTED_TRUE
- Observed in Oravenda’s controlled workflow. It supports that scenario, not every possible setup.
- OFFICIALDOCUMENTATION_VERIFIED
- Supported by an official source when checked. Product facts and policies can change.
- UNKNOWN / NOT TESTEDNOT_ESTABLISHED
- Not tested or not supported strongly enough to claim. This is a boundary, not a gap to hide.
WHEN A GUIDE USES MANGA
A story can explain the decision. It cannot prove the result.
Editorial artwork uses fictional scenarios to make a workflow problem easier to recognize. The test record and official sources remain the evidence for any factual claim.
READER CHECK
Before you act on a guide
- Does the tested scenario resemble my job?
- Which statements come from the provider, and which come from a controlled test?
- What limitation could change my decision?
- Can I test the smallest version before relying on it?