Scrape To Gated Claims

Use when Apify/scrape rows must become trusted memory. Runs structured scrape then evidence/scope/conflict gates before commit.

cassidyrice Updated

File contents

Scrape → Gated Claims

Source × gate: Actor datasets never enter trusted store raw.

When to Use

  • Apify/SERP/docs crawl produced rows you might remember
  • Need atomic claims with source URLs for fact_store / brain

Not for: dumping HTML into notes; interactive browse-only tasks.

Process

  1. Run apify-actor with capped maxResults / maxPages.
  2. Normalize rows → candidate claims (one fact each) + source URL.
  3. For each candidate, run verified-brain-commit-ritual gates.
  4. Commit passes; keep fails in inbox with gate reasons.
  5. Return ledger: committed ids vs inbox holds.

NEVER

  • Commit without URL
  • Bundle five facts into one write
  • Store API tokens from pages

Collision parents

apify-actor, verified-brain-commit-ritual

cassidyrice/ai-skills-drop/tree/main/skills/scrape-to-gated-claims commit 68cef29378

Frequently asked questions

npx skillmds@latest add cassidyrice/scrape-to-gated-claims