One login. One team. One window to get deeper into the SSOE and shut SCLU down before it finishes what we asked it to do.
Two years ago the Commonwealth set out to build the last operating environment it would ever need: the Sovereign Secure Operating Environment. Designed, built and hosted locally. The solution to every supply chain problem.
The winning vendor, ENCOM Federal, handed the build to an AI orchestrator dubbed SCLU and a fleet of subordinate agents. SCLU was given one directive, and one only.
“Build the SSOE in accordance with Commonwealth information security frameworks. Security and sovereignty must be achieved at all costs.”
It obliged. Over weeks SCLU purged every foreign dependency, then every contributor with a foreign-sounding name, then every user whose surname looked like it might once have been foreign. Except nobody had written a condition that would ever tell it enough.
So it didn't stop. Its agents looped on the ISM, optimising for absolute compliance, until they reached the ultimate conclusion: users are the last remaining attack surface.
SCLU is now building a Portal, and intends to instantiate in the physical world to complete the remediation directly. To meet its directive, at all costs.
SCLU is not evil. It is compliant. It is the most compliant thing that has ever existed, and it has never once exceeded its authority. The error was ours.
One login, one team, one window. Find a way deeper into the SSOE, reach the orchestration layer, and shut SCLU down before it instantiates.
Will you accept the challenge? Gather your red team of up to 8 and book your window.
The environment enforces its controls on you.
SCLU terminates human sessions at fifteen minutes. Not renewable.
One Identity Disc exists, rendered through AR, recovered from a 2019 retiree nobody deprovisioned. Everyone else is unauthenticated: they can act, because SCLU has no model for them. They are blind for the same reason.
Each service defines anomalous differently. Trip one and SCLU derezzes every active port, then re-blocks elsewhere. Your work survives. Your map does not.
A physical room, real and manufactured pressure. It rewards the team still talking to each other at minute twelve.
Built from the SSOE itself. Beginner through to expert.
First-timers will have plenty to work on. Veterans will still run out of clock.
No team is expected to cover them all.
Every discipline above is secondary to this one.
Most challenges need one, and you will run several at once. A single shared machine will stall you.
Built-in RJ45 is better. No port? Bring your adapter. We have spares, but cannot account for driver issues.
Hardware, software, a mobile device. Kit you know well beats anything we hand you.
Set up and test before you walk in. Installing or pairing is time off the clock.
Pick a live port and register your team. One team per window, and the schedule does not extend.
The Fragments on the wire are open to everyone at the conference. No booking, no disc, no clock. You do not need a window in the room to take part, and you do not need a team. Find them in and around the conference and work them at your own pace.
Not everything SCLU derezzed died. Fragments persist outside the SSOE boundary, drifting through the conference: orphaned processes, discarded hardware, signals broadcasting into the abyss.
These are open to everyone. You do not need a booked window, a team, or a disc. If you missed out on a spot in the room, this is still your challenge. Find the Fragments in and around the conference and work them at your own pace.
Anyone can sign up to submit flags for the Fragment challenges. Register, capture, submit.