Put voltage on the gate and current flows. Hold the gate open and the memory survives. Nothing passes a gate it hasn't earned. This is where the tools get built.
Three fields use the same word for the same idea: a control point that decides whether anything gets through. The name isn't a metaphor borrowed from architecture. It's the engineering term.
A MOSFET's gate is the control terminal. Below threshold there is no channel and nothing moves. Cross it and a conducting path forms between source and drain — the gate decides whether current exists. Every logic gate above it inherits that: a gate is not a wall, it's a condition.
VGS > Vth → channel formsLSTM and GRU cells are built from gates — sigmoid values between zero and one, multiplied against the signal. Hold the forget gate near open and the state persists across time; let it close and the memory is gone. Gating is what made long-range memory possible. The same word still sits inside every modern model: gate_proj, in the feed-forward block of nearly every open-weight LLM shipping today.
A quality gate in a pipeline, an admission controller at a cluster boundary, a barrier that holds every thread until the count reaches zero. Each is one rule: the thing on the other side has to satisfy the condition or it does not go through. That rule ran a factory long before it ran a build server.
gate passed → ship · else → holdThe interesting part is that only two of the three are binary. A quality gate is pass or fail. A transistor is on or off. But a neural gate is never all the way open — it's a value between zero and one, deciding how much gets through. Both are true, and running anything real means knowing which kind of gate you're standing at.
openg8.com is the short form · the name is OPEN GATEAn 8 built from two identical diamonds, drawn on a single 45° grid. The lower bowl is left open — a circuit that doesn’t close. A short leg springs from the break at ninety degrees to the diagonal, which puts it parallel to the edge beneath it and turns the whole figure into a G without ever spelling one. Four paths. No curves, no exceptions.
Not a philosophy. A measurement. Name what should be happening, measure what actually is, and the gap tells you what to build. It scales from a welding bay to a codebase.
It leaves right or it does not leave. That's a non-negotiable.
Words carry meaning. Avoid slang — say the thing you actually mean.
Never hand over a problem without the correction attached.
Don't wait for a step-two method. Start crude, then digitize.
Tools are worth paying for personally. Leverage doesn't wait for a budget cycle.
Scroll to fly the corridor — nine shipped systems, then each one in detail below. Built without a framework or a build step where the job allowed it: static HTML, CSS, vanilla JS, PHP APIs, SQLite. Boring on purpose. Boring survives.
CAD tooling · browser-native decoder
A legacy CAD format nobody supports anymore, read directly in a browser. Drop in a .prt file and it decodes the geometry, renders the drawing as real vectors, and exports DXF or SVG — no seat license, no install, no vendor still in business.
Fleet software · route intelligence
A dispatch and route command center for refuse fleets: stops remaining, delayed routes, containers out, scale tickets, telematics, and a request queue that tells a dispatcher what needs a decision right now. Built to answer one question on open — what is actually happening today.
Client site · shipped & live
A full marketing site for a paying client outside the truck world — brand, copy, photography, service pages, and a self-hosted PHP inquiry handler after the third-party form service failed once too often. Own the pipe.
SaaS · service management
The operations layer behind the client site: route scheduling, service records, chemical logs, and a customer portal, plus a native iOS companion for the tech in the field. Gated by design — the screen most people should ever see is the one above.
Website refresh · demo build
A ground-up redesign demo for a Central Coast waste hauler — roughly three hundred routes rebuilt as static pages, a client-side search index, a translation layer, an accessibility layer, and Python tooling to generate and audit the whole thing. Built to answer whether a regional hauler's site can be fast, findable, and accessible without a CMS underneath it.
Independent venture
Independent refuse equipment guidance — route profile first, configuration second, quote last. Thirty years of category experience pointed at the question a brochure page can't answer: which truck actually fits this route.
Drive the route. Grab the cart, lift, dump, and try not to miss one. A playable 3D collection sim that runs in a browser with no install and no plugin — mobile controls, on-screen arm functions, scoring, and a photorealistic-tiles build that drops the truck into a real city. It shipped as the kids' section of a hauler's website, which is the only design review that has ever really mattered.
Axle loading, bridge formula, and state regulation reference in one page, cross-referenced against three hundred and four real chassis and body drawings and fifty-six extracted configurations. One HTML file. No install, no license, no server.
A century of family records compiled into something that will still open in thirty years. A GEDCOM file and a manuscript go in; out comes a fully static, searchable archive — a page per person, a client-side search index, and a validation pass that flagged and suppressed four hundred and thirty-five relationship links whose timelines couldn't be true. No database, no service to go dark. The same instinct as the rest of this page, pointed at people instead of trucks.
A personal operating layer, not a chatbot. AIMEE indexes the corpus, watches the workstreams, drafts the reply, and routes each task to whichever model is actually best at it — measuring its own backends and demoting the slow ones. Every send and every write stays approval-gated. And it has a judgment layer: fifty-two scenario interviews encoding how decisions get made, so the machine decides the way I'd decide when I'm not in the room. No screenshot here — it's a native app, not a web page.
Three more are client-facing and credentialed. They aren't linked and they aren't shown in detail — that's the whole point of a gate.
Quote & spec configurator over a live library of engineering documents.
Build stage, dwell time, and projected ship for every unit on the floor.
Twenty years of buying history and source documents behind one search box.
One page, no dependencies, no build step. Tokens at the top, components below, everything drawn from the same variables. Fork it, retheme it in one block, ship the next app by Friday.
Illustrative values · tile, delta, and sparkline are the reusable parts
| Unit | Program | Stage | Progress | Dwell | Status |
|---|---|---|---|---|---|
| A2026-0418 | Front Loader 40yd | Final assembly | 4 d | On plan | |
| A2026-0421 | Roll-Off Hoist | Paint | 7 d | Chassis late | |
| A2026-0427 | Automated Side Loader | Weld-up | 2 d | In build | |
| A2026-0433 | Rear Loader 25yd | Pre-delivery | 9 d | Ready | |
| A2026-0440 | Manual Side Loader | Awaiting chassis | — | Hold |
Sample data · status pills, inline progress bars, tabular numerals
#04060a#0b0f18#101622#52e0d4#ff9d4d#e9eef7#6b7889#ff5f6d--t-heroOpen--t-xlSection heading--t-lgCard heading--t-md / 1.65Body copy — the reading size--t-xs monoLABEL · META · EYEBROWRetheme = edit one :root block
What's open is open. The credentialed workspaces on this domain aren't listed here and won't be — a gate you can see the handle on isn't much of a gate.
Brand, site, and self-hosted inquiry handling. Live.
Route profile first, configuration second, quote last.
Questions about any of the work above, or access to a private workspace.