I understand your concern with proposed features in general. I think that fact that the CyclOSM and Cycle Map layers on the OSM home page render proposed bike routes (as distinguished from existing) represents some consensus that they are useful (or at least acceptable) to map. (Waymarked trails also correctly parses the state=proposed tag.) But I take a conservative approach to doing so in NYC and only map them once DOT (or Parks/DDC/EDC) publicly present a specific route that they plan to implement. If multiple route options are under consideration (or multiple plans that might or might not include bike infra), I don't map that until one specific plan is decided on. For example, DOT has been doing workshops getting feedback on several options for Harlem River Greenway routes, and I haven't mapped any of them since they haven't announced which one they are moving forward with.  https://www.nyc.gov/html/dot/downloads/pdf/harlem-river-greenway-bronx-route-alternatives-north-section-mar2024.pdf And I do update the routes if the proposals are updated, and then based on construction and completion. 