About the lab

One bench, built in the open.

Jorik Rook is a small personal R&D lab: circuits, simulation and the tools that sit between them. This page explains the name, what is on the bench and the rules it runs by.

01 · Who

A working name for one engineer’s lab

Jorik Rook is the working name for one engineer’s personal lab. The engineer behind it likes circuits that behave, simulations that agree with the bench, systems drawn as boxes and arrows before anyone writes code, and dashboards that answer a question in one glance.

Most of what gets built here is built for its own maker first: a calculator that should have existed, a plot that explains a bug, a checklist turned into a tool. The things that hold up after a few weeks of real use get cleaned up and published. The rest stays on the bench, and that is fine.

02 · Why a rook

Straight lines, guarded corners

The rook is the plain piece on the board. It moves in straight lines, holds the corners, and when it is time to castle it steps in to protect the king. That is a fair description of good engineering work: direct, dependable, quietly defensive.

Under the rook sits a step-response curve: a system answering a sudden input. It overshoots a little, rings, and settles on the new value. Every project here works the same way. Take a step, watch what the system does, let it settle, then take the next one. One step further at a time.

Step responseAn input steps from low to high; the output rises, overshoots, rings briefly and settles on the new level.stepovershootsettled
input response

03 · On the bench

Four tracks of work

Everything here starts as something the bench needed. These are the four tracks it is growing along; each one ships as its own tool when it is ready.

04 · How it’s built

Small stack, written down

Site
Astro, static output, a little vanilla TypeScript
Hosting
Cloudflare Workers, serving static assets
Changes
Every change goes through git; a push to main builds and deploys
Help
AI-assisted, with a human reading every diff before it ships
Look
One set of design tokens shared by every part of the lab
  • Own use first

    Every tool starts as something needed on the bench this week. If it does not earn its keep there, it does not get published.

  • Show the work

    Plans, roadmaps and half-finished ideas are written down in the open. Dates are indicative; reasoning is included.

  • Demo data is labeled

    Anything that looks like a measurement but is not one says so, right next to the number.

  • No tracking cookies

    No ad trackers, no third-party fonts, no embeds that phone home. Fonts are self-hosted.

05 · Contact

Say hello

Questions, corrections, or a problem that sounds like it belongs on this bench: write to hello@jorikrook.com. Replies are slow but real.