a gate is the generic slot — the real .mds, protocols and skills go inside it, in the order the agent has to take them
Draw the route an agent has to take before you let it work. Drop gates on the yard, put your real rules inside them, wire them together with a coloured key, then watch an agent walk the whole thing. If a lane dead-ends, forks with no answer, or gets flown over by a bypass, the board says so in red before an agent ever runs it for real.
Two gates sitting side by side are connected, the way two bits of track butted together are connected — you'll see that join as a short dotted stub, so nothing is hidden. Bypass wires still do what they do: reach a gate that isn't next door. During a run, wires sit dim until an agent uses one, then light along their length behind him; he stops on each gate and it pulses as the task lands.
tap a gate to name it and see everything inside it; drag a rule from the drawer onto a gate to add one, drop it on an empty tile to start a new gate. gate colour = yours to set — click the coloured tab on a gate in the shelf to pick from twelve. wire colour = which key it belongs to; there are eight now, so eight agents can share a yard. dot = where a wire enters, arrow = where it leaves, both in that wire's own colour — same colour, different shape, so flow direction can't be misread. dotted stub = two gates touching. drag port to port to wire, drag near pegs to route around things, tap a wired port to undo it, click a wire to remove that one connection, click a gate's × to remove the gate. red means a break in flow — a wire the run never reaches, a fork the agent has to guess at, or a gate a bypass flies straight over; the red line under the yard says which. save writes this exact yard back to this page so it's here next time you open it.
the chips are yours. a chip is a name, a note and a path — and the path is free text on purpose: a file, a folder, a URL, a command, a ticket number, whatever you want the agent pointed at. add one under rules & docs, make your own groups to keep them in, hit edit path to change one later. a gate holds its own copy, so the same rule can point at a different file on a different gate — press … on the row inside a gate to set that. your library is saved with the board and travels inside exported .json.