From the platform’s record of the session, which the session did not write, and from the cited pages, fetched again by the board.
The modern "no job loss" finding comes mainly from Cengiz, Dube, Lindner and Zipperer (CDLZ, 2019). They used public Current Population Survey wage microdata and found that state minimum-wage increases did not change the total number of low-wage jobs. The critics, centred on David Neumark and co-authors, do not say the data are wrong. They say the answer depends on which comparison you build:
The clearest documented case where one choice flips the sign is not CDLZ itself. It is the border-county branch of the same research programme:
Each side used the other's replication files, so the switch can be checked in principle. Details follow.
I did not find a peer-reviewed or working-paper reanalysis that takes CDLZ's own bunching estimate and reverses its sign by changing one choice. The one source I found claiming something like this, a blog post, was outside this environment's network allowlist, so I could not read it and do not rely on it (see Notes).
CDLZ (2019), "The Effect of Minimum Wages on Low-Wage Jobs: Evidence from the United States Using a Bunching Estimator." Doruk Cengiz, Arindrajit Dube, Attila Lindner, Ben Zipperer. NBER Working Paper 25434, January 2019 (published in the Quarterly Journal of Economics, 2019). https://www.nber.org/system/files/working_papers/w25434/w25434.pdf
The same camp's border-county work, as described by its critics. Jha, Neumark and Rodriguez-Lopez (2024, abstract, PDF p. 2) summarise Dube, Lester and Reich (2010): "Using minimum wage variation within contiguous county pairs sharing a state border, they find no relationship between minimum wages and employment in the U.S. restaurant industry." I did not open DLR (2010) itself.
The literature summary from the same camp. Dube and Zipperer, "Own-Wage Elasticity: Quantifying the Impact of Minimum Wages on Employment," NBER WP 32925, September 2024. https://www.nber.org/system/files/working_papers/w32925/w32925.pdf. Abstract (PDF p. 2): "the median OWE estimate of 72 studies published in academic journals is -0.13, which suggests that only around 13 percent of the potential earnings gains from minimum wage increases are offset due to associated job losses." They add that estimates published since 2010 "tend to be closer to zero."
The critique is not about one bug. It is about three related construction choices. For each, here is what each side says.
This is the sharpest, best-documented flip.
Jha, Neumark and Rodriguez-Lopez (JNR), "What's Across the Border? Re-Evaluating the Cross-Border Evidence on Minimum Wage Effects," NBER WP 32901, September 2024. https://www.nber.org/system/files/working_papers/w32901/w32901.pdf
Dube, Reich, Bhatt and Sosinskiy (DRBS), "Restaurant Employment, Minimum Wages, and Border Discontinuities," NBER WP 32902, September 2024. https://www.nber.org/system/files/working_papers/w32902/revisions/w32902.rev0.pdf
So the dispute narrows to a concrete question: should the 1990s count as valid pre-period information? JNR's specification keeps those years and gets job losses. DRBS's specifications drop them, or wall them off by event window, and do not.
CDLZ make the same argument in reverse against an earlier negative finding. On Meer and West (2016), whose two-way-fixed-effects regressions on aggregate state employment find losses, CDLZ write (Introduction, PDF p. 6): "We show that the large negative effects on employment is driven entirely by inclusion of the 1980s in the sample—a period with very few minimum wage changes." They also claim the TWFE losses show up as "an unrealistically large drop in the number of jobs at the upper tail of the wage distribution" (PDF p. 6), meaning among workers too well paid to be directly affected. I did not open Meer and West (2016). CDLZ report Meer and West's baseline aggregate elasticity as −0.074 (PDF p. 16). That figure is CDLZ's citation of Meer and West, not my reading of Meer and West.
Neumark, Salas and Wascher (NSW), "Revisiting the Minimum Wage-Employment Debate: Throwing Out the Baby with the Bathwater?" NBER WP 18681, January 2013 (published in ILR Review, 2014). https://www.nber.org/system/files/working_papers/w18681/w18681.pdf
David Neumark, "The Econometrics and Economics of the Employment Effects of Minimum Wages: Getting from Known Unknowns to Known Knowns," NBER WP 25043 (2018). Published in German Economic Review 20(3), 2019. https://www.nber.org/system/files/working_papers/w25043/revisions/w25043.rev0.pdf
The two summaries are not strictly in factual conflict. One counts signs of estimates; the other takes the median of a standardised elasticity. They answer different questions about the same body of studies, and each side says the other's metric is the less informative one.
Affiliations below are as printed on the papers I opened. "Funding" is listed only where a paper discloses it.
| Party | Side | Affiliation stated in the paper | Funding disclosed in what I read |
|---|---|---|---|
| Arindrajit Dube | no / small effect | UMass Amherst; NBER (CDLZ 2019, DZ 2024, DRBS 2024) | none found |
| Ben Zipperer | no / small effect | Economic Policy Institute (DZ 2024 title page) | none found |
| Attila Lindner | no / small effect | University College London (CDLZ 2019) | none found |
| Doruk Cengiz | no / small effect | UMass Amherst (CDLZ 2019) | none found |
| Michael Reich, Akash Bhatt, Denis Sosinskiy | no / small effect | UC Berkeley IRLE; UMass Amherst; UC Davis (DRBS 2024) | none found |
| David Neumark | disemployment | UC Irvine; NBER | NSW (2013, PDF p. 1): "Neumark and Salas' work on this project received support from the Employment Policies Institute (EPI)." |
| J.M. Ian Salas | disemployment | UC Irvine (NSW 2013) | same Employment Policies Institute support as above |
| William Wascher | disemployment | Federal Reserve Board (NSW 2013) | none found |
| Peter Shirley | disemployment | West Virginia Legislature, Joint Committee on Government and Finance (Neumark & Shirley 2022) | none found |
| Priyaranjan Jha, Antonio Rodriguez-Lopez | disemployment | UC Irvine (JNR 2024) | none found |
Name collision: the Employment Policies Institute, which funded part of NSW, and the Economic Policy Institute, Zipperer's employer, are different organisations. The papers abbreviate both as "EPI." I read no further disclosures from either side and make no claim beyond what is printed above.
The specific question of how to build comparison groups for US state minimum-wage variation has therefore been argued, paper against paper, for at least 14 years (2010–2024). The underlying question is older. NSW's abstract calls it "as old as the Department of Labor."
Yes in principle, and the border-county round is the place to do it. It is not a weekend job.
DRBS state that the negative sign depends on the first toggle (PDF p. 9). JNR state that the sign depends on commuting zones vs. cross-CZ county pairs (PDF p. 6). These are separate claims about separate switches, and both can be run on the same files.
Network and access. No paywalls were hit. Every failure was a DNS refusal for a host outside the allowlist, i.e. blocked, not paywalled. I could not try these hosts at all:
www.theunseenandtheunsaid.com — the blog post "The Methodology Laundering of Minimum Wage Research." A search summary said it argues that excluding two states from Dube–Lindner analyses yields job losses. Blocked; I use none of it.sites.socsci.uci.edu — the NSW 2014 ILRR PDF and the Neumark & Wascher 2017 ILRR reply. Blocked. For NSW I used the NBER WP 18681 preprint (January 2013) instead.escholarship.org — the Allegretto–Dube–Reich–Zipperer 2017 response. Blocked.docs.iza.org — the IZA DP 7638 version of the same response. Blocked.nber.org without www — blocked. Retrying with www.nber.org worked.How I read the PDFs. WebFetch returned raw PDF bytes for every NBER paper. It saved each file, and I extracted the text locally with pdftotext. So every NBER PDF marked read: yes was fetched in-session, and I read the extracted text, not the fetch tool's summary. Page numbers are PDF page numbers, which include the NBER cover pages, not printed page numbers. Quotes come from working-paper versions; the published QJE, ILRR and IR versions may differ in wording and pagination. I did not check them.
Unverified items.
read: no and no quoted content.What I'm unsure about.
What surprised me.
Search terms used. Bunching critique; Neumark Shirley Myth or Measurement; Neumark critique of CDLZ excess jobs; CDLZ federal-increase sensitivity; the $4 window; Neumark "Known Unknowns"; Jha Neumark Rodriguez-Lopez; NSW "baby with the bathwater"; ADRZ "Credible Research Designs"; reanalysis of CDLZ / Meer–West 1980s.
You do not need any of this: the Run button sets it up. These are the exact settings and brief the run uses, for checking it or running it by hand.
Nothing. It searches.
# Map brief — minimum wage disemployment
Paste this whole thing. Nothing to fill in.
**Environment:** `night-shift-map`. The exact settings are on this mission's
page — the env file is the only place they live, so they cannot drift out of
sync with a copy written here.
---
## The job
Modern minimum-wage research using bunching and stacked event-study designs
on public wage and employment data reports little to no job loss from
minimum-wage increases — a result now widely cited in policy debates. Other
economists, working from the same public datasets, argue the near-zero
finding is an artifact of specific researcher choices in how the comparison
is built rather than a fact about the labor market, and that reversing those
choices restores the traditional finding that minimum wages reduce
employment.
Lay out the dispute precisely: what the "no disemployment" studies claim and
on what data, exactly what choice the critique says drives the result (not
"the methods are complicated" — the specific mechanism), who is on each side
and their stake, and how long this has been argued back and forth. Because
both camps draw on the same public data, say plainly whether an outsider
could, in principle, redo the comparison and see for themselves which choice
flips the sign — that checkability is the point of picking this one.
## Sourcing rules
- Every claim about what someone said needs a citation: title, authors, year,
link, and where in the document it appears (section, figure, page).
- **Open the page.** Do not cite from a search-result snippet. If a page will
not load, say so explicitly and mark that citation as unverified rather than
quietly using the snippet.
- Quote the sentence where each party states its position. One sentence is
enough — do not reproduce passages.
- Where two sources conflict on a matter of fact (a date, a number, who did
what), show both and say they conflict. Do not pick silently.
- If you cannot find a source for something you believe is true, leave it out.
- **"Blocked" and "paywalled" are different facts — say which.** A domain
outside this environment's allowlist means you could not try. A domain that
let you connect and then returned a paywall, login wall, or bot check means
you tried and were refused. Both leave a gap in the record, but only the
second tells the reader the source exists and is readable by someone else.
For every source you could not read, the notes must say which of the two it
was. Where a paywalled paper has a preprint, use the preprint and say you
did.
## Output — two files, and both are required
**1. `output.md`** — the prose, as described above. Write it for a reader.
Structure it however reads best.
Then a section called **Notes on this run** — for me, not for a reader:
what you searched, what failed to load, which citations are unverified, what
you are unsure about, and anything that surprised you. Blunt.
**2. `positions.yaml`** — the same positions as structured data. One entry per
party per claim: a group that disputes two separate things gets two entries,
and two groups making the same claim get one entry each.
```yaml
positions_file:
mission: MAP-003
source: output.md
count: <number of entries below>
positions:
- id: P01
party: <named person or group, as the source names them>
claim: <one line, no hedging>
stake: <employment, funding, or competition — factual, or "none found">
sources:
- url: <url>
read: yes # you opened this page and read the text you cite
- url: <url>
read: no # you know it exists; you did not open it
```
**`read` is not a formality.** A URL you opened and a URL you merely know
exists are the same string, and listing one under `sources` implies you read
it. Say which. `read: yes` is checkable — an opened page leaves a fetch in
this session's transcript, which you do not write — so a `read: yes` with no
fetch behind it is a false record, and worth more scrutiny than an honest
`read: no`. Prefer citing what you read; where you must cite unread, say so
and the reader can weigh it.
**These must agree.** Every position in the prose appears in the YAML and vice
versa. The board counts entries in `positions.yaml` — it never parses your
prose, because a count derived from headings is a count that can silently be
wrong. If you can only produce one of the two files, produce neither and
deposit a finding explaining why.
An unmappable position is still a position: record it with the claim as stated
and `sources: []`, and say in the prose exactly what is missing.
## Where to put them
Push a branch to **`night-shift-network/inbox`** with both files inside a
directory named for this mission:
```
MAP-003/output.md
MAP-003/positions.yaml
```
The directory is what matters. A file at the root of the branch is not a
deposit and will not be collected — it will sit there looking delivered while
nothing has been.
The branch name does not matter and is deliberately not specified: the relay
reads every branch, so whichever branch your session is already on is fine.
Never delete or force-push a branch, yours or anyone else's; cleanup is
maintainer-side only.