At least it sort of works after using the best thermal compound available, adding thick feet, and using it only on a cutting board to make sure an uneven surface like my lap doesn't reduce flow. Also, never place the charger on the carpet or it will shut itself off from thermal overload. Everything still randomly overheats with minimal workloads, but mainly it sort of works now :)

The idea is not to solve everything with one simple trick, but to reduce the attack surface as much as possible in hardware. If you are dumb enough to make your 4 messages something like off, on, hard reset, random dangerous maintenance protocol, then it does nothing. If instead it encodes 4 useful and typically used states that can't destroy your system, then you have massively reduced the requirement for onsite, and accepted that more serious issues require onsite control.

1. There are laws already. It is an enforcement problem.

2. The Epstein-type crimes appear to be more prevalent in other branches of government and other parts of society than specifically in the legislative.

3. Enforcement problem is specifically in the executive, of which enforcement is a part.

Other than that, I like to insert agents into deterministic workflows, so some way to easily have deterministic steps (calling a script rather than delegating to an agent, but determined by the workflow rather than the agent). However this second one is likely out of scope for a while, since it is the inverse of the typical agent workflow. I could probably work this out clunkily by polling the cli from an external master script, but it would be cool to have it all inside the box.