The six redstone wire rules nobody reasons their way to

Redstone looks like logic gates, so the instinct is to reason about it like a circuit diagram: signal goes in here, comes out there, so the lamp lights. That instinct is wrong often enough to be dangerous, and it is wrong in specific, repeatable ways. It is also where large language models fail at Minecraft redstone. On the SciCraft-Bench benchmark every frontier model tested plateaus near 26%, and the dominant failure class is wire semantics rather than anything conceptually harder. Cubelings does not ask a model to derive wiring live. It places verified circuits from a library, and the library is built on these six rules.

1. 1Build order is load-bearing

   Placing a block with setblock does not make an already-placed neighbour re-check its redstone state. Put a lamp down next to a live power source and it stays dark, because nothing told it to check. Place the power source last and the lamp lights, because that placement is what triggers the update. The fix is no cleverer than that: place power after everything else, every time.

2. 2A repeater's facing points at its input

   A signal travelling west to east needs a repeater facing west, pointed back at where the signal comes from. It is the easiest thing in redstone to get backwards, because every instinct about "facing" reads it the other way round.

   SignalWE

   FacingWE

3. 3Dust only powers the block it points into

   Redstone dust powers the block at the end of its run. A block that merely sits beside the dust is not powered by it, even though in the world it looks connected.

4. 4Dust needs a solid block under every cell

   Dust on air breaks the circuit silently. There is no error and nothing different to see. The run stops carrying signal at that cell, and the only way to notice is that whatever it was meant to drive never turns on.

5. 5A repeater cannot turn a corner

   A repeater only passes signal in a straight line. On a corner its input side faces where the wire is not, so it cannot legally sit there at all. That matters for anything circular, because a rasterised circle is almost entirely corners. On a radius-14 ring, one stretch came out as 19 consecutive cells with no straight run anywhere in it, so no repeater could go there and the dust decayed to nothing partway round. A ring built from a square with its corners cut off keeps long straight runs where repeaters can live.

6. 6A closed loop of repeaters latches itself on

   Wire a ring of repeaters back round to its own start and it no longer needs an external signal to stay lit. A stray pulse during construction circulates back into itself and holds the whole ring powered, lever or no lever. One version of a chase-ring build left a single missing cell as the gap, on the assumption that one cell was enough separation. It was not. A feed assembly built into that gap bridged it, and 26 of 111 cells stayed powered with the lever off. The gap has to be wide enough that nothing built near it can close the loop by accident.

Why the answer is a library

None of the six is exotic on its own. What makes redstone hard to get right by reasoning is that a working circuit has to satisfy all six at once, and a single violation anywhere in a hundred-cell ring fails silently. There is no error message, just a lamp that never lights or a ring that never turns off. Leftovers count too. One build kept 17 of 109 cells lit with the lever off, because a forgotten observer clock from an earlier build was still on the site and feeding the new circuit power it was never meant to have. The fix every time was the same: check the circuit against the world after building it, instead of trusting the wiring plan.

where frontier models plateau on SciCraft-Bench

~26%

corner cells in a row on a radius-14 ring

19

cells stuck on with a one-cell gap

26/111

cells held on by a leftover clock

17/109

Verification explains how that check works, and Capabilities has the full skill list.