The previous posts focused on what ACT is — sandboxed components, one binary per transport, capability ceilings. This one is about a thing that was missing: state . Most of the components on actpkg are pure request/response — crypto , encoding , random , time . They don't need a session because every call is independent. But the moment you reach for tools that do — a database connection, an OpenAPI client that has parsed a 5MB spec, an MCP bridge mid-handshake with an upstream server — there's nowhere to put that state. Components held it in thread_local! HashMaps keyed by std:session-id metadata, and the host had no idea what those ids meant or when to clean them up. ACT 0.7 fixes that. Stateful components now opt into a small new WIT interface, act:sessions/session-provider@0.1.0 . The interface is deliberately tiny — three functions — and it changes nothing for the 80% of components that don't need it.…