collaborate on diagrams: https://drive.google.com/file/d/1uELuB8yGMp1Xvmu_HttxmUK-au7xq-YM/view?usp=sharing main considerations how will the "lobby" DNA structure change? how will membrane access change? how will the desktop app change? do we want to make the desktop app interoperable with the We applet? How will this affect the current registration flow and architecture? architecture considerations

The following document outlines what I see as the major consideration in integrating ad4m with clutter. I'm also attempting to generalize these considerations as they may be useful patterns for ad4m in general. [ ] encapsulated expression icons [ ] language icon development scaffolding [ ] extend clutter dna to store ad4m expression metadata [ ] allow ad4m executor to use same holochain conductor as nix-shell for enhanced developer experience encapsulated expression Icons I'm currently working on a default icon for mew expressions. The goal here is to create an icon that encapsulates the basic mew interactions (lick, reply, share, mewmew). This way, any ad4m compatible app can recognize the url and replace it with the default icon (thus the mew can be interacted with from Perspect3ve, flux, etc.) As of now, I have a basic Icon.svelte and ConstructorIcon.svelte component (both the reply and mewmew buttons display the ConstructorIcon component).