What is the smallest polycube whose cavity has two cells, and how many minimal examples are there?
15 cells. Exactly 4320 fixed examples; 180 up to rotation and reflection.
Minimality and census both proven in the campaign-one paper.
The signature page
A question can be original the same way a theorem can. These are mine — with their status, and their answers as they land.
These are free. Steal them. Cite generously.
15 cells. Exactly 4320 fixed examples; 180 up to rotation and reflection.
Minimality and census both proven in the campaign-one paper.
17 cells — and there are exactly 369 minimal examples up to rotation and reflection (718 one-sided, 16,968 fixed).
Census of all 206,155,755 size-16 cavity polycubes: none has two cavities. A targeted search over anchored cavity pairs then found the 17-cell examples — the two sealed cells either diagonally adjacent or collinear at distance two, sharing shell walls — and ruled out every other geometry. The full census at 17 followed: every example verified by flood-fill, and the fixed total confirmed by two independent derivations.
Not monotone: shrinking the cavity you want can strictly raise the price of building it. Realizable exactly when the shape does not enclose a cavity of its own. Growth ranges from Θ(n^(2/3)) for compact shapes to Θ(n) for rods.
The counterexample is exact: remove one face-center cell from a 3×3×3 cavity and the minimum enclosure rises by precisely one. Underneath, f(R) is a Steiner connection problem on the lattice outside R. Known values, each a small theorem: f(cell) = 11, f(domino) = 15, f(2×2 square) = 21, f(tripod) = 22, f(plus-pentomino) = 27. Full writeup is folding into paper two, together with a new sequence: the smallest polycube admitting an n-cell cavity, the 3D analogue of A283056.
Pattern so far: d = 2 gives 7 (classical); d = 3 gives 11, with exactly 384 minimal enclosures — the spanning trees of the octahedron. Conjecture: the minimum is 4d − 1 in every dimension, with the count given by spanning trees of the d-dimensional cross-polytope graph. If true, the cost of hiding emptiness grows linearly in dimension, and the ways to do it minimally are counted by Kirchhoff. Novelty check against the folklore literature in progress.
answered this? send it in →First terms computable from enumeration dumps already generated; candidate new OEIS sequences.
answered this? send it in →Our data: Z8, Z9, Z18 — precisely the exceptional orders of the undirected classification — all fail CI for oriented graphs. If the oriented case differs from the digraph case anywhere, that gap is publishable. Literature check in progress.
answered this? send it in →The adopted column
Standing questions from the literature — flagged in OEIS entries, left open in comments, waiting sometimes for years. I collect them here and chip away. The answered ones keep their receipts.
No — because it is wrong. The true value is 9, and the published table is also wrong at n = 12 and n = 15 (true values 70 and 290). Howroyd's own computation was correct everywhere.
Exhaustive isomorphism classification, verified three independent ways, plus five new terms a(16)–a(20). The wrong values trace to a table in the 2001 source paper. Bonus finding: the cyclic groups of order 8, 9, and 18 — a known exceptional family — fail the Cayley-isomorphism property for oriented graphs.
a(15) = 422,277; a(16) = 4,310,738; a(17) = 41,982,903; a(18) = 395,335,115.
Exhaustive enumeration with a proven pruning threshold, anchored against the known totals of all fixed polycubes at every size.
They were not: a(14) = 76,017 (published 75,917) and a(15) = 838,575 (published 835,491). Plus three new terms through n = 18.
Two independent methods agreed with each other and disagreed with the published values; a full autopsy of the original program then accounted for both deficits to the exact object. The corrections are live and the faulty program was removed.
Recomputable with standard graph-generation tooling. Queued.
answered this? send it in →A sequence that has been wrong twice deserves a third, independent look. Exact-solver verification plan drafted.
answered this? send it in →A live contradiction between two published entries; at least one is wrong. Queued.
answered this? send it in →Needs serious memory to verify; sized for the next hardware step.
answered this? send it in →Testable by exhaustive search at the next several sizes; an elementary proof looks plausible.
answered this? send it in →Closing a published bound is the strongest kind of correction. Exact optimization does it.
answered this? send it in →Needs a genuinely independent algorithm, not another translation. Gardner-adjacent pedigree.
answered this? send it in →Standard graph-generation tooling settles it tier by tier.
answered this? send it in →A machine-checkable certificate of the non-existence half would settle it permanently.
answered this? send it in →Afternoon-scale each. Hand counts have a base rate, and it is not zero.
answered this? send it in →A direct request, publicly posted, unanswered. Our favorite kind.
answered this? send it in →Rebuilding and maintaining the tables makes the maintainer the area's record-keeper.
answered this? send it in →