A case for formalizing the Spectral ruleset format as a proper specification, backed by a published list of every known engine and product that implements it. The author catalogs open-source engines (including vacuum, an independent Go implementation), commercial products like IBM's OpenAPI Validator and Microsoft's Azure API Center that silently depend on the format, and invisible enterprise in-house implementations. The core argument: the format has become load-bearing infrastructure inside other people's products without ever being written down, creating incompatible private solutions to the same problems. The proposed path forward is a public implementations map followed by a conformance suite that makes 'compatible with the Spectral ruleset format' a testable claim rather than a marketing line.
