Mandelbrot
The Mandelbrot set, rendered from a pixel-grid pipeline.
The wiring ∘ feeds ⊗ parallel
This is the compiler’s reading of how the gifts compose into one app. Read left to right: each stage feeds the next (∘). A bracketed group (⊗) is parallel — its parts don’t depend on each other.
pixel grid- ∘
render
Composition term: render ∘ pixel-grid
2 declared gaps — named below, not hidden.
constructible-with-gaps: 2 pipe primitives fully witnessed (grid-source, ppm-raster); 2 declared pure-kernel gaps (color-map, escape-iter) — the fractal compute core is honest derive-first work. One interactive sub-lane (pan-zoom / input-handling). Judgment call resolved: mb.pixel-grid witnessed by grid-source (the shared grid substrate, same as spreadsheet).
The declared gaps 2
A gap is a piece the compiler knows it needs but doesn’t yet have a witnessed gift for — honest derive-first work, declared rather than hidden. The app is constructible; these are the parts you’d build.
-
mb.color-mappure-kernelescape-count -> RGB: a deterministic per-record map, a pure fold. Reclassified pipe->pure-kernel by the S13.1752 D1 ruling (drift 8251ecec). Declared derive-first gap; a color-map-transform witness gift (path b) is open gifts-8-reference-apps work — the oracle's own hint flagged it a gap candidate.
-
mb.escape-iterpure-kernelper-pixel escape-time iteration z=z^2+c: the deterministic fractal-core fold. Already pure-kernel in the oracle; declared derive-first gap (null-witness).
Witness gifts 2
These shipped gifts witness stages of the pipeline — the real, downloadable parts the proof stands on.
The gifts are real and free; the wiring is a plan. Take the parts and build the app — as the schematic reads it, a variation, or something we’d never have compiled.
Built it, found a gap we missed, or think the wiring is wrong? Shea wants to hear it — success stories, questions, and corrections all land in the same inbox: