a website, and the operating system behind it

Worksop Workspace is a coworking space in Worksop, Nottinghamshire: desks, private hire event space, and the day-to-day machinery that keeps a shared building running. Who's allowed in, what's booked, who's on shift, who showed up to last night's event.

The public website is the front door. wwOS is the product the business actually runs on every day, and it's the part this case study is mostly about.

wwOS already existed as a working prototype when nura got involved. Rather than start rebuilding against assumptions, the first project was an audit, WWS-AUD-P01, that produced the evidence base every later decision was built on: what worked, what was fragile, and what was missing entirely.

The rebuild runs as a single parent programme, WWS-OPS-P01, with each part of the system split into its own child project, each with its own PLAN, DESIGN, and BUILD, gated by explicit acceptance criteria before it ships. Identity and access, member management, bookings, payments, staff tools, day-to-day operations, embedded documents, building integrations, and lobby displays.

A single STATUS document sits above all of it, living, dated, and honest about what's shipped, what's broken, and what's deferred. That's the document this page is drawn from.

Every attendee of a private hire is now known before the event and admitted by name on the night. There are three routes in and no fourth: a registration link the organiser sends out, a pass staff scan at the door, or the door list staff admit from directly. Anyone unregistered has no pass and no row, so the only way through is a staff member adding them there and then, recorded against their own user id.

The daily automated sign-out was scheduled to run at a fixed UTC time. During British Summer Time that meant it would fire an hour and a half into an evening event, signing out every attendee of a hire still running and leaving the fire roll call reporting an empty building while forty people were actually inside it.

It's fixed: the sweep now skips anyone whose booking is still active, and a later sweep closes out whatever it deliberately left open. A governed, gated process caught this before it reached a live event, not after.

wwOS is being rebuilt in the open, one governed subsystem at a time. We're not publishing a "before and after" here, because the programme isn't finished, and pretending otherwise would break the same standard this page is describing.