GlyphWeaver

Reconstructed from published legacy GDSL

See a glyph become
computable.

Each walkthrough starts from a published final GDSL file and restores earlier states by removing later containers, mappings, or relations. The result is one reproducible construction path, not an instrumented interaction log.

Explore 4 original cases 25 reconstructed states · 4 published GDSL files
The paper's blue-flower process: selected petals, inferred repeat parameters, and preview

Figure from the GlyphWeaver paper · pattern inference and live preview

How to read a walkthrough

Four synchronized forms of evidence

  1. 01IntentThe action represented by the reconstructed step.
  2. 02OperationThe corresponding paper-level GDSL operation; legacy aliases appear in parentheses.
  3. 03Legacy GDSLAn executable state derived from the published final file.
  4. 04Render + changeThe rendered output and the declared structural change.

Reconstructed construction walkthrough

Every state is executable and derived from the published final legacy GDSL. The sequence documents one valid construction path; it is not a recorded interaction log.