The operations platform.

The problem

The first tool ran on one machine, for one person. Three operators needed to convert, look up and manage loads simultaneously without double-posting, and the bots needed somewhere to live.

How it works

• Next.js on Vercel, serverless Postgres, every piece of state in the database: ledgers, daily boards, output files, settings singletons. The batch-reference counter sits inside a transaction so two people converting at once cannot collide.
• Five independent password gates on one site: the whole site, then separate second passwords on each dangerous surface. A cookie for one gate can never be replayed as another's. Server actions re-check auth themselves.
• Timezone discipline: the whole app runs on Central wall-clock time encoded consistently. A four-digit-year edge case once produced deadlines in the year 3926, which would never expire. Found, fixed in both parsers, regression-locked.
• Hard-won facts are written where the code is: a compiler quirk tests cannot catch, a clipboard format, an endpoint that re-labels times without converting them.

// every dangerous surface has its own gate, and every server action re-checks it

The result

Live since June: 210 commits over 54 build days around a full-time operations seat. The platform is the floor every other system on this page stands on.