Method · Transparency · Corrections
How Research turns evidence into decisions.
Every report is designed to be useful before it is exhaustive: a bounded question, a clear answer, traceable support, visible uncertainty, and a practical next step.
- Editorial goal
- Decision clarity
- Evidence standard
- Direct sources first
- Public identity
- Research
What readers can expect
The report should let a skeptical reader see what is known, how it was interpreted, and what remains uncertain.
The brief view carries the decision, decisive evidence, main caveat, and next action without requiring a long read.
Decision-changing claims point to direct sources. Platform and vendor claims are labeled when they are self-reported.
Revenue is not presented as profit, correlation is not presented as cause, and unavailable evidence remains an explicit unknown.
From question to publication
A shared workflow keeps the evidence notebook, both languages, and the public page aligned.
- Bound the decision. Define the reader, geography, terms, time cutoff, and exclusions.
- Collect evidence. Prefer primary and official sources; record dates, scope, caveats, and confidence.
- Challenge the answer. Separate observation from inference and actively look for failures, delays, and contradictory cases.
- Publish in two languages. English and Simplified Chinese preserve the same numbers, causal strength, caveats, and sources.
- Validate before release. Check metadata, links, structure, JavaScript, keyboard use, small screens, no-script reading, and the exact Pages artifact.
AI assistance and public identity
Tools may accelerate the work; they do not replace the evidence trail.
AI-assisted tools may support discovery, comparison, translation, drafting, and interface production. Published factual claims are checked against the research notebook and linked evidence. Interpretations remain labeled as interpretations.
Reports use the organization-level byline Research. Personal names, local machine paths, private account identifiers, credentials, and internal operational files are excluded from the public site. The repository may retain development resources, but the Pages artifact is built from an explicit reader-facing allowlist.
Corrections are part of the record
Evidence changes. Platform rules move. A useful report should make revision possible.
To report a broken source, factual error, translation mismatch, or material omission, open a public correction issue. Include the page, claim, and supporting source. Substantive corrections update the report date and both language editions.
Reuse with clear credit
The reports are made to be shared, checked, and built upon.
Unless a page says otherwise, original report text and original visuals use CC BY 4.0. Credit “Research by Onovich,” link to the source page, and note changes. Code, skills, scripts, and templates use the repository’s MIT License. Third-party quotations, trademarks, logos, screenshots, and source data keep their original rights.