researchlisted

# Research Everything a plan rests on that is not in this repository — a standard, a data release, a library's behaviour, a known vulnerability — lives outside it and **moves**. Your training data has a cutoff and the world does not, so anything you "know" about a version number is a hypothesis with a date on it. ## Before you search, look **Somebody may already have answered this, for another project.** Digests are filed per project, so the same question gets paid for twice by default: ```bash python3 "${CLAUDE_PLUGIN_ROOT}/scripts/research_index.py" query <terms> ``` **A hit is a lead, not an answer.** The index holds the topic, the question, the date, the sensitivity and the path — deliberately no findings, because an index carrying the answer becomes a second home for a fact (P-34), goes stale silently, and gets read in preference to the digest precisely because it is more convenient. | The hit is | Do | |---|---| | fresh, and answers the question | cite it — `per <path>, as of <date>` — and say in your digest that you reused it rather than re-derived it | | fresh, and answers a *neighbouring* question | read it for its sources, then do your own work. A digest about TOML's current version does not answer one about YAML's | | stale | **re-verify at the primary source.** A stale hit is worth having — it says where to look and what the answer used to be — and is worth nothing as a citation | | absent | ordinary research, and your digest becomes the next person's hit |