MétaCan
Menu
Back to cohort
Record W2151620757 · doi:10.1111/1467-9396.t01-1-00344

Monetary Policy and Built–In Stability

2002· article· en· W2151620757 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueReview of International Economics · 2002
Typearticle
Languageen
FieldEconomics, Econometrics and Finance
TopicEconomic Theory and Policy
Canadian institutionsMcMaster UniversityBank of Canada
Fundersnot available
KeywordsEconomicsExchange rateMonetary policyRobustness (evolution)Supply sideBusiness cycleStabilization policyInterest rateMonetary economicsConsumption (sociology)Open economyMacroeconomicsAggregate demandKeynesian economics

Abstract

fetched live from OpenAlex

Concern about globalization has rekindled interest in a longstanding issue—the implications for macroeconomic stability of alternative monetary/exchange–rate policies. This paper re–examines the issue, and it assesses the robustness of several recommendations by comparing the results of a series of small open–economy macro models. All involve model–consistent exchange–rate expectations and (through the existence of intermediate imports) supply–side effects of exchange–rate changes. The first model is descriptive, while the second and third allow for more thorough–going micro foundations and forward–looking behavior—first on the supply side (with multiperiod overlapping contracts), and then on the demand side (with the Ramsey theory of consumption). To clarify the impact of each change in model specification, they are introduced one at a time, and the same questions are posed at each stage. Two issues are examined—the implications of alternative monetary policies for (i) the effect on output of a one–time (unexpected) change in demand, and (ii) the effect on the amplitude of the business cycle that accompanies an ongoing (anticipated) cycle in demand. Three policies are compared: price–level targeting, wage–rate targeting, and exchange–rate targeting.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.529
Threshold uncertainty score0.998

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0020.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.042
GPT teacher head0.261
Teacher spread0.219 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it