non-consensus-researchlisted

# Non-Consensus Research Pipeline A reusable, topic-agnostic skill that turns Claude (or Codex) into a self-running market-research apparatus. It hunts findings that are technically true *and* still absent from mainstream analyst consensus, with brutal verification to throw away anything that isn't. ## When to invoke The user wants to: - Build a continuously-updated research repository on any technical or market domain. - Combine findings across sectors / sub-domains to surface emergent insights no single-sector report contains. - Apply an independent "is this really not priced in?" verification pass to every claim. - Generate a clean public site that updates automatically and reads well on mobile. If the user just wants a one-shot research report, **do not invoke this skill** — use a single research agent instead. This skill is for the *ongoing* version that runs on a schedule. --- ## What you'll set up The pipeline has three durable layers and one disposable layer per cycle. ### Durable 1. **A spec file** (`orchestration/PIPELINE.md` template provided) that defines the topic domain, the N sectors, keyword seeds, source tiers, and validation criteria. 2. **A `CLAUDE.md` (or `AGENTS.md`) file** in the working repo that encodes the recurring cycle protocol. 3. **A scheduled remote agent** (cron `0 */N * * *`, default 5h) that re-executes the full pipeline. 4. **A static HTML viewer** (`index.html`) that fetches the generated markdown at runtime and renders it. No build