Catalyst Calendar vs Experience Journal

A catalyst calendar answers: when might information arrive?

An experience journal answers: what did I risk, what shape did I think I bought, how long did I give it, how did I mean to get paid, and what did I learn when reality showed up?

ConvexClub is built for the second object. We still respect the first. We just refuse to let calendars cosplay as theses. If that identity cut is new, start with asymmetric risk journal ≠ day trading.

In this guide

1. What a catalyst calendar is good for
2. Where calendars quietly become tips
3. What the experience journal must capture
4. Signal-only experiences without becoming a tip feed
5. Circles: process talk, not countdown theater
6. Templates that stay process-shaped
7. A weekly habit that does not melt together
8. Try this yourself

What a catalyst calendar is good for

Operational awareness. Earnings dates. Court rulings. Permit hearings. Unlock schedules. Lease renewals. Election certification days. Product ship windows.

Useful questions a calendar supports:

• Do I need liquidity before a known event?
• Is my review gate accidentally set the day after a binary print?
• Am I pretending I will be attentive during a week I already know is chaotic at work?

None of that requires a buy/sell call. It is schedule hygiene.

Partners who take asymmetric bets across domains keep different calendars: IR pages for listed names, city permit dashboards for renovations, token unlock tables, customer contract renewals for a small business. The tool can be a spreadsheet. The danger is cultural, not software.

Where calendars quietly become tips

Watch the language drift:

• "Everyone knows this earnings is the setup."
• "Unlock week is free money if you time it."
• "The hearing is the catalyst; size up."

Those sentences smuggle recommendations into date math. They also collapse company time into personal judgment time. Our mixed-outcome composite in Horizon longer than the headline exists partly because that collapse is common.

Another failure mode: building a public "watchlist calendar" that functions as a tip feed with timestamps. ConvexClub will not productize that shape. If you want countdown theater, other apps already compete there.

What the experience journal must capture

After an event lands (or fails to land), the journal cares about:

• Budget that was actually exposed across the window.
• Whether your risk–return shape assumed a binary outcome.
• Whether your horizon was the event or a longer repair path.
• Monetization: did you need to trade the event, or were you funded by a slower path?
• Lesson: what broke or held.

The five factors are spelled out in Five factors of an asymmetric experience. Calendars do not replace them.

Example contrast, no ticker:

Calendar note: "Print on May 2."

Experience note: "I sized 4% into a binary margin print with a two-week horizon. Monetization was a same-day sell rule I did not follow. Outcome mixed. Lesson: binary calendar events need pre-committed size cuts, not vibes."

Only one of those belongs in ConvexClub as a first-class object.

Signal-only experiences without becoming a tip feed

Outcome class signal_only exists for times you observed a process lesson without a full capital commitment, or you logged a watch that never became a bet.

Rules we use internally for signal_only quality:

• Past tense or clearly marked observation window that has closed.
• No "you should."
• Name the constraint or mechanism, not a shopping list.
• Prefer lessons like "custody assumptions failed under withdrawal queues" over "coin Z goes up after unlocks."

Historical process lessons (FTX custody stress, property-credit rollover dependence) belong as mechanisms. We discuss those carefully in Journaling across domains without turning them into recreatable plays.

If a signal_only entry reads like a pitch, rewrite it until it reads like a lab note.

Partners sometimes ask whether a pre-event checklist belongs in the journal or the calendar. Our bias: checklist items that change budget, horizon, or monetization belong in the experience draft before the window. Checklist items that are pure ops ("confirm wire cutoff times") can stay on the calendar. When in doubt, put it in the experience once. Duplication is cheaper than a missing lesson.

Circles: process talk, not countdown theater

Circles on ConvexClub are meant for people who already write experiences: comparing how budgets and horizons were honored, not coordinating entries into next Tuesday’s event.

The public feed stays gated while the Founding Experience Partner cohort proves the habit. That is intentional. Empty rooms fill with calendar chatter because chatter is cheap. Process writing is not.

If you want in early, start at signup and follow the partner path described in Founding Experience Partners. Circles without writers are just Discord with better typography.

Templates that stay process-shaped

A calendar line that stays useful:

2026-09-12 | Company print | Personal review gate already set for 2026-09-20 | No size change pre-committed

An experience line that stays useful:

Budget 3.5%. Horizon through 2026-09-20. Monetization: half cut if thesis variable misses; else hold to written gate. Outcome TBD.

A tip-shaped line we reject:

Print week = long. Size up into weakness.

If your notes lean toward the third, ConvexClub will feel annoying. That annoyance is diagnostic.

Real estate and business calendars deserve the same discipline. Permit hearing dates and customer renewal dates are catalysts. Your renovation budget overrun or your key-employee dependency are experience factors. Do not let the hearing date become a substitute for writing carrying costs.

A weekly habit that does not melt together

A pattern that survived partner weekly reviews:

1. Sunday (or your quieter day): update the catalyst calendar for the next two weeks. No sizing decisions in that sitting.
2. When you open or change a real bet: write or amend the experience draft with core five before the event window.
3. After the window: close the loop in the journal within 72 hours. Outcome class + lesson.
4. Once a week: reread one old experience. Ask whether your calendar hygiene or your journal honesty is drifting.

If step 1 starts producing trade ideas, you are not doing step 1 anymore. Separate the browser tabs. It sounds childish. It works more often than willpower speeches.

Cross-border events add jurisdiction wrinkles; a hearing date in one country does not imply your capital can move on that same day. See Same thesis, different jurisdiction.

Also notice what we are not publishing here: a dated list of "asymmetric setups" for the next quarter. That format converts signal posts into tip sheets. If you came for that, you will be disappointed on purpose. The signal is the habit split, not a countdown.

Try this yourself

Create an account via signup. Log one past experience where a catalyst date hijacked your horizon. Then write a signal_only note about a calendar habit you are retiring. Keep related reading handy: five factors and max-loss exits.

Not advice. Habit design.

Next steps

Start free · Horizon vs headline · Partners