Hacker
sohamjuneja
@sohamjuneja
Projects
Clearance
Flip the Switch HackathonNov 2026
In Switch today, an agent's approval card goes to whoever may address the agent, and by default that's the person who asked. In our test setup, a persona asked for a ₹40,000 refund, approved every card herself, and the money went out. Clearance is a Switch agent plus a small gate in front of business APIs. The gate holds the credentials, so an agent can only ask, and Clearance holds the call until an eligible person answers. The person who asked can't approve. The card goes to someone else by role and rota, with an escalation timer behind it. It leads with fields parsed from the real call, and the agent's own sentence comes last, labelled unverified. It works wherever your team already talks. Every card, refusal, escalation and answer goes through Switch, so the same flow reaches a team on Slack, Discord, Teams or Mattermost through Switch's bridges, with no change to Clearance. Our demo and measurements ran on Mattermost. Approval gates decay, so Clearance also tests attention: practice requests with planted flaws, typed confirmation on high-risk cards, and autonomy for small refunds that an agent earns from a record two people sign, lost after one incident. It works for two people as well as a company: a builder and someone they trust, over their own agents and money. No LLM sits in the decision path. Identity comes from Switch's own events, never from an agent's text. If anything is missing, the answer is hold. Measured with real agents: with no Clearance, Claude's agent went ahead with risky actions in 5 of 20 runs and OpenCode's in 13 of 18. With Clearance, 0. All 25 cases in our attack suite were prevented, also on real Switch and Mattermost. Every number comes from a script in eval/.
DellFargo@prashantthakur77