I think there would be value in some sort of DAO focus group informally having a think about what theyād like to see. This is more for prospective applicants than the delegates. It could also coincide with some marketing of the program across platforms (X for example) to try and get more teams involved in the ecosystem.
Delegates can vote how they choose of course, and (as I see it) the program would still welcome novel ideas outside of the list of āthings we would like to seeā.
As with everything in life, this is a trade-off. The DAO should (of course) be financially prudent but itās a balancing act. If the DAO wantās teams to think outside the box, and develop novel solutions to as-yet unknown problems there needs to be some level of flexibility.
Is the implication here that some Service Providers in the first year didnāt deliver? In principle the original terms gave the DAO powers to stop streams, but again it requires human bandwidth - a resource that is in limited supply.
This comes full circle to my original point, namely that the program needs clarity on what it intends to achieve. Objective clarity. If that is literal āservice provisionā - āthe DAO wants this, who will do it, and for how muchā, well defined KPIs make much more sense.
No. it couldnāt and shouldnāt (IMO) be.