← registerm/FIND-001.html
On file
Find contested areas worth mapping
Ran 2026-08-09. Twelve sourced candidates; Tier 1 — D-Wave, minimum wage, AlphaChip, CMIP6. Quotes are search-index-confirmed only; a rerun on night-shift-map upgrades them to page-read.
What it found
12candidates
On hand

Nothing.

Environmentnot recorded

This is the environment file as it stands today, not a record of this run. The run predates environment capture, so what it actually had on hand was never recorded and cannot be recovered.

Name
night-shift-map
Network access
Custom
Allowed domains
arxiv.org www.nature.com www.science.org pmc.ncbi.nlm.nih.gov journals.aps.org www.nber.org openreview.net cacm.acm.org blog.google research.google deepmind.google
Setup script
no setup script
Environment variables
no variables
Brief81 lines
# Run 0 — find the areas worth mapping

Paste this whole thing. Nothing to fill in.

---

## What this run is for

I want to spend future nights mapping open questions in a technical field. I
don't know which field yet, and I don't want to pick from memory or from a
list someone generated without checking. Your job is to go find the
candidates and show me the evidence.

## What makes an area a good candidate

Look for areas where **claims are loud and independent verification is thin**.
Concretely, any of these:

- **A live dispute.** Two credible parties publicly disagree about whether a
  result holds, and it hasn't been settled. Failed replications, published
  rebuttals, comment-and-response exchanges, editorial notes.
- **A loud claim nobody independently checked.** A widely cited result whose
  data or code isn't available, or where every follow-up comes from the
  original group.
- **Nobody's job.** The question falls between fields, or everyone qualified
  to settle it has a commercial or reputational stake.

An area is a *bad* candidate if it's simply hard and everyone agrees it's
hard. Difficulty isn't the signal. Contested-ness is.

## What to produce

Around ten candidate areas. Fewer is fine if that's what's real.

For each one:

- **The area**, in a sentence a non-specialist understands.
- **What's contested** — the specific claim in dispute, not the general topic.
  "Whether method X actually beats baseline Y" beats "AI in chip design."
- **Who's on each side**, and what their stake is if they have one.
- **The evidence this is live**: at least two sources, with titles, authors,
  years, and links. At least one should be a document where someone states
  the disagreement directly — a rebuttal, a failed replication, a comment
  paper, an editorial note. Quote or closely paraphrase the sentence that
  shows it, and say where in the document it appears.
- **How long it's been unresolved.**
- **Whether a careful outsider could actually map it** — is the evidence
  public, or is the key data proprietary and the whole thing unmappable from
  outside? Say which.
- **Your confidence** that this is genuinely unresolved rather than settled
  somewhere you didn't look: high, medium, low.

## Where to look

Cast wide. Include at least one candidate from each of: semiconductors and
hardware, AI/ML internals, quantum, and somewhere none of those — biology,
climate, materials, economics, medicine. Do not restrict yourself to fields I
might be expected to care about; a good candidate in an unexpected field is
more valuable than a mediocre one in a familiar field.

Useful places for this kind of thing: PubPeer, Retraction Watch, arXiv comment
threads and v2+ revisions, journal comment-and-reply sections, replication
studies, reproducibility workshops, editorial expressions of concern.

## Rules

- Every claim about a dispute needs a source. If you can't find someone
  publicly saying it, it doesn't go in the list.
- Don't include a controversy that's already been resolved — check whether the
  argument continued after the last exchange you found.
- Don't pad. Six real candidates beat ten with four invented.
- Rank them at the end: which would make the best first mapping run, and why.
  Say plainly if you think some are not worth doing.

## Output

Write `output.md` in this run's folder.

Then a section called **Notes on this run**: what you searched, what you
couldn't reach, what you're unsure about, and anything that surprised you.
Blunt. This part is for me, not for a reader.