ThinkTech

Methodology and Source Standards

ThinkTech aims to be a reliable reference for AI governance decisions. This page describes how we research, verify, and present information.

Source classification

Every factual claim on ThinkTech is tagged with a source type badge. This helps readers assess the reliability of the information quickly.

Primary Source

Primary Source

Government regulation text, court filings, official technical specifications, published datasets. The original document, not a summary of it.

Vendor Claim

Vendor Claim

Company press releases, product documentation, whitepapers, marketing materials. Information produced by the entity being discussed. Presented as-is, not endorsed.

Independent Review

Independent Review

Peer-reviewed academic papers, nonprofit audit reports, investigative journalism from established outlets. Third-party analysis not funded by the subject.

Legal Source

Legal Source

Legislation text, regulatory guidance documents, court opinions, administrative rulings. Legal documents that establish binding requirements or precedent.

Source hierarchy

When multiple sources conflict, we follow this priority order:

  1. Primary legal text (legislation, court opinions)
  2. Official technical specifications and standards
  3. Peer-reviewed academic research
  4. Independent audits and investigative reporting
  5. Vendor documentation (noted as vendor claims)
  6. Industry reports and analyst commentary

We never cite an industry report as fact when a primary source is available. If we can only find vendor claims for a given topic, we label it clearly.

Review process

  1. Research: Identify the reader question. Find primary sources first, then supporting evidence.
  2. Draft: Write with source badges on every factual claim. Include decision tables or checklists.
  3. Verify: Check every source URL is live and correctly attributed. Confirm facts against primary sources.
  4. Review: Check for unsupported claims, missing context, and clarity. Ensure the reader question is answered.
  5. Publish: Include last-updated date. Set review reminder for content that may become outdated.

Update policy

Content is reviewed on a regular schedule based on type:

Content TypeReview Frequency
Policy tracker entriesMonthly
Risk library entriesQuarterly
Guides and toolsEvery six months
Benchmark analysisWhen new benchmark versions release

When content is updated, the “last updated” date changes and a note is added describing what changed.

Corrections

If you find an error in any ThinkTech resource, contact us at contact@thinktech.ngo. We will investigate within seven days and publish a correction with a note explaining what changed and why.