When scheduled links are useful

Most short links should be boring: one slug, one destination, one clear owner. Scheduled links are for the few cases where the slug should stay stable but the destination needs to change during a predictable time window.

The starter instance includes a deliberately silly /contact example. During the configured 9-to-5 window, it can point to Dolly Parton’s “9 to 5”; outside that window, it falls back to Rick Astley and “Never Gonna Give You Up.” The point is not the music taste, heroic as it may be. The point is that one memorable short link can have a normal destination and a time-based exception.

Good use cases

Scheduled links are useful when people already know the slug:

• a recurring meeting link that points to the work room during office hours and a community room after hours
• an event link that points to registration before the event and a recording afterward
• a launch link that points to a waiting page before release time and the live page afterward
• a support link that points to a maintenance notice during a planned outage

In each case, the human memory stays stable. The route changes underneath it.

Keep the link inventory readable

The slug and the normal fallback target belong in v8s-links.txt. The schedule adds indented @schedule lines directly below that link row. If no schedule rule is active, the Worker falls back to the normal target.

That keeps review sane. One small block answers both “does this slug exist?” and “when does the destination change?”

Prefer the CLI

For 3.x compatibility, lnk schedule still writes the legacy JSON schedule file. For new hand-authored changes, prefer inline @schedule lines in v8s-links.txt.

Use Scheduled links for exact examples, and compare the starter contact block in defaults/v8s-links.txt when you want a concrete reference.