Skip to content

AGENTS: the manifests are the upstream-delta register of record #125

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mmcky merged 1 commit into from
Sep 7, 2026
Merged

AGENTS: the manifests are the upstream-delta register of record #125

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ Cross-repo repoints are worked from [`QuantEcon/workspace-lectures`](https://git

### Repointing a lecture — one scope rule

- **A migration moves bytes; it does not update them.** Land the copy the lectures already consume, validated byte-identical — that is what makes a repoint provably unable to change a figure. If the committed file differs from what upstream publishes today, migrate it unchanged anyway, record the delta in `integrity.upstream` **and** in the register at [#39](https://github.com/QuantEcon/data-lectures/issues/39), and leave the decision for after the migration. Adopting a newer vintage changes lecture output and is an author's call, not an infrastructure one — and per "Corrections vs vintages" below it gets a **new filename**, never a silent replacement.
- **A migration moves bytes; it does not update them.** Land the copy the lectures already consume, validated byte-identical — that is what makes a repoint provably unable to change a figure. If the committed file differs from what upstream publishes today, migrate it unchanged anyway, record the delta in `integrity.upstream` — **the manifest is the register of record**, and the generated catalog shows the delta from the day it is found — and leave the decision for after the migration. The upstream-delta register issue [#39](https://github.com/QuantEcon/data-lectures/issues/39) was that register while the migration ran; it closed on 2026-09-07 once the migration completed (40 of 40 repointed 2026-08-18, strict audit green) and its review step had run (2026-09-01: `mpd2020.xlsx` and `life-expectancy-vs-gdp-per-capita.csv` kept deliberately, `business_cycle_data.csv` refreshed by #112). Its history is the worked example of the three steps; new deltas need no issue — set `integrity.upstream` in the same PR that finds them, and the catalog is where a reviewer looks. Adopting a newer vintage changes lecture output and is an author's call, not an infrastructure one — and per "Corrections vs vintages" below it gets a **new filename**, never a silent replacement.

### Corrections vs vintages

Expand Down
Loading