Systems Corp. is a work of fiction: a company in Beige, Kansas that has been providing systems since 1987 and would prefer not to elaborate. No such company exists. The memos, press releases, personnel records and the annual report are written to be read the way a stranger reads a filing cabinet, one document at a time, noticing what the documents decline to say.
╔═════════════════════════════════════╗ ║ NOTE FROM THE SYSTEMS ARCHITECT ║ ╚═════════════════════════════════════╝
Every system has an author. Most systems work very hard to make this fact unrecoverable. The forms are unsigned. The policies are "company policy." The memos come from "Management." The friction arrives without a return address. This is how systems encode the values of their makers while disclaiming that they had any.
Systems Corp. is a system that admits it. The reason a new hire is asked to acquire Module 7's escalation paths informally, the reason Form 17-C exists only because Form 17-B failed, the reason the cafeteria can suspend Thursday meatloaf without explaining why: these are not accidents of a 1990s office. They are every office. They are, quite possibly, yours.
If any of it rings true, the author would like to hear about it: kelsy.design. The name on the company door is Kelsy Gagnebin.
╔════════════════════╗ ║ HOW IT IS MADE ║ ╚════════════════════╝
The world is a folder of plain text files, one per document. A registry lists every person, room, form and system the documents can mention, and at build time every mention becomes a link to that subject's Index card, which lists every document that records it. Nobody links anything by hand.
The public pages ship no JavaScript files, no web fonts and no trackers. The photograph on the front page keeps your local hours.
Between April and November 2026 this address served a simulated desktop operating system. It has been retired. Its documents were kept.