22 October 2026 · Kin Lane

The OpenLint specification draft is ready for feedback

Pill-shaped figures reviewing a two-page document of rule bars, with a mint-green squiggle resolving into a check mark above

The first formal draft of the OpenLint Ruleset Specification is published at spec.openlint.org, and we’d like your feedback.

Rulesets are how teams write down their API style guides and governance: thousands of them already exist in the Spectral format. But that format was never specified; it was whatever one tool did. This draft changes that. It describes the ruleset format as it works today, so existing rulesets stay valid, and writes it down as a proper specification that any tool can implement.

What’s in the draft

Joost Farla rewrote the specification as a formal Working Draft, built with Bikeshed, the tool behind many W3C-style specifications:

Where we need help

Writing the format down surfaced a lot of behavior that was never documented, only implemented. The draft marks 36 open questions inline, right where they occur. For example, a YAML file with several documents is accepted today, but only the first one is linted. Should it be?

These are exactly the decisions that need more than one voice:

Under our governance, changes to the specification stay open for at least 14 days, and anything breaking for 30, with known implementers told directly. Nothing here changes what your rulesets do today.

Join us at office hours on Thursdays if you’d rather talk it through.

Drafted with Claude, and edited by me.