Which Gate Did You Leave Open — Blast Gates That Move Themselves and Prove They Moved
🤝 Want this built for you? Start a request — our AI scopes it, estimates a price range, and matches you with a vetted AI Advisor. →
Two ways to open it
Unlocks this full walkthrough on your account — no subscription, and no account needed until you check out.
Over 160 project walkthroughs, the 6-week course, and your certificate.
🔒 Secure checkout by Stripe · Already a member? Sign in
What you'll do
A dust-collection sequencer that Claude Code built with you — a Raspberry Pi that notices which tool just came on by reading listed metering plugs over your own network, drives that tool's blast gate open with a 12 V linear actuator, closes the branch that was open before it, and refuses to call any gate open until two independent witnesses agree: the actuator's current trace says the blade ran its full travel and stopped against its end stop, and the duct's static pressure moved in the direction that gate change should have caused. It holds exactly one branch open so the ducts stay above chip-transport velocity, never switches the power of a tool or of the collector, tells you when a tool is cutting with nothing behind it, and when it cannot prove where a blade actually is, it stops guessing, latches into manual mode, and asks you to pull four clevis pins and run your own shop by hand.