China AI Hub
Authors & Research Team
Last updated: 2026-09-29
Who writes this site
China AI Hub is researched, written and maintained by the SinoAI Hub Research
Team — a team-level byline, not a set of named individuals. Pages are credited to
the team collectively (author: SinoAI Hub Research Team in each page's
metadata) because the work is collaborative: data collection, source verification, writing
and correction are distributed across a small group rather than attributable to a single
person.
We do not publish invented individual author profiles. The site deliberately avoids the common pattern of fabricating a named "expert" persona with a biography. Where any future page carries an individual byline, that person's real name and credentials will be shown on the page itself; none currently exist.
Why team attribution instead of named authors
Named author pages are only trustworthy when the name maps to a real, checkable person. We would rather understate than misstate: a team byline is honest, and it keeps the reader's focus on the evidence rather than on a persona. The accountability mechanism on this site is the source layer — every factual claim carries a source, a source type and a verification date — not an author's reputation.
How the team works
- Collection — data is gathered from official sources first (vendor documentation, model cards, pricing pages, papers, GitHub), following the tier hierarchy in the methodology.
- Verification — values are re-checked against primary sources and date-stamped; records carry a
verifiedorpartially_verifiedstatus. - Writing — editorial analysis is separated from observed data and labeled (editorial standards).
- Correction — errors are handled through a public process with a record (corrections policy).
Independence
The team operates without advertising, sponsored listings, or affiliate links, as described in the funding disclosure. No Chinese AI vendor pays for placement, ranking, or description.
Contact
To reach the team about content, data or corrections: Martin.W — [email protected]. For a factual error, see the corrections policy for the fastest route.