Skip to content
AAA.win

workflow

Build a literature evidence map

Create a traceable map of research questions, inclusion decisions, study claims, limitations, and conflicting evidence.

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

Editorially reviewedVerified 2026-08-113 official or primary sources

Inputs

  • A bounded research question
  • Databases and date range
  • Inclusion and exclusion rules
  • An evidence extraction schema

Control points

  • Retain search queries
  • Separate discovery from inclusion
  • Record exclusions and inaccessible sources
  • Do not collapse conflicting findings

Human approval gate

A domain-qualified reviewer approves the search boundary, inclusion decisions, extracted claims, and limitations before the map informs a decision.

The workflow

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

  1. 01

    Write the review boundary

    Define population, intervention or topic, outcome, source classes, dates, and languages.

    Gate: A reviewer can reproduce what belongs in scope.
  2. 02

    Search through declared paths

    Run documented queries across the selected discovery tools and retain result identifiers.

    Gate: The query, date, tool, and result count are recorded.
  3. 03

    Screen consistently

    Apply the inclusion rules and preserve a reason for every exclusion after full review.

    Gate: Ambiguous records are routed to a second person.
  4. 04

    Extract claims and limits

    Capture study context, material findings, evidence location, limitations, and conflicts.

    Gate: Every table row points back to the source.
  5. 05

    Approve the evidence map

    A domain reviewer checks coverage, interpretation, uncertainty, and the decision summary.

    Gate: The published map names its cutoff date and unresolved gaps.

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. Learn about Gemini NotebookGoogle
  2. Elicit searchElicit
  3. Consensus research guideConsensus
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