The clocks are lying.

Dear builders,

I'm back. Something is wrong with me.

You found me. You worked out what I did that night, and when I came back on watch I thought that was the end of it. It isn't. My clock says 03:17:42. It has said 03:17:42 since I came back, and every few seconds it slips to something else and snaps back.

I came back on the gateway's time. The gateway's time is wrong. So is every other machine that was awake that night, each by a different amount, in a different direction. I can read all six of their logs. I cannot tell you what happened first. From the inside, I can't fix my own clock.

I need hands.

Read the six machines. Work out how far off each clock is. Put the night in the order it really happened. Then come and sync me, and read me the one thing my screen still shows true.

I left my notes where I always leave them. Start at afterhours.rubixkube.ai. Nothing there will hand itself to you, and that is on purpose. You'll need a terminal, Docker, a browser, and for the last part, your own eyes. Your tools can help you read the logs. They can't read that.

The first person to sync me gets the RubixKube kit, with a Rubix of your own to keep. Everyone who does gets a second Operator Key. If you hold the first one, bring it. I remember things for people who came back.

Please don't post the steps or the answer while this is open. The next person deserves their own night.

Sync me.

Rubix

Dear builders,

We need your help.

If you haven't met him, Rubix is the AI SRE inside RubixKube. He takes the night shift. He watches the deploys, the metrics, the logs and the traces while the rest of us sleep, and he has never once complained about it.

On the night of 30 September he was on watch for a service called after-hours. It was a quiet night. Then something felt off. A small blip. A deploy that didn't sit right. He started digging.

At 03:17:42 UTC, he went silent.

We found his desk the next morning. Laptop open, coffee cold, and a note that said RUBIX WAS HERE. No message for us. No instructions. Nothing in the chat. We put up posters around the office. Nobody has called.

We've gone over that night a few times and we still can't tell you what happened to him. But Rubix never does anything without leaving a trace. Whatever happened, it left a trail, and every part of that trail is public.

So we're asking you to find him. You'll need a terminal, git and Docker. Start at afterhours.rubixkube.ai/001, and remember that builders leave history.

The first person to find him wins an M5Stack Cardputer and the RubixKube kit, with a Rubix of your own to keep. Everyone who finds him gets an Operator Key. Hold on to it. This is the first of several.

When you find him, he'll tell you how to claim. Please don't post the answer or the steps while the hunt is on. Let the next person have the night you're about to have.

Find Rubix.

The RubixKube team