File one clerk packet, then build a stakeholder path.
The clerk mixed official packet cards with hallway rumors. Use only cards stamped Clerk Packet. Sort those room numbers lowest to highest, read the first letter of each desk word, then append the checksum: add the final digit of each sorted Clerk Packet room and keep the last digit. Add one routing note explaining why the rumor cards do not count.
Everything needed for this puzzle is on this screen. Start with each card's stamp, not its desk word. The clerk rewards a clean process before a clever guess.
Tap a card to file it. Tap a filed card or a tray token to remove it, then file it again in the order you want.
The competition has ended, but the policy challenge is still live. Clear the Front Desk, earn time with staff, map trusted messengers, and make a case the office can act on. New captures are saved without changing the final 2026 standings. Thank you to everyone who played at Policy @ DEF CON.
See the 2026 honor rollU.S. House · Energy & Commerce Committee
Staff reviews meeting requests for a local reason, credible attendees, a practical answer to cost concerns, and one specific action the office can take.
Hartwick listens hardest when employers and workers show up together with a workable implementation path.
Staff favors meetings that include a constituent story plus a local validator who can confirm the problem.
District asks land better when they respect the port, logistics, schools, refinery, credit, and small-business economy.
Write like a constituent: name the local problem, who can verify it, and one practical first step. Give scheduling a request it can route without rewriting.
In this CTV scenario, H.R. 4892 is an AI accountability bill about high-stakes automated decisions. It asks when people deserve notice, explanation, and a human review path if software substantially influences a consequential outcome.