Skip to content
AAA.win

workflow

Build a source-checked research brief

A repeatable research workflow that separates discovery, claim verification, synthesis, and editorial approval.

Stored on this device only. Account and cross-device sync are not available.

Editorially reviewedVerified 2026-08-112 official or primary sources

Inputs

  • A bounded research question
  • Source requirements and date range
  • A claim-and-citation template
  • A named reviewer

Control points

  • Prefer primary sources
  • Open every cited page
  • Mark uncertainty and conflicts
  • Do not auto-publish

Human approval gate

A named editor approves every material claim, citation, uncertainty note, and refresh date before publication.

The workflow

Every step includes a check that can stop the process before risk moves downstream.

  1. 01

    Define the decision

    Write the question, audience, cutoff date, and claims that would change the decision.

    Gate: A reviewer can tell what is out of scope.
  2. 02

    Discover candidate sources

    Use more than one search path and collect primary documentation before commentary.

    Gate: Every source has a publisher, URL, and access date.
  3. 03

    Verify claims

    For each material sentence, confirm that the cited source says what the sentence claims.

    Gate: Citation presence and citation entailment are reviewed separately.
  4. 04

    Synthesize with uncertainty

    Separate facts, provider claims, editorial inference, and unresolved questions.

    Gate: Uncertainty is visible instead of smoothed away.
  5. 05

    Approve and schedule recheck

    A named person approves the brief and records when volatile claims should be revisited.

    Gate: The published page has a reviewer and verified date.

Candidates to pilot

Inclusion means relevant product shape, not measured superiority.

Sources checked

Open the original pages before relying on a time-sensitive product decision.

  1. What is Perplexity?Perplexity
  2. Google Search guidance on generative AI contentGoogle Search Central
Version · v4.3.4-indexnow-root-proof

Latest releases

IndexNow root-proof request compatibility

After v4.3.3, the exact root-level {key}.txt proof returned HTTP 200, but a full request carrying keyLocation still returned HTTP 403; a minimal homepage request with the same production key and no keyLocation returned HTTP 202. This release omits that field, while the automatic full run and idempotent rerun remain deployment checks.

IndexNow key-proof compatibility

Changed IndexNow verification to the official root-level {key}.txt convention after the first production notification returned HTTP 403; revalidation remains pending, while the website, sitemaps, and Bing sitemap processing are unaffected.

Bing sitemap discovery and IndexNow change notifications

Prepared canonical sitemap discovery for Bing and added automatic IndexNow change notifications while keeping segmented sitemaps authoritative and making no claim that a notified URL has been crawled or indexed.

View all releases