Resolves if the model could reasonably described as being released in 2023. Feel free to posit grey area release scenarios and we can reach a consensus.
List of events qualify to resolve this market YES:
Released to the public
Open Beta
Paid but otherwire open service
Leaked weights that have been packaged to be usable by laymen
Renamed to something else (in name only) but released
Closed Beta with proof of >=10,000 users
List of events that do not qualify to resolve this market YES:
Leaked weights that are useless
Closed Beta with no proof of user numbers
Closed Beta with <10,000 users
Limited researcher only release
List of events that immediately resolve this market NO:
Project renamed and takes vastly different direction
Project cancelled
Not released by 2024
Model explicitly permanently not released due to risks
Also:
/cloudfront-us-east-2.images.arcpublishing.com/reuters/KE6JJYSFBVLEFIKRQF7HJ2FQ5A.jpg)
It seems to me that these two could happen in order:
List of events that immediately resolve this market NO:
Model explicitly permanently not released due to risks
Followed by:
Leaked weights that have been packaged to be usable by laymen
Does the market in fact resolve No and stay that way if that happens?
@EvanDaniel rules as written, yeah you'd be correct there. Looking back I'd probably have the "explicitly permanently not released due to risks" not be in the immediate NO category, but I wanted a way to resolve early if they killed the project, and don't think I should change it now.
@brubsby Thanks! I'm supportive of not changing things unless there are major problems, just wanted to check that I was reading it correctly.
@jacksonpolack fair, I'm kind of two minds about the specific criterion though. I think maybe it should resolve NO before getting leaked in that case, as the title wording "released" does imply a bit of an official vibe (as opposed to if it were to say "leaked"). although immediate NO resolution in such a case is a bit unusual, I'll admit.
