Editorial standards
What you can hold this publication to, stated plainly enough to hold us to it.
Last updated
Sourcing
Every factual claim is traceable to a source a reader can reach. Sources are listed at the foot of each piece, with the publisher and the date accessed where the source can change.
- First-party data means data ROLearn collected itself. It is named as such, and the collection method is described in the methodology.
- Platform data means figures published by Roblox, Epic, Valve, or another platform. We report what the platform reports and note where its definition differs from ours.
- Third-party estimates are labelled as estimates, attributed to whoever made them, and never silently merged into our own figures.
- Anonymous sources are used only when the information is material and cannot be obtained on the record. The reason for anonymity is stated in the piece.
Verification
A number is not published until it has been reproduced from the underlying data at least once, independently of the query that produced it first. Where a figure comes from a single API call that cannot be reproduced later, the piece says so and treats the number as a point-in-time observation rather than a measurement.
Charts are generated from the same dataset the text describes. If a chart and a sentence disagree, the chart is wrong and it gets fixed, because the chart is what people screenshot.
Labelling
Every piece declares its kind in the byline: research, analysis, data brief, case study, report, opinion, news, or interview. The distinction is enforced, not decorative. Anything published as research, a data brief, a case study, or a report must carry the full apparatus (question, source, sample, period, method, definitions, limitations) or it cannot be published under that label at all.
Opinion is labelled as opinion. Facts inside an opinion piece are sourced to the same standard; the conclusion is the author's.
Conflicts of interest
This publication is owned by ROLearn, which sells software to some of the companies it writes about. That conflict is managed by disclosure, not by pretending it does not exist:
- Any piece that uses ROLearn's collection pipeline as a data source names it in the apparatus block.
- Any piece about a company that is a ROLearn customer, prospect, or partner discloses that relationship in the piece.
- No customer, advertiser, or sponsor reviews a piece before publication, and no finding is softened, delayed, or dropped because it is commercially inconvenient.
- Paid placements are labelled Paid content above the headline and never appear in the research, data brief, case study, or report sections.
Corrections
Errors are corrected in public and the log is permanent. The original claim is not deleted or quietly rewritten; a dated entry is appended explaining what was wrong and what changed. See the corrections policy.
Use of AI
Where and how machine assistance is used is set out in full in the AI use policy. The short version: no piece is generated by a model, and a human is accountable for every number.
What we will not publish
- A ranking whose formula we will not show.
- A projection without the assumptions that produce it.
- Scraped personal data, or any figure that identifies an individual player.
- A vendor's claim about their own performance presented as a finding.
- An estimate stated with more precision than the method can support.
Right of reply
If a piece makes a critical claim about a named company, that company is contacted before publication where practical and its response is included. If a response arrives after publication, it is added to the piece and noted in the correction log.
Concerns about anything published here: intelligence@rolearn.dev.