MrlyProd

• The MrlyMath crates: the mathematics of designs, and the instruments that measure them.
• Nine crates, one chain: mrlycore <- mrlynum <- mrlymath <- mrlylab <- mrlydemo, with mrlyfig on the laboratory, mrlymusic and mrlyfont on the substrate and mrlygame on both.
• crates/mrlycore the substrate: tensors, atoms, cells, tiles, colors, images, seeded chance, json.
• crates/mrlynum the instruments: primes, divisors, series, recurrences, fft, lattices, networks.
• crates/mrlymath the definitions: design codes, symmetries, counts, names, tiles, automata, renderings.
• crates/mrlylab the laboratory: the sequence press and the moire stacks.
• crates/mrlyfig the figure press: the drawing kit and the square figures the site and the papers open on.
• crates/mrlymusic the sound: waves, notes, timbres, the composer that walks voices through chords, and the wave file.
• crates/mrlyfont the alphabet: the stroked pixel glyphs, the grid a text lays out to, and the stroke-order writing animations.
• crates/mrlygame the content generator: seeded life quests pressed into frames, a heatmap, audio and a manifest.
• research/ the mathematics: one page per idea, every number regenerated by research/lab/, the crates, a paper or the OEIS.
• crates/mrlydemo the eyes: the wasm bridge that hands the designs to a browser.
• site/ the website at mrly.net that draws them; site/README.md says how to run it under bun.
• site/kit/ is the site's own chrome: ssg/ the builder, git/ the code viewer, ui/ the design kit every page wears.
• pkgs/js/mrlyjs/ is reserved for MrlyRs in JavaScript: the wasm bridge, later.
• aws/ is the Lambda that ships the site: net.ts builds on push, s3.ts talks to the bucket.
• cargo test --workspace runs every test; cargo doc --workspace --no-deps --open reads the crates.
• MIT. This is the way. Why is the secret.