url-insightlisted

# url-insight — URL batches → portfolio insights → DoR issues **Fires on**: multi-URL paste · "analyze these urls" · "should we adopt X" · "competitive signal" · "worth a spike" · arxiv/HN/ProductHunt/GitHub URLs in bulk. **Purpose**: compress a firehose of URLs into ranked, evidence-backed actions against the 21-active-repo portfolio. Noise → IGNORE. Signal → specialist agent panel → Linear ticket with devil + steelman reckoning. Design: Fukasawa (paste URL → pipeline fires) · Rams #10 (8 labels, not 30) · Honest (IGNORE is first-class) · Calibrated (devil + steelman together). --- ## 0 · MANDATORY protocol (non-negotiable, like hebb/linear) 1. **Before fetching any URL**: run the dedup pre-check in §0.1. If hebb or Linear finds a prior verdict, **skip fetch**, **skip nab**, and report `Already triaged: <MIK-id>, verdict=<ADOPT|IGNORE|INSPIRE|SUPERCHARGE|HUMAN-REVIEW>, ROI=<n>x` with the issue link. 2. **After each URL is classified + scored**: write the hebb dedup pin in §0.1 with `project="url-insight"` and key schema `url-<sha256-of-canonical-url>-<iso-date>`. 3. **Before filing any issue**: run devil's advocate (§6) AND steelman (§6.5). Quote both verbatim in issue body. 4. **For SUPERCHARGE**: dispatch innovator agent FIRST (serial gate). If kill → drop signal. If proceed → parallel fan-out: moonshot-architect + business-panel + research patent-prior-art. 5. **For FAIL-FAST SPIKE**: surface user prompt "file issue / also spawn <1h spike agent?" (unless `--auto-spik