---

name: analyze description: "Perform a full 3-stage analysis following the Reality Check methodology. Use for manual analysis without automatic database registration."

Manual 3-Stage Analysis (Codex)

Perform a full 3-stage analysis following the Reality Check methodology. Use for manual analysis without automatic database registration.

Invocation

Copy$analyze <url>

Note: Codex reserves /... for built-in commands. Use $analyze instead.

Perform a full 3-stage analysis following the Reality Check methodology. Use this for manual analysis when you want to review claims before registering them.

Prerequisites

Environment

Set REALITYCHECK_DATA to point to your data repository:

Copyexport REALITYCHECK_DATA=/path/to/realitycheck-data/data/realitycheck.lance

The PROJECT_ROOT is derived from this path - all analysis files go there.

Red Flags: Wrong Repository

IMPORTANT: Always write to the DATA repository, never to the framework repository.

If you see these directories, you're in the framework repo (wrong place for data):

• scripts/
• tests/
• integrations/
• methodology/

Stop and verify REALITYCHECK_DATA is set correctly.

Data Source of Truth

LanceDB is the source of truth, not YAML files.

• Query sources: rc-db source get <id> or rc-db source list
• Query claims: rc-db claim get <id> or rc-db claim list
• Search: rc-db search "query"

Ignore YAML files like claims/registry.yaml or reference/sources.yaml - these are exports/legacy format.

Fetching Content

To retrieve and parse source content:

• Primary: WebFetch for most URLs
• Alternative: curl -L -sS "URL" | rc-html-extract - --format json
• rc-html-extract returns structured {title, published, text, headings, word_count}

Methodology

Stage 1: Descriptive Analysis

• Summarize the source neutrally
• Extract key claims, predictions, and assumptions
• Identify theoretical lineage (what traditions/thinkers it builds on)
• Map argument structure (chain arguments, logical flow)
• Note scope and domain (what does this attempt to explain?)
• Define key terms with operational proxies

Stage 2: Evaluative Analysis

• Assess internal coherence and logical consistency
• Evaluate evidence quality using Evidence Hierarchy (E1-E6)
• Verify key factual claims (especially crux claims)
• Search for disconfirming evidence (5 min minimum)
• Check for internal tensions/self-contradictions
• Note persuasion techniques and rhetorical devices
• Identify unstated assumptions and dependencies
• Flag unfalsifiable claims

Stage 3: Dialectical Analysis

• Steelman the strongest version of the argument
• Identify strongest counterarguments and counterfactuals
• Consider base rates and historical analogs
• Map relationships to other theories (supporting/contradicting)
• Synthesize: where does this fit in the broader landscape?

---

Evidence Hierarchy

Use this hierarchy to rate strength of evidential support for claims.

Claim Types

---

Output

Generate:

1. Analysis document following the 3-stage methodology
2. Extracted claims formatted for database registration

After analysis, register manually:

Copyrc-db source add --id "..." --title "..." --type "..." --author "..." --year YYYY --url "..."
rc-db claim add --id "..." --text "..." --type "[F]" --domain "..." --evidence-level "E2" --credence 0.XX --source-ids "..."

Or use $check for fully automated analysis + registration.

---

Related Skills

• $check
• $extract