← All projects
Automations That Run on a Scheduleintermediate · ~100 min

The Third Business Day, Not the Third — a Holiday-Aware Gate for Every Scheduled Job

Your billing run is supposed to go out on the third business day of the month — so why does your crontab say "the 3rd"?

Every scheduler on every operating system can fire on a date, and none of them knows that the third of January 2026 was a Saturday, that the third of April 2026 was Good Friday, or that the last business day of December 2027 depends on a holiday in a different year. The gap between "the 3rd" and "the 3rd business day" is where invoices go out early, dunning notices go to people who already paid, and a month-end close lands on a day the bank is closed. This project has Claude Code build you a small gate that sits in front of any job you already own and answers one question honestly: is today actually the day?

🤝 Want this built for you? Start a request — our AI scopes it, estimates a price range, and matches you with a vetted AI Advisor.
Share this:
The Third Business Day, Not the Third — a Holiday-Aware Gate for Every Scheduled Job
Unlock this walkthrough

Two ways to open it

Just this build
$10 one-time

Unlocks this full walkthrough on your account — no subscription, and no account needed until you check out.

Best value Over 160 projects + the full course
$99 / year

Over 160 project walkthroughs, the 6-week course, and your certificate.

🔒 Secure checkout by Stripe · Already a member? Sign in

What you'll do

A holiday-aware schedule gate you own: one plain-text schedule file that states each job's calendar, anchor rule, and roll convention as data rather than as a comment in a crontab; a resolver Claude Code builds that turns those rules into real dates using the published US federal and NYSE calendars; an eighteen-month agenda preview you can hand to a colleague; an explain command that reconstructs why any single date was chosen or rejected; a frozen calendar snapshot plus a drift check that tells you when the holiday data underneath you has changed; a fail-closed exit-code contract so a broken calendar skips the run instead of guessing; and a cron entry that has been proven on four hard dates without waiting a month for any of them.