(pronounced “sword”)
a SSORD is essentially just a database pushed to the public before it’s been massaged into a shape that will do good, and in a format that extracts money from the local community
SSORDs are databases exposed to the public and a database is not a guidebook. No volume of contributed data changes what this structure is built to do. They come with baggage.
Climbing’s written knowledge – its guidebooks, topos, area histories – is a community asset. The SSORD is a structural category for understanding one way that asset gets managed, and what that management costs.
SSORDs have absorbed much of that knowledge while introducing structural problems the community didn’t conciously choose this.: The climbers in Smith Rocks are entirely unaffected by what the folks at T-Wall are doing. Not so on a SSORD.
Renaming a route after a major hold breaks at Rumney doesn't require a regional approval from a private company. Not so on an SSORD, you'll need to reach out to an admin.
star-ranking model that concentrates attention on a handful of climbs while flattening everything else.
Every area gets the same treatment — Vedauwoo, Seneca, Bishop — each with its own character, history, and community, rendered in the same template. The result treats climbs as inventory and climbers as consumers
Trying to get a SSORD to add friendly features, or replacing one with another could improve the situation but it won't change the model.
On top of that, SSORDs don’t last. When they fail or change hands, the knowledge goes with them.
A SSORD is a route database owned and operated by a single entity, spanning enough areas that local fidelity becomes structurally impossible. The data is largely community-contributed; the control is not.
Scale is part of the definition. A single owner maintaining a database for their local crag is doing community service. The same structure applied across thousands of areas is a different thing and has different effects.
These are not failures of execution. They follow from the form.
A SSORD can’t prioritize quality over growth because growth is the product. To keep existing, they need to be growing. The database is only valuable at scale, so scale is always the objective. A SSORD that's not growing is losing the numbers game to the next SSORD. In this race, quality is a secondary concern. There’s no version of a SSORD that says “we have enough areas, let’s go deeper on the ones we have.” That’s not a decision anyone at those organizations would ever make because it contradicts the model. The guidebook contrast is sharp: scope is a feature, not a limitation. A guidebook that covers Red River Gorge is complete when it covers Red River Gorge. That completeness is what allows the editorial work – you know what you’re working with, you can make judgments about what to include, what to emphasize, what to leave out. A SSORD has no equivalent moment of completion and therefore no equivalent editorial foundation.
When climbs and areas get similar treatment, size is what stands out, even if you're only going to get on 15 routes in a weekend, stars at bigger areas are more appealing. When two areas are presented the same way, why bother going to one with 50 climbs if another has 500?
SSORDs scale and uniformity, because that’s all they offer; SSORDs are a database dumped to the public. Their administrators aren’t owners and can’t be expected to act as such. Curation is deffered and many important notes get dumped into the catch-all comments section. It’s awkward at best, and an exercise in detective work/archaeology at worst.
Organizations are fallible. and could loose data
Organizations fail . This is not a criticism of any platform – it is a base rate.
When a SSORD fails or changes hands, the community does not recover what it contributed. Licensing terms typically prevent it. Unlike a book going out of print, there is no artifact that persists. The thousands of hours climbers put in are not theirs to keep.
Backups are beside the point. The problem is not data loss – it is that the rights to the data do not belong to the people who created it.
SSORDS are not "all climbing platforms"
Tools like Rakkup and GunksApps are not SSORDs. They are purpose-built, bounded in scope, and not engaged in absorbing community knowledge at scale. They serve a specific community with a specific tool. That is a different relationship.
SSORD is a structural category, not a verdict on any specific platform.
Locally-authored, intentional guides operate on different assumptions. The author is accountable to a place and a community, not to a platform’s consistency requirements.
The barrier has historically been production – layout, distribution, and tooling that individual authors and small communities couldn’t easily manage. Stele exists to lower that barrier. It carries no climbing data; it supports the people who do.
SSORDs operate at the level of data (mostly). Reluctance of climbers to check out somewhere new with just MountainProject highlights this. And the Climb-On Maps exists because of the void in knowledge left by these platforms.