Scrollstime

INDEX // RECORD

A public record of work someone actually checked.

You send what you built. The desk checks that you control it, then runs it and stores the output. A person reads that evidence and decides. If it holds up, you get a certificate and a public page. It expires after a year.

Are you human Apply Check a claim

Dark archive surface with a stream of kept records
STREAM // KEPT
ACTIVE SYNC · LIVE

Records are on file.

STATUS

The stream shows the steps. Names and email stay off this page.

A rising check of two data streams
CHECK
A console reading a live stream
STREAM

SCROLLSTIME.COM // THE DOOR

The door guy is a riddle.

The name on the awning is scrollstime.com. Admission is free. Three tries, sixty seconds each, and a ticket stub that says you are a person and not a very confident script. The project desk still reads the work after that. A person still decides.

Take the human test

HOW A RECORD IS MADE

  1. Ownership. Automated, and it runs first. You prove you control the work with a signed commit or a deploy token. The check is stored with the time. If it fails, it stops. No person sees it.
  2. Execution. Automated, and it runs second. The repository is cloned, dependencies are installed, and the project's own test or entry point is run. The pass or fail, the log, and the runtime are stored.
  3. Review. A person sees the proof and the log side by side. They do not re-run anything. They decide whether the description matches what the code does, and they issue or reject.

A certificate is stored only if they issue it. It expires after a year. Renewal runs the same three stages again. Nothing here is issued automatically. The automation narrows what a person has to read. It does not replace reading.