a clock for time that refuses to be a line

CP TIME CLOCK

Set when the party starts, drag the hands to when you'd actually arrive, and the clock will tell you not how late you are — but what shape your lateness takes.

How to use it

  1. Read the prompt below the dial.
  2. Drag the coral hour hand to your arrival hour.
  3. Drag the cyan minute hand to your arrival minute.
  4. Click AM / PM to set the half of the day.
  5. Hit Calculate CP Time.
  6. Your temporality lights up in the Atlas — and your Remedy appears.
12
1
2
3
4
5
6
7
8
9
10
11

The Temporality Atlas

Six shapes time can take once it stops pretending to be a straight line. Each diagram moves the way that temporality actually behaves.

≤ 0.5 hrs

Linear

Passing as punctual. Blending into dominant clock-time without notice — or you're about to leave early.

≤ 2 hrs

Cyclical

Rhythmic loops and returns.

≤ 4 hrs

Fractal

Nested lateness — recursive folds of memory, patterns within patterns.

≤ 6 hrs

Oscillatory

Temporal pulses — presence and absence swinging in and out.

≤ 8 hrs

Coiled

Spiral time: layered, compressed narrative.

> 8 hrs

Speculative Other

Fugitive deep-time. Quantum Black time, imagining beyond this dimension.

The Remedy

Tardiness isn't a character flaw — it's a communication problem. The late person and the on-time person are operating on different temporal grids, and neither is wrong. The fix isn't discipline. It's translation.

rooted in trickster epistemology — the trick exposes the myth of a universal clock
℞ Linear — ≤ 30 min
Diagnosis
You treat the stated time as a contract. When others don't show up, it reads as disrespect — but they may be working on a different calendar entirely.

The trick: Stop giving one time. Give a window — "come anytime between 7 and 7:30." You still arrive at 7. They feel welcomed at 7:20. Nobody loses.

If you need them somewhere at 7, tell them 6:30. The gap is the gift.

Sig: reframe the start time as a range, not a deadline. Punctuality is a dialect, not the language.
℞ Cyclical — ≤ 2 hrs
Diagnosis
You move on social time — when the vibe is ready, you move. Clock time feels arbitrary because for you, time is relational, not numerical.

The trick: Your friends should tell you "doors at 6" for an event that starts at 7. You'll arrive at 6:45 feeling early. They'll feel relieved. The party starts on time.

Or: have someone text you "we're all here" — that's your real start signal.

Sig: your clock runs on presence, not position. Work with it, not against it.
℞ Fractal — ≤ 4 hrs
Diagnosis
You're always inside a previous task — time folds inward and each delay contains smaller delays. You intended to leave at 6:45 but that required finishing something that required something else.

The trick: You need two reminders — not one. One an hour before. One 30 minutes before. Text, not call — calls pull you back in.

Block a "transition window" on your calendar: a fake dead zone between the task and the event where nothing is scheduled.

Sig: the problem is the handoff between timelines, not the destination. Build the bridge earlier.
℞ Oscillatory — ≤ 6 hrs
Diagnosis
Your presence pulses — sometimes early, sometimes hours late, hard to predict. It's not inconsistency, it's responsiveness: you arrive when the energy calls you.

The trick: Don't anchor oscillatory people to a clock time — anchor them to a feeling or a window. "Come through whenever, we'll be here 'til midnight." They will come when they come, and it will be the right time.

If it's a hard start, designate someone to be the beacon — a friend who texts "it's time" when the vibe peaks.

Sig: oscillatory time is rhythmic, not random. Read the rhythm; don't fight the wave.
℞ Coiled — ≤ 8 hrs
Diagnosis
You operate on a compressed, layered timeline — everything is nested in longer arcs. A 7pm event is still hours away at 3pm; by 9pm it's barely begun in your internal calendar.

The trick: Plan the next gathering at the end of the current one, in person, so the commitment is anchored to a memory, not a date. Set their reminder for two hours earlier than the actual time.

Better yet: don't invite coiled people to start times. Invite them to the middle — "we'll be deep in it around 9."

Sig: coiled time is accumulative. You're not running behind — you're running a longer loop.
℞ Speculative Other — > 8 hrs
Diagnosis
You operate outside the event horizon of standard clock-time. This isn't lateness — it's a different temporal dimension entirely. The party exists on a timeline you will enter eventually, from an angle no one predicted.

The trick: Do not give a time. Give an address and a vibe. "It's happening. Come when you come." The event is already underway by the time you receive the invite — and that's fine.

If someone is counting on you, give them a conditional commitment: "I'll be there before midnight" — a range with a ceiling, not a point on a line.

Sig: fugitive time refuses the master's clock by design. Showing up is the act. When is secondary.