
Scenario Overview
This scenario rehearses event-driven journaling around a scheduled macro announcement: a synthetic central bank decision, a scripted curve reaction, and modeled FX follow-through — all inside a simulation where the 'decision' is a configuration value.
Scheduled events are journaling's hardest test: everyone knows when the print lands, everyone watches the same screen, and the difference between preparation and reaction is a matter of minutes. The scenario compresses that discipline into a replayable drill.
No real central bank, statement, or policy path is simulated. 'Rate decision' here means a scheduled script that rewrites the scenario's macro parameters at a known timestamp.
Pre-Decision Fields
| Field | Written Before Announcement | Purpose |
|---|---|---|
| Expected decision | Participant's stated guess with one-line rationale | Separates prediction from reaction |
| Baseline reaction | 'If as-expected, I expect first move within X%' | Defines what 'surprise' would even mean |
| Surprise plan | Written response to a move against expectation | Converts the interesting case into a checklist |
| Trade decision | Explicit 'no new positions through the window' | Documents restraint as a choice, not luck |
| Logging trigger | Journal entry required within 5 synthetic minutes | Trains timestamp discipline under event pressure |
Simulated Observations
- The scripted curve reaction propagated through the synthetic treasury basket over two sessions — the log tags every downstream move 'scripted consequence' rather than 'market judgment.'
- Modeled FX follow-through arrived with a configured lag; the journal notes that in a real market this sequence would be contested and simultaneous, not staged.
- The participant's stated expectation missed the scripted decision; the pre-written surprise plan was invoked — the scenario's core deliverable, executed under mild synthetic pressure.
- Post-announcement, the participant logged entry ideas they did not act on — an underused Reviewbook habit that preserves the counterfactual for later honesty checks.
Expectation-Writing Under Pressure
The exercise's hidden subject is the five-minute window after the announcement. Writing an expectation then is worthless — it is contaminated by the print. Writing it before is the entire discipline, and the scenario makes the contamination visible by replay.
The log therefore timestamps its pre-decision fields separately and treats them as the primary artifact; everything written after is annotation.
Repeated across several event scenarios, these pre-decision fields become the participant's calibration record — a private history of what they expected versus what the script delivered, which no sandbox outcome can substitute for.
Methodology and Limits
A scripted decision has no information content — it is a parameter change wearing a suit. The scenario cannot teach whether a cut or hike was 'right,' how markets really digest surprise, or what a real statement's language does to positioning.
It can teach the mechanics of event preparation: expectation fields, surprise plans, restraint documentation, and fast timestamped logging. That boundary is stated inside the log itself.
Review Checklist
- Were all pre-decision fields completed and timestamped before the scripted announcement?
- Was the surprise plan invoked, and was its invocation logged?
- Are unexecuted post-announcement ideas preserved for later review?
- Does any entry treat the scripted reaction as macro evidence? (It must not.)
Review Takeaways
Event discipline is rare and cheap to practice — the scenario exists to make 'prepared for the print' a routine journal state rather than a heroic one.
The review's sharpest question is always the same: was the expectation written before the number? Everything else in the entry is decoration.
Frequently Asked Questions
No. The 'decision' is a scripted parameter change at a scheduled timestamp. No real central bank, statement language, or policy path is modeled — the event is a drill in preparation, not economics.
They exist because writing an expectation after the print is contaminated. The scenario makes the contamination visible: fields timestamped before the announcement are the artifact; everything after is annotation.
Unexecuted ideas preserve the counterfactual. Months later they let you audit whether restraint was discipline or luck — data no executed-trade log can supply.
No, and the log says so explicitly. The exercise teaches event mechanics — expectation fields, surprise plans, timestamp discipline — which transfer to real events; the scripted outcome does not.
Review Note
A simulated rate decision rehearses expectation-writing, not macro forecasting.
Continue Exploring
Large and Small Caps Divergence
Studying Russell 2000 vs. Nasdaq 100 tracking differentials and liquidity friction within simulated small-firm equity baskets.
Janus Henderson Markets Overview
A comprehensive appraisal of sovereign debt benchmarks, corporate credit spreads, and cross-asset correlation models.
US GDPNow Data Simulation
Simulated real-time tracking of Atlanta Fed growth estimates and sectoral sensitivity analysis across synthetic portfolio configurations.