I've been thinking about the three layers of software I work across these days: fixed, fluid and JIT software.
Fixed software: dashboards, apps, UIs
Fluid software: skills, packaged instructions
JIT software: chatting with AI to transact with APIs in real time
Concrete example from today. Someone on the team asked "can we send a WhatsApp to all families attending workshop X?"
I asked one of my claws to create a WhatsApp template using the Kapso API, then agree on message and variables, then define the audience (kids age 8-9, signed up for activity X) and finally send a test msg to my number.
solved instance zero of the problem in a conversation. That's JIT software.
An hour later I packaged that conversation into a skill: "whatsapp-broadcast". A reusable set of instructions my claw can execute. That's fluid software.
A few hours later the front desk team needed the same capability. They don't have their own claws with skills _yet_. So I built a screen in the admin dashboard: pick a workshop, write a message, preview, send. That's fixed software.
The flow goes: JIT → fluid → fixed. gas -> liquid -> solid. Every layer coexists. I use all three daily depending on the situation.
