<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AI Usage Scale — releases</title>
    <link>https://usagescale.org</link>
    <atom:link href="https://usagescale.org/feed.xml" rel="self" type="application/rss+xml" />
    <description>Version history of the AI Usage Scale. A change to what a level means invalidates declarations already made against it — this feed exists so the tools and registries that adopt the scale know the moment it moves.</description>
    <language>en</language>
    <lastBuildDate>Sun, 09 Aug 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>1.2.0</title>
      <link>https://usagescale.org/spec</link>
      <guid isPermaLink="false">usagescale-1.2.0</guid>
      <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<ul><li>The law caught up, so the mapping did too. <strong>The scale is unchanged</strong> — same six levels, same definitions, same decision tree — so no declaration already published is affected. A minor version, by the policy above.</li><li><strong>Every level now carries its EU mapping.</strong> <code>levels.json</code> gains <code>euAiActIcon</code> and a note per level, mapping the scale onto the three EU icons published with the Code of Practice: Level 2 is an exact match for *Partially AI-Modified*, Levels 4 and 5 for *Fully AI-Generated*, and Levels 0 and 1 need no icon at all. <strong>Level 3 is marked as contested rather than guessed</strong> — its substance is human and its form is not, so neither EU term is true of it, and the basic icon plus its interactive second layer is the honest mark.</li><li><strong><code>interop</code> gains three legal regimes</strong> beside W3C, IPTC and C2PA: the EU AI Act with its icons and Code of Practice, China's labelling Measures with GB 45438-2025, and the California AI Transparency Act (SB 942 as amended by AB 853). All three ask the same three questions — was AI involved, how much of the work is its own, and did a human take responsibility.</li><li><strong>A correction on the EU AI Act page.</strong> It read as though human review switched the disclosure duty off generally. It does not: the Article 50(4) exemption is written for <strong>text only</strong>, so a reviewed, signed-off deepfake still carries the duty. That is now stated where the mistake was.</li><li><strong>Source code is outside Article 50.</strong> The Commission's final Guidelines (20 July 2026) exclude it broadly — code comments, SDKs, SQL, infrastructure-as-code, YAML and JSON configuration, schemas, scripts, APIs and libraries — along with short outputs and machine-to-machine output. The page says so plainly: the code surface of a declaration is not a legal artifact, and this standard never claimed the law asked for one.</li><li><strong>The page is current.</strong> Article 50 has applied since 2 August 2026, the Code of Practice was confirmed adequate in July 2026, and the remaining deadlines — 2 December 2026 for marking on systems already on the market, February 2027 for watermark interoperability — are named.</li><li><strong>242 corrections across all 21 translated locales.</strong> Each locale was audited against English for wording that would send a reader to a *different level*: a dropped negation, "most" softened to "some", "review" collapsed into "edit". Polish had narrowed "the expert" to "the surgeon" and rendered Level 5's "legitimate" as "legal"; Ukrainian, Russian and Turkish carried comparable slips. Key parity and interpolation placeholders are unchanged, and both are gate-tested.</li><li><strong>A wider document.</strong> Prose keeps a readable measure while tables, marks and snippets now span the full page, so a three-column mapping table is no longer squeezed into a prose column. Section headings open on a rule, level tables gained hairline rows and a header, and a wide table scrolls inside its own box instead of pushing the page sideways. No horizontal overflow at 320px.</li></ul>]]></description>
    </item>
    <item>
      <title>1.1.1</title>
      <link>https://usagescale.org/spec</link>
      <guid isPermaLink="false">usagescale-1.1.1</guid>
      <pubDate>Wed, 22 Jul 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<ul><li>Site hardening, accessibility, and documentation. <strong>The scale is unchanged</strong> — same six levels, same definitions, same decision tree — so no declaration already published is affected. A patch, by the policy in GOVERNANCE.md.</li><li><strong>The English-only reference pages now declare English.</strong> <code>ecosystem</code>, <code>integrations</code>, <code>cases</code> and <code>eu-ai-act</code> are served under every locale but keep English bodies. They were emitting <code>&lt;html lang="pl"&gt;</code> and hreflang for translations that do not exist; they now declare <code>lang="en"</code>, canonicalise to their English URL, and drop the false alternates — fixing a WCAG language mismatch and 84 duplicate URLs.</li><li><strong>A strict Content-Security-Policy.</strong> The site ships <code>default-src 'self'</code>, <code>connect-src 'none'</code>, hashed scripts and styles, plus <code>X-Frame-Options</code> and a <code>Permissions-Policy</code> — the "nothing phones home" promise, now proven at the browser level. A build gate fails if the inline theme script's hash ever drifts out of sync.</li><li><strong>New docs:</strong> a [threat model](docs/THREAT-MODEL.md) — how a self-declaration can be misused, and what the design does and does not defend — and a [FAQ](docs/FAQ.md).</li></ul>]]></description>
    </item>
    <item>
      <title>1.1.0</title>
      <link>https://usagescale.org/spec</link>
      <guid isPermaLink="false">usagescale-1.1.0</guid>
      <pubDate>Mon, 20 Jul 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<ul><li>A boundary clarification, two new reference pages, and a larger badge family. No level changed its meaning; under the policy in GOVERNANCE.md this is a <strong>minor</strong> version.</li><li><strong>Boundary clarified: substance the model originated is new material.</strong> The decision tree's second question said ideation that leaves no model-produced material in the work is Level 1, while Level 1's own excludes said AI restructuring your argument is not Level 1 — two honest people could reach different numbers. Resolved in the direction the levels always promised ("It invented nothing" has to mean it): a thesis, argument, or structure the model originated is new material that survives into the work, even if you wrote out every word yourself. That is Level 2 or above; feedback, critique, and fact-finding you verify stay Level 1. New edge case: <strong>Substance from AI, wording from you</strong>. This resolves a contradiction rather than moving settled works between levels — a clarification, not a breaking change. Updated in all 22 languages.</li><li><strong>New page: the case corpus (<code>/cases</code>)</strong> — real published works classified, with the walk to the number shown and sources linked: The Beatles' "Now and Then" at Level 0, Zarya of the Dawn at 3 with a Surfaces breakdown, The Guardian's GPT-3 essay and CNET Money at 4, the AP's automated earnings, Heliograf and Air Canada's chatbot at 5, and Sports Illustrated's fake bylines as the undeclared anti-case.</li><li><strong>New page: EU AI Act (<code>/eu-ai-act</code>)</strong> — Article 50 for publishers: the disclosure duty for AI-generated text from 2 August 2026, the human-review exemption, and how it lands on the Level 4 / Level 5 distinction. Explicitly not legal advice; legal review remains on the roadmap.</li><li><strong>Spec: "If you doubt a declaration"</strong> — what a reader can do with a declaration they don't believe, in all 22 languages. The spec also documents the whole-site declaration at <code>/.well-known/ai-disclosure.json</code>, the discovery path for the Surfaces object.</li><li><strong>Marks: <code>auto</code> builds and a named chip.</strong> Every mark now ships in a <code>currentColor</code> build, so one inline snippet is legible on any host theme; the level pages' inline snippets use them. A new chip variant spells the level out — "AI USAGE 3 DIRECTED" — for audiences meeting the scale for the first time; the number-only chip stays the universal default. 54 SVGs, up from 24.</li><li><strong>Fixed:</strong> the hosted-embed snippet declared <code>width="205"</code> for a 122.5 px mark — dimensions are now read from the generated file; the two lighter text greys now clear WCAG AA for small text in both themes; a shared "Find your level" result link (<code>#level-N</code>) now opens on the result instead of question one.</li><li>Signing no longer requires GitHub: the sign page links the contact page as an equal path in every language. The author signed <code>signatories.json</code>.</li><li><strong>The draft has an end date.</strong> The level boundaries stay open for challenge through <strong>31 December 2026</strong>; the first stable release, without the <code>-draft</code> suffix, follows once the roadmap's Toward-1.0 gates close. Details in the roadmap.</li></ul>]]></description>
    </item>
    <item>
      <title>1.0.0-draft</title>
      <link>https://usagescale.org/spec</link>
      <guid isPermaLink="false">usagescale-1.0.0-draft</guid>
      <pubDate>Mon, 13 Jul 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<ul><li>Initial draft. <strong>Not yet stable — the level boundaries are open for challenge.</strong></li><li>Six levels, 0–5, decided by five yes/no questions.</li><li>Levels named: Human, Assisted, Co-created, Directed, Prompted, Automated.</li><li>Optional per-surface declaration (text, image, audio, video, code, data).</li><li>Edge cases settled: translation, transcription, decorative assets, derivative works, live generation, non-generative machine learning.</li><li>Mappings onto W3C <code>ai-disclosure</code>, IPTC Digital Source Type, and schema.org.</li><li>Badge family: 6 levels × chip/stamp × light/dark, type outlined, CC0.</li><li>Published in <strong>22 languages</strong>, with a switcher. Every translation declares itself as a machine translation on the page, under the scale's own translation rule.</li><li>Social cards, schema.org <code>DefinedTermSet</code> (the levels as a controlled vocabulary), reciprocal hreflang, <code>llms.txt</code> and <code>llms-full.txt</code> (the whole standard in one fetch).</li></ul>]]></description>
    </item>
  </channel>
</rss>
