rind / ops

the production weave

Six white-collar ops surfaces woven over eight production engines — the complete bipartite graph K(6,8), realised as a real weave (not the abandoned gyroid). Every white surface reaches every engine; the whole thing lives in the rind's Voronoi foam in 2–3 walkable floors. These are the views, newest first.

the answer — one door

⌸one doorproof · 3D

The hard requirement made true and proven: any point in the chunk to any other passes through only one door — including the two central hubs. The walkable space collapses to two door-free concourses — the 6 arms + the nave hub , the 8 arms + the bottom hub — joined only by the 48 zero-grade K(6,8) doors . Route any two rooms live; colour by concourse or all 14 threads; solid or ghost. Two substrates: an HCP lattice claimed by flood, or nuclei seeded on the analytic curves then grown to fill (full K=48, every door at grade).

rind.mino.mobi/ops/onedoor.html

walk it — the navigator

▤your thread — an officev100 · walk

The right engine for this map: the map is only what's reachable from your thread. Your thread renders in full as an office of rooms (the v100 foam partition — role rooms + a hallway spine), and every other thread is only a door in your wall — not a standing room. Cross a door and that thread becomes your office, re-centred; the one you left is a door behind you. The nexus opens onto all sibling offices. K(6,8) made first-person: a white office has 8 doors, a production office 6. Proven (office.selftest.mjs).

rind.mino.mobi/ops/office.html
▦the demo floor — god-viewv100 · walk

The counterpoint: all threads standing at once. The v100 foam engine grows a district of rooms + a concourse in every hex chunk, tiled into a honeycomb (7/19), abutting at seam doors, corners forced into nexus mixing points. Walk 300+ rooms across one connected floor — the whole tessellation inhabited simultaneously (vs the office's thread-at-a-time view). Proven navigable (floor.selftest.mjs).

/ops/floor.html
@inhabit a threadproto · walk

Navigation is mapping. You are the @, standing in one thread — its own chambers strung along its curve into one walkable surface, walled but for its doors and the nexus. Start at the white nexus, pick an arm, walk it out toward the rim past the doors where it crosses each production line — cross a door and the whole map becomes the new thread's, re-centred on the crossing (and spiralling the other way). The one-door structure, made first-person.

/ops/nexus.html
◇the pocket dimensionv101 · walk

The weave walked at nave scale: each thread becomes a full pocket floor (the v101-skinned rooms-and-concourse engine), doors at the analytic stations in true-arc order, over/under on the north/south wall. The metric is faked, the topology is exact — cross a door and you're on the reciprocal station of the other thread. Streamed segment by segment; the analytic map (office) stays the truth.

/ops/pocket.html
🌀upperrind — the ring topology, walkednew · walk

The pocket, re-posed as the ring topology: 6 white ops above × 6 engines below (K 6,6), joined by two walkable ring loops — assembly (inner, bonded to the fulfillment nexus) and reclaim (outer, at the rim), each touching all 12 threads and closing into a loop you walk round. Every floor keeps its flavour: white threads are verb-hued solenoids (flux bending round shielded chambers), the six engine floors are machine halls (bays wired by conveyors), the rings + nexus their own hues. Kernels node-tested (ringpocket · fluxfield · machinehall).

rind.mino.mobi/upperrind/
⚖the works — production solverecon · solved

The map supposes the material flows; this solves them (the hoop/econ + forge lineage). A product setpoint is back-propagated to every engine's run-rate; two populations — logistics bots and the six white-collar ops — gate the throughput. Live oracle: per-engine load, material closure (the water leak), the binding keystone, a vitality tier. Quantifies why assembly & reclaim want to be rings. Node-tested (econ.selftest.mjs).

rind.mino.mobi/upperrind/econ.html
⬡the ring weave — 2D + 3Danalytic · over/under

The solver's ring hypothesis, drawn. A re-posed analytic weave: 6 white ops above × 6 engines below (K 6,6), with reclaim as an outer ring and assembly as an inner ring — each touching all 12 threads — bonded to the fulfillment nexus. The 3D view (spin it) lifts it into z with real over/under parity: every crossing is a zero-grade flat, and the 60 antechambers (36 K + 24 ring) sit proposed on the z=0 mid-plane — no ladders. Flat 2D schematic too. Node-tested (ringweave · ringweave3d).

rind.mino.mobi/upperrind/rings3d.html

tessellate it — the infinite world

⬡the tessellating weave, solvedproof · 2D

The real answer to how does the world go infinite. Honeycomb the single hex and solve what happens to its 14 threads where tile A's edge meets tile B's. Two halves, computed from the real Voronoi weave and proven (tessweave.selftest.mjs): the 6 whites form an exact 1-per-edge bijection that translation-tiling turns into 3 global strand families (one ring + two helices — the emergence, over the real weave); the 8 engines can't divide the hex's 6-fold symmetry, so they stay local and supply the cross-kind K-doors that reach across every seam. Trace a family across the tiles; watch the interface census live.

/ops/tessweave.html

the weave in space

◍orbit — the woven shell3D

The primary 3D read: 6 white + 8 production counter-rotating spirals in a volumetric Voronoi pancake. Orbit the shell, inhabit a thread to unroll the map from its point of view, or explode the museum map and route through doors and stairs.

/ops/orbit.html
⬡lay the weave (on the prism)3D

The substrate rebuild: 6+8 tubes claim a hexagonal prism of homogeneous HCP nodes. Push the levers — width, areal density, decks, thread counts, flat core — and watch continuity, K(6,8) and the over/under weave break and resolve. True 3D Voronoi chambers, packed solid.

/ops/prism.html
⬢tessellation2D

How one hex weave-cell tiles the rind shell: a hexagon has 6 neighbours and the cortex has 6 white arms, so each arm hands off to one neighbour (the white weave is the connective tissue; the 8 engines stay local). Aperture-7 self-similar, H3-style.

/ops/tess.html
✺the helix emerges2D / cylinder

Local hexes, global helix. Chain the white edge-handoffs across the wrapped honeycomb and the six directions resolve into three families — azimuthal rings and two counter-rotating helices — the cylinder weave, emergent. Unroll it or wrap it onto the tube; trace one strand and watch it spiral. Expansion = more rows of hexes.

/ops/helix.html

the 2D lineage & proofs

▦flat polar rosette2D

The original polar spiral weave: 6 white & 8 production spiral out from two disconnected hubs, woven across two floors over a 19-chunk hex region. Where the K(6,8) idea first became a picture.

/ops/flat.html
🧵the loomproof

The K(6,8) plaid as a woven-tube proof — warp × weft, every white crosses every production exactly once, over-under by plain-weave parity. The kernel the whole apparatus is built on.

/ops/weave.html
▤region decks2D · legacy

An earlier region-decks comparison with a live material-flow schematic of the 8 engines — the wrong metaphor (stacked decks + a link-star), kept for contrast with the weave.

/ops/decks.html
The theory — the diagnosis of the gyroid, the reframe to K(6,8), the plain weave, the one-door resolution and the two substrates — is written up in WEAVE.md. rind is the structure wing of the O'Neill cylinder package · back to rind.