Morning 10 minute freewrite scrawl. I want to return to the timer concept today. Build out the frontend with the iframe portals. Reduce data scope down to just startTime, duration, and label (leave calendar time blocks for later). I think the shuffle mechanism will be the real small proof of what shared data/structure could do for generated apps.

Remembered walking today that the two pieces should be separate - timer is in charge of displaying the apps but the iframe links could go anywhere. I'll probably have a convenience repo to start with. I wonder how much focus I should put on getting a live react playground working with it - I wonder if I could use one of the LLM canvas playgrounds to actually run it - with the share link - though how stable are those share links really?

Some of my recent work experience from submissions should come in handy - it's always surprising how the most mundane projects have a way of working themselves back in.

Ideas-wise also really curious about this guide to living structures by Ken Isaacs that was referenced on Merveilles. Have to get my printer connection on this laptop working and then I'll print it out.

Some of his other work reminded me about discussions about transparency layers. Think I should get some of those again - will also be useful for planning out tattoos.

I also had the related idea for a drawing/image editing app where each layer is an iframe. This follows up the work I'm doing with scrape. The worry with scrape is just that the layer business is overwhelming the scrape effect which is my main focus. Not the first time that's happened so of course I'm looking for a place to modularize or generalize it. Reminds me again of 'carving at the joints'. I want to do a better job of remembering key touchstone phrases - I should add carving at the joints to the quote page. It might be the one I think of most.

That got me thinking about the connection between frames and layers. Based partly on my other work on frame trying to isolate GIF and video frames. I can't tell if I have too many unfinished constraint systems projects right now or it's just the natural mess of working things out.

I really like combining - or playing with combining - frames and layers. Frames are time based, or sequential based? Layers have an order too. Playing between the two a practical problem is there's often probably just too many frames - if I explode them all there's going to be too little difference between them and too many to run. But FPS would be the natural solve for that right? Maybe even playing with the idea of keyframes.