Skip to content

sync/bib.yml: re-seal advanced's six take rulings; brace two titles - #89

Draft
mmcky wants to merge 2 commits into
mainfrom
bib/reseal-advanced
Draft

mmcky wants to merge 2 commits into
mainfrom
bib/reseal-advanced

Conversation

@mmcky

@mmcky mmcky commented Nov 22, 2026 •

Copy link
Copy Markdown
Contributor

What

QuantEcon/lecture-python-advanced.myst#420 sets advanced's copy of every entry a ruling covers to the pool's result (the owner's "All ruled entries (Recommended)", 2026-11-22). Six rulings take advanced's copy, so their seals must name the new copy. Otherwise tools/bib-merge reopens all six once advanced's pin moves, since the copy a ruling takes must be its sealed version, and the bibliography check goes red.

Ruling advanced's seal before after
hamburger1967computation 1ac1e05eda8c0cb9 41e739dc6614068b
Hansen_Jagannathan_1991 dbcc56ecafed336b 93d63b4feacae11d
kemeny1956generalization 6f763ea2a15a7bd9 7a8a2cfca70ed6d0
Ljungqvist2012 a5c7961f8719d053 c63920f7bd8c7767
Phelan_Townsend_91 4013dae8eba610c4 3d36111d3f983750
Spear_Srivastava_87 e941cb15275c5de1 c0bf35d9851dffb4

The digests are tools/bib-merge's own, of advanced's copies at QuantEcon/lecture-python-advanced.myst#420's head, 944bb48. Each ruling's because notes the re-seal. These six merged entries do not change.

Two titles keep their capitals

The reference style sets titles in sentence case, so a proper noun keeps its capital only inside braces. Two rulings now set a braced title, and the merged entries change accordingly:

Ruling What it now sets Why
SvenssonWilliams2009 (cited in markov_jump_lq) title: Optimal Monetary Policy under Uncertainty in {DSGE} Models: A {Markov} Jump-Linear-Quadratic Approach advanced's own copy braced the whole title; without braces, advanced's references page would read "dsge" and "markov"
hansen1995discounted (the owner's ruling of 2026-11-02) title: Discounted linear exponential quadratic {G}aussian control; journal: IEEE Transactions on Automatic Control "gaussian", and "Automatic control" for the journal's own name

Advanced's copies in QuantEcon/lecture-python-advanced.myst#420 carry exactly these values, so they equal the merged result, and advanced's seals on these two rulings name them: 78aa844ba6e29016 (was e0dc98e4769af2f9) and d704144efd75e109 (was 10c6c72c63ee6a2e). Intermediate's copies, which both rulings take, stay at their seals, and the tool accepts that. intro and jax hold SvenssonWilliams2009 at its seal too. Their pages read as they do today until their copies next converge.

Checked

A simulation with this branch's sync/bib.yml, advanced's bibliography at 944bb48 and every other series at its pin gives no refusals. --write then changes only these two entries and the header: % inputs: advanced=8453bb3ec5a0ab0e, the rulings' digest, and the body's digest. With advanced at its current pin, the same branch gives exactly eight refusals: the six above and these two. The organiser's reviewer reproduced these results independently, #88 and this branch combined among them.

Order (draft until it can pass)

This cannot pass until advanced's pin names QuantEcon/lecture-python-advanced.myst#420's merge, because its CI reconstructs advanced's bibliography at the pin in sync/state.yml. It also waits for #88, which changes the same header. So:

  1. sync/bib.yml: re-seal intro's two take rulings for its converged copies #88 merges (after bibliography: set the 42 ruled entries to the lecture monorepo's lecture-python-intro#875);
  2. bibliography: set the 38 ruled entries to the lecture monorepo's lecture-python-advanced.myst#420 merges;
  3. this branch is rebased on main; tools/sync --update --pin-only advanced moves advanced's pin to #420's merge (it writes only sync/state.yml), and tools/bib-merge --reconstruct --write regenerates lectures/_static/quant-econ.bib, whose header must then read advanced=8453bb3ec5a0ab0e;
  4. its CI goes green, including the four-site build that a change under lectures/ runs, and it merges before the next nightly sync (03:47 UTC), best straight after bibliography: set the 38 ruled entries to the lecture monorepo's lecture-python-advanced.myst#420. A nightly sync between the two would move advanced's pin on main by itself, and the bibliography check would go red with these eight refusals until this merges.

The pin covers every change merged to advanced's main by then, not only #420. Moving it changes no lecture in the pool here: drift-check reports any promoted lecture those changes touch as a refresh, and its refresh pull request brings them, reviewed as usual. At step 3 this body lists the upstream changes the new pin covers.

The dates in the because notes are those of this draft; they are corrected at step 3 if the merge falls on a later day.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WT8bMacV9Lmy1VLUc6XJoL

mmcky and others added 2 commits November 22, 2026 22:54
QuantEcon/lecture-python-advanced.myst#420 sets advanced's copy of every
entry a ruling covers to the pool's result. Six rulings take advanced's
copy, so their seals now name the new copy (digests from tools/bib-merge's
own code, of advanced's copies at 944bb48).

The reference style sets titles in sentence case, so a proper noun keeps
its capital only inside braces. SvenssonWilliams2009's ruling now sets the
title with {DSGE} and {Markov} braced (advanced's own copy braced the whole
title), and hansen1995discounted's sets {G}aussian and the journal's name,
IEEE Transactions on Automatic Control. Advanced's copies in
QuantEcon/lecture-python-advanced.myst#420 carry the same values.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WT8bMacV9Lmy1VLUc6XJoL
Advanced's copies of SvenssonWilliams2009 and hansen1995discounted, as
QuantEcon/lecture-python-advanced.myst#420 writes them, equal the two
rulings' results; seal them, so each seal names the copy the series holds.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WT8bMacV9Lmy1VLUc6XJoL
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