We ship in units, not sprints.
Voxel Stack is the internal build log of Kettleworks — four platform towers, twenty-two layers, each one stacked only after the layer beneath it holds weight.
02u
The Yard
Select any block to read its layer note. Height is literal: one unit up means one dependency satisfied.
RUNTIME07u · tallest
LEDGER04u · frozen
EDGE06u · building
Runtime tower · unit 07
Canary Gate
The tallest block we have shipped. Holds a release at one percent until four independent signals agree it is boring.
04u
Layer notes
Four blocks the crew argued about hardest this cycle, written up in plain language.
Schema Guard
We used to accept anything and repair it downstream. Three incidents later the rule is simple: if the shape is not declared, the payload does not enter the tower.
Scheduler
Bin-packing by memory shape reads as a small change and behaves like a large one. Idle footprint fell 34% and the graph has stayed flat since.
Merkle Index
Publishing hourly root hashes to a mirror we do not control was uncomfortable, which is exactly the point. Verification should not require our goodwill.
Client SDK
Nine kilobytes took four rewrites. Every feature request now has to justify a byte budget, and most of them quietly withdraw.
06u
Build manifest
Every tower, its ceiling height, and what we are permitted to stack next cycle.
| Tower | Height | Ceiling | Owner | Next unit | State |
|---|---|---|---|---|---|
| Ingest | 05u | 08u | Pipeline guild | Replay Buffer | Live |
| Runtime | 07u | 08u | Runtime crew | Region Pinning | Building |
| Ledger | 04u | 04u | Finance eng | — | Frozen |
| Edge | 06u | 09u | Edge squad | Origin Shield | Building |
08u
Colophon
Voxel Stack is written by the Kettleworks platform group and published at the close of every build cycle. We keep it in units because units are honest: a tower is only as tall as the last block that held.
Set in the system UI stack with a monospace counterpoint. Every block on this page is drawn with clip-paths — no images, no libraries, no 3D engine.