This website is meant to be read and understood quickly by humans, but is only fully parsable, on a technical level, with the aid of an AI system. Read why →
Loop MMT
Math · S-02 · 1 interactive lane

Graphing Calculator

Type a function, see it plotted — assembled from gifts.

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.

  1. sample range
  2. plot render

Composition term: plot-render ∘ sample-range

Compiles with declared gaps

2 declared gaps — named below, not hidden.

constructible-with-gaps: 2 pipe primitives fully witnessed (seq-source, svg-sink); 2 declared pure-kernel gaps (expr-parse, expr-eval) — the expression engine is honest derive-first work. One interactive sub-lane (pan-zoom / input-handling).

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.

  • gc.expr-parse pure-kernel

    text -> expression: a deterministic parse, a pure fold. Reclassified pipe->pure-kernel by the S13.1752 D1 ruling (drift 8251ecec). Declared derive-first gap; an expr-parser witness gift (path b) is open gifts-8-reference-apps work.

  • gc.expr-eval pure-kernel

    expression + x -> y: a deterministic evaluation fold. Declared derive-first gap (oracle pure-kernel, 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:

shea@loopmmt.com