Skip to content

Remove duplicate research source supplement - #18

Merged
erinepshovel-code merged 3 commits into
mainfrom
agent/remove-duplicate-research-sources
Jul 25, 2026
Merged

erinepshovel-code merged 3 commits into
mainfrom
agent/remove-duplicate-research-sources

Conversation

@erinepshovel-code

Copy link
Copy Markdown
Contributor

Purpose

Repairs the research-ledger uniqueness regression currently failing main and the synthetic merge gate for PR #17.

src/_data/research/source_supplements.yml repeats four source IDs that already exist in the primary reviewed ledger:

  • un-crpd-2014-legal-capacity
  • stephan-chenoweth-2008-civil-resistance
  • rosch-1975-semantic-categories
  • solove-2013-consent-dilemma

The duplicate records cause the executable source-identity invariant to fail (21 !== 25). All claims already resolve through the primary sources.yml, so no research evidence is removed.

What changed

  • removes the duplicate supplemental source file
  • removes the now-unused optional supplement-loading path from the Eleventy research adapter
  • restores the test to the single authoritative source ledger
  • preserves source-ID uniqueness rather than weakening or bypassing the guardrail

Evidence boundary

This is a data-identity repair only. It does not alter any research claim, stance, limitation, Article Lab content, canonical text, or external source.

Validation

The branch differs from current main in exactly three research-ledger files. The normal pull-request workflow will run the complete build, research, generated-site, browser, and accessibility gates.

hmmm

The four repeated records contained slightly different metadata wording, but not four additional sources. Retaining both versions would manufacture corpus size and make one source appear twice; the primary reviewed records remain authoritative.

@erinepshovel-code
erinepshovel-code marked this pull request as ready for review July 25, 2026 02:42
@erinepshovel-code
erinepshovel-code merged commit 7a88158 into main Jul 25, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant