<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Spotlight — Blog</title>
    <link>https://spotlight-rules.com/blog/</link>
    <atom:link href="https://spotlight-rules.com/feed.xml" rel="self" type="application/rss+xml" />
    <description>An openly-governed, maintained build of the Spectral API linter — and the Spectral ruleset format as a standalone specification that stands on its own, apart from any one tool.</description>
    <language>en</language>
    <lastBuildDate>Fri, 14 Aug 2026 00:00:00 +0000</lastBuildDate>
    
    <item>
      <title>The 2012 move, one layer up</title>
      <link>https://spotlight-rules.com/2026/08/14/the-2012-move-again-one-layer-up/</link>
      <guid isPermaLink="true">https://spotlight-rules.com/2026/08/14/the-2012-move-again-one-layer-up/</guid>
      <pubDate>Fri, 14 Aug 2026 00:00:00 +0000</pubDate>
      <description>Swagger was a config file for a code generator until a group of people decided it was a format. This is the same move, applied to the rules that govern the descriptions.</description>
    </item>
    
    <item>
      <title>Mapping every implementation of the format</title>
      <link>https://spotlight-rules.com/2026/08/07/mapping-every-implementation-of-the-format/</link>
      <guid isPermaLink="true">https://spotlight-rules.com/2026/08/07/mapping-every-implementation-of-the-format/</guid>
      <pubDate>Fri, 07 Aug 2026 00:00:00 +0000</pubDate>
      <description>The tool is one implementation among many — a claim worth nothing without a published list. So here is the list, with the evidence for every entry and a rule that maintainer corrections get merged on sight.</description>
    </item>
    
    <item>
      <title>Why splitting the Spectral spec from the tooling is the priority</title>
      <link>https://spotlight-rules.com/2026/08/03/why-the-split-comes-first/</link>
      <guid isPermaLink="true">https://spotlight-rules.com/2026/08/03/why-the-split-comes-first/</guid>
      <pubDate>Mon, 03 Aug 2026 00:00:00 +0000</pubDate>
      <description>The first move after forking was not fixing the tool. It was pulling the ruleset format out of the tool entirely — because whatever gets built first becomes the definition, and because &quot;supports Spectral&quot; currently means eight different things nobody has words for.</description>
    </item>
    
    <item>
      <title>Twenty-seven CI runs, and not one of them a test</title>
      <link>https://spotlight-rules.com/2026/08/03/twenty-seven-ci-runs-and-not-one-of-them-a-test/</link>
      <guid isPermaLink="true">https://spotlight-rules.com/2026/08/03/twenty-seven-ci-runs-and-not-one-of-them-a-test/</guid>
      <pubDate>Mon, 03 Aug 2026 00:00:00 +0000</pubDate>
      <description>A day spent on the unglamorous half of forking something — security policy, package metadata, branch protection — which turned up the fact that no test had ever run here, that the one workflow which did run belonged to somebody else, and that three things already written down were wrong.</description>
    </item>
    
    <item>
      <title>A development strategy you can actually switch to</title>
      <link>https://spotlight-rules.com/2026/07/30/a-development-strategy-you-can-switch-to/</link>
      <guid isPermaLink="true">https://spotlight-rules.com/2026/07/30/a-development-strategy-you-can-switch-to/</guid>
      <pubDate>Thu, 30 Jul 2026 00:00:00 +0000</pubDate>
      <description>Branching, releases, package management, README, and communication — proposed in public before any of it is built, because a fork nobody can switch to is worthless.</description>
    </item>
    
  </channel>
</rss>
