NWKS Encounter: Nobody Retypes Anything

The design rule this engagement was decided by is written into its own documents and quoted back across four of them: the design that means nobody retypes anything wins. Every part of what follows is an instance of it.

The public side is one page. Registration opens at an instant the ministry sets in advance and flips on its own with no network call at that moment, because an Encounter fills and the ministry announces a time. Before the announced minute there is no form at all, not a disabled one and not a notice. After it, the same form quietly re-points at a waitlist when the weekend is full, so a person who arrives late joins a queue with their details already captured. When a seat is released the next person is emailed an offer with a day to take it, and the seat is held by an unresolved outcome rather than by a clock, claimed by a compare-and-swap so two people cannot accept the same bed. Viewing the offer changes nothing and only a deliberate action accepts it, so an email scanner opening the link on somebody's behalf cannot take a seat for them.

The cabins are drafted rather than arranged. A weighted planner works the whole board against seven ranked objectives, the two heaviest being that a town's men are not placed on a side with none of that town's servers, and that a man lands in the same cabin as the server who invited him. It is tuned to produce a defensible first draft of roughly 144 bed assignments, so two volunteers can correct it by hand in an evening and hand the result to the printer with nobody retyping a name. A bed set by hand is locked and a rerun never moves it. The weighting itself was argued down once, from a level where one rule had stopped being a weight and had become a hard constraint wearing a number, and the test that pins the order of those objectives caught the first replacement value for being a different instruction rather than a gentler one.

The weekend's volunteer teams are drafted from the ministry's own history: 684 team placements across fourteen Encounters between 2015 and 2026, plus twenty of their schedule workbooks, turned into eleven measured rules. Nothing in it is a preference somebody typed in, and deliberately no rule names a team, so the women's Encounter is entitled to a different answer to the same question out of its own sheets. The most useful thing it does is refuse: handed a programme it has no history for, it declines to draft at all and says so, on the reasoning that with no past sheets there is nothing on offer but a guess with a confident interface. Once a sheet exists the system also reads it backwards, running eight checks against a decade of practice, including the one nobody could do by eye: spotting that a man who has captained the same team for years has been quietly re-registered under a misspelling of his own surname and placed among the first-timers. That check is deliberately built to share no code with the engine that drafts, so it can catch that engine's own drift.

Then the paper, which is where the retyping actually ended. Three print jobs and four workbook profiles produce the badges, luggage tags and rosters, all written from scratch with no dependencies and drawn at absolute coordinates into a PDF rather than handed to a browser's print dialog, because a correctly registered sheet of label stock should not depend on somebody setting margins, scale and headers right in whatever browser they are in front of at midnight the night before the Encounter. The cheapest win shipped before the generator even existed: an export shaped exactly the way the label importer expects, which retired the hand-typing outright. And nothing is blocked by one unresolved person, because the tags that can be made get made and the person who could not be placed is named on an exception page instead. The paper reports its own gap.

The security answer is the one the ministry asked for. Passwords are scrypt, sessions are opaque and server-held, there are three roles on a default-deny allowlist so a route added next month is refused to reviewers until someone opens it on purpose, and every administrative action is written to an audit trail where a refusal is logged rather than quietly returning an empty list. Most of all the two ministries cannot reach each other's records. That is enforced by the database itself, 127 triggers of which 113 are that separation, because the leak that actually happened did not come through a route: an import script wrote straight to the database and put eighteen men's registrations under an invented women's event, where they surfaced in the women's administrators' panel. A route can be forgotten and a trigger cannot, and a standing test now fails the build if a new table is added without one.