06 · Digests
Event-risk calendar
One forward calendar for macro prints, unlocks, listings, and governance votes that can move books you hold.
- Level
- Intermediate
- Cadence
- Rebuilt at the start of the week, checked each morning
- Read
- 8 min
- Updated
Definition
An event-risk calendar lists scheduled items inside your horizon: macro prints, token unlocks, listings, and governance votes. Each row has a time, a timezone, a source, and the book it can touch. Unscheduled rumors do not get a row.
Who it is for
Traders who get surprised by scheduled events they could have seen on a calendar.
Job to be done
Maintain a forward calendar of scheduled events that can reprice markets you trade, with source and timezone.
Human gate. You mark which rows change how you hold risk into the event. The calendar does not tell you the direction.
Inputs and outputs
Inputs
- Markets you hold or plan to trade this week
- Horizon in days
- Sources you accept for macro times, listings, votes, and unlocks
- Your timezone
Outputs
- Rows sorted by time, inside the horizon only
- Source and timezone on each row
- Which position or plan the event can touch
- A rumor bin for undated chatter
Step-by-step workflow
- 01List books firstEvents that cannot touch a book you hold or a trade you planned this week stay off the page.
- 02Pull scheduled sourcesMacro calendar, venue listing notices, governance proposals with a vote time, unlock rows you already verified.
- 03Normalize timezoneConvert to the timezone you trade in, and keep the original zone in the source note.
- 04Drop undated itemsIf there is no time, it is a rumor. It can sit in a bin. It cannot sit between two real rows.
- 05Attach the bookEach row names the position or the plan. A row with no book is a candidate for deletion.
- 06Human gateYou decide whether you want to be smaller, flat, or unchanged into the event. The row does not pick a side.
Suggested tool types
These are categories of tools, not product picks. Crypto Agent Desk does not certify vendors and does not run an affiliate program.
| Type | Why it is here |
|---|---|
| Official calendars and project governance pages | Scheduled means someone published a time. |
| Unlock notes from the unlock playbook | Reuse that table instead of a second folklore list. |
| Chat model | Merges rows into one timezone. It should not invent a time to fill a gap. |
| Calendar or spreadsheet | You will look at it on a phone before the print. |
Risks and failure modes
Invented timestamps
Models fill gaps. A missing time is an incomplete row, not an excuse to guess the hour.
Direction smuggled in
"Hawkish event" is a view. The row is the event name, the time, and the book it touches.
Double counting unlocks
If the unlock calendar already has the row, link it. Do not maintain two conflicting dates.
Operator notes
Scheduled risk is the kind you are not allowed to call a surprise. The calendar is a filter, not a newspaper.
Row
Time in your zone, event, source, original zone, book it touches, your hold note left blank. No arrow for direction.
Prompt you can paste
Build a forward calendar. Horizon: DAYS days. Timezone: ZONE.
Books: BOOKS.
Scheduled items with sources: ITEMS.
Convert times to ZONE and keep the source zone.
If an item has no published time, put it in a rumor bin.
Do not predict direction. Leave a blank "hold note" for me.
Link unlock rows instead of inventing a second date.Done when
The next event that can touch an open position has a time you could put in a reminder, and you know the source.
FAQ
How is this different from the morning digest?
The digest looks backward over a window that already happened. The calendar looks forward at things with a published time.
Should I include every macro print?
Only if it can change a book you have. A full global calendar is how the one print that matters gets buried.
What about an event that "might" be this week?
Without a published time it stays in the rumor bin. You can check again tomorrow.
Published . Updated . This is an operating playbook, not a recommendation to buy, sell, or hold any asset.