A Farewell Script · Zenfulfillment Engineering
Architect of ZenOS · 62 Tokens · No Bluffs
Some engineers ship features. Some quietly remove the reasons anyone had to open the production database at eleven at night. Jonas did both, for four years, without ever once being the loudest person in the room.
SEP 2022 — AUG 2026 // PROJECTS: ALKT · IT
The Good Team
Twelve characters he played, all at once, across four years. Each ability is a real thing that is running in production right now.
You start knowing nothing about inbound transport. By dusk there is a Freight Forwarder role, transport fields, a pickup workflow and a price negotiation — and a stranger can log into ZenOS and move your pallets.
IT-1010 · IT-1011 · IT-1012 · IT-1014 · IT-1015 · IT-1070
Each time DHL rejects a reimbursement because the totals do not add up, you may rebuild the PDF. Eventually DHL runs out of reasons.
ALKT-547 · ALKT-548 · IT-926 · IT-996 · IT-997
Suppliers see only their own purchase orders. Before you, every supplier saw everyone’s. Nobody had noticed.
ALKT-386 · ALKT-394 · ALKT-513
Each night, inventory that arrived under a blocked batch number and believed itself free is blocked again — this time in Storelogix, where it actually counts.
ALKT-507
Each night, returns that were announced but never shipped leave the Grimoire. Returns that arrive without a label are finally seen.
ALKT-433 · ALKT-534 · ALKT-569 · IT-934
Warehouse workers in Aschaffenburg read German. Warehouse workers in Szczecin read Polish. This required considerably more than a dictionary.
ALKT-528 · ALKT-532
You know where every Packstation, Paketshop and Postfiliale stands, and you tell DHL and Hermes in real time. You also worked out that a Postfiliale never needed a Postnummer to begin with.
ALKT-471 · ALKT-474 · ALKT-479 · ALKT-533
Orders may now change fulfillment centre without anybody opening a production database at 23:00 and pasting in a list of UUIDs. Operations has not stopped thanking you.
ALKT-361
External return providers, partners and safety-stock consumers may speak to ZenOS through an actual endpoint instead of an email and a hope.
IT-855 · IT-1547 · ALKT-563 · ALKT-571
You choose what ZenOS whispers to Azza: reserve the stock or don’t, send the bundle configuration, mark digital products inactive, leave the warehouse SKU unprefixed.
ALKT-495 · ALKT-499 · ALKT-502 · ALKT-406
A refund may be taken as store credit. The money never leaves the shop, the customer gets a bonus, and the merchant sends you a very nice message.
ALKT-568
Every export gains the thing it was missing — the ZF number, the shipping date, and the carrier’s own words about where the parcel actually is.
ALKT-427 · ALKT-506 · ALKT-560 · ALKT-500
Also on the Good Team, Technically
Every script needs characters whose ability is mildly inconvenient for everyone, including themselves.
You start knowing the answer. Six of your tickets produced no code whatsoever — only the truth, which turned out to be the expensive part.
ALKT-386 · ALKT-464 · ALKT-528 · ALKT-604 · IT-997
You are eleven of the sixty-two. You did the work. Nobody will count you.
ALKT-331 · ALKT-333 · ALKT-460 · ALKT-471 · +7
Created 10 January 2025. Status: To Do. Some evils cannot be defeated, only outlived — and you have outlived it.
ALKT-196
Removed From the Bag
The evils that lived inside ZenOS before he got to them. All six are dead. None of them are coming back.
Each night, an engineer opens the production database and moves orders between fulfillment centres by hand, following a four-step procedure written down in a ticket.
Minion · slain
ALKT-361
You are visible to every supplier who logs in, regardless of whose purchase order you happen to be.
Minion · slain
ALKT-394
You assume every purchase order starts with “ZF”, and that no other merchant on earth ever had the same idea.
Minion · slain
IT-962
You were announced. You were never shipped. You will sit in “Incoming” forever, and there are thousands of you.
Minion · slain
ALKT-433
Each day DHL reads the Order Overview PDF, observes that the total does not equal the sum of its parts, and declines to pay.
Demon · slain
ALKT-548
You were integrated, never finished, then quietly reimplemented somewhere else. You lingered in the codebase anyway. Removed in a single day, without ceremony.
Demon · slain
IT-1493
The Almanac
Sixty-two tickets is a number, and numbers are the least interesting thing about this. They are also only the tail of it: Jonas joined in September 2022, and the ALKT and IT boards only start carrying his name in January 2025. Eleven of the sixty-two are sub-tasks of his own stories. Six produced no code at all — only an answer, which was usually the expensive part. What the number hides is that three of the systems ZenOS runs on today did not meaningfully exist before he picked them up.
In June 2026 ZenOS had no concept of a freight forwarder. By mid-August it had a role, transport fields on every warehouse receiving, a pickup task workflow, automated notifications to external forwarders, a price confirm-and-reject negotiation, and a Partner API that exposes all of it. He owned the epic IT-1010 and every one of its six children. That is not “worked on a feature” — that is an entire external actor introduced into the inbound process, designed and shipped end to end, by one person, in ten weeks.
Returns runs through his whole time on ZenOS like a spine. Phantom returns that were announced but never shipped, cluttering merchants’ overviews forever — gone. Returns that arrived without a label and were therefore invisible — now visible. Return reasons displayed in English to a warehouse worker in Szczecin — now in Polish, and in German in Aschaffenburg. C-grade items being booked back as A-stock because Storelogix pre-selected nothing — now pre-selected correctly. Store credit as a refund option, so the money stays in the shop. External return providers with a real API endpoint instead of a spreadsheet.
No single one of those is a headline. Together they are the reason the returns side of ZenOS is something merchants tolerate rather than complain about.
The most quietly valuable thing in the list. DHL was rejecting reimbursement claims because the Order Overview PDF attached to Carrier Investigation emails didn’t reconcile — discounts weren’t included, so the total never matched the sum of the line items. Jonas worked out why the PDFs were frequently missing altogether, then rebuilt the price calculation so the numbers hold up to a claims adjuster. Then he added the customer number and the trigger type, and went back to document how the automatic trigger logic actually works so it could be improved.
The evidence is not in the features. It is in what he did when nobody asked. He replaced a fragile ZF-prefix string check with proper warehouse-site resolution before it broke. He folded the last orphan email into the shared builder instead of leaving the duplication. He killed an N+1 feature-fetch loop. He deleted a dead GoRamp integration rather than letting it rot. He replaced a documented, multi-step, hand-written production SQL procedure for moving orders between fulfillment centres with a button.
And when he handed over the unfinished return-matching work, he left spec.md, discovery.md and idea.md in the repository, with decision records and a written warning about which subtask is a safety prerequisite. Most people leave a Slack message.
Still in the Bag
Six tokens remain. Whoever picks them up should read this in order — the first one genuinely matters.
His own ticket calls this “a hard prerequisite for safety rather than for function.” Automatic feedback generation decides restock-or-dispose on the merchant’s behalf once a return is old enough — and under Return Adoption, “old enough” starts measuring from the wrong moment. Do this before enabling Return Adoption for anyone.
Return matching is currently unaccountable: a single candidate is accepted without ever being scored. Specs and decision records are in the repo under .scratch/IT-1262/.
node16 and python3.9 are not getting younger. In progress since February.
Opened four days ago. Step one: restore the BambooHR notifications. Step two: ask other teams what they use. Step three, apparently, is somebody else’s problem now.
Created 10 January 2025. Status: To Do. Nineteen months. This one is not a handover item, it is a family heirloom.
Sourced From GitHub · alaiko-tech
His public profile shows nothing — zero repos, zero followers. Everything below came from the private org he actually shipped into, four years of it, pulled straight from the log.
Good has won. Good is, regrettably, also leaving.
The Storyteller has checked, and there is no clause in the rules that lets us keep a player who has already picked up his token and put on his coat.
Thank you, Jonas — for the freight forwarders, for the Polish return reasons, for making DHL pay their invoices, and for every single time you fixed the thing next to the thing you were asked to fix.
Ships Well · Documents Better
Bonus Token
Four years of clearing them four at a time. Here is one for the road.