{"id":78027,"date":"2026-04-23T15:52:37","date_gmt":"2026-04-23T15:52:37","guid":{"rendered":"https:\/\/creativecommons.org\/?p=78027"},"modified":"2026-04-23T15:54:49","modified_gmt":"2026-04-23T15:54:49","slug":"update-on-cc-signals-what-changed-and-why","status":"publish","type":"post","link":"https:\/\/creativecommons.org\/2026\/04\/23\/update-on-cc-signals-what-changed-and-why\/","title":{"rendered":"Update on CC Signals: What Changed and Why"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">It\u2019s been a while since we last shared an update on CC signals and our work around AI and the commons. Over the past several months, we\u2019ve been deep in <\/span><a href=\"https:\/\/creativecommons.org\/issue-briefs\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">research<\/span><\/a><span style=\"font-weight: 400;\">, <\/span><a href=\"https:\/\/creativecommons.org\/2026\/02\/18\/cc-licenses-data-governance-and-the-african-context\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">in conversation<\/span><\/a><span style=\"font-weight: 400;\">, and <\/span><a href=\"https:\/\/creativecommons.org\/2026\/03\/04\/ais-infrastructure-era\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">in active collaboration with communities, policymakers, and practitioners<\/span><\/a><span style=\"font-weight: 400;\">. At the same time, <\/span><a href=\"https:\/\/creativecommons.org\/2026\/04\/14\/celebrating-25-years-of-choosing-to-share\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">we kicked off our 25th anniversary celebrations<\/span><\/a><span style=\"font-weight: 400;\">, which gives us a rare opportunity to reflect on where we\u2019ve been and, more importantly, where we need to go next.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The biggest reason for the gap between updates is timing. We are deliberately resisting the pressure to move quickly simply because the broader technology landscape rewards speed. Our work touches the infrastructure of the commons. That requires care, consultation, and a willingness to sit with complexity.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">So we slowed down. We let the first wave of AI development crest without rushing to respond. We took the time to understand where power is consolidating, where harms are emerging, and where meaningful intervention is actually possible. We are now at a point where we believe we can act in ways that will have real impact.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This post is meant to bring you into that journey. Our destination has not changed, but the path we are taking to get there has. Come along!<\/span><\/p>\n<h2><b>From Signals to Agency<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">When we first introduced <\/span><a href=\"https:\/\/creativecommons.org\/2025\/06\/25\/introducing-cc-signals-a-new-social-contract-for-the-age-of-ai\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">CC signals<\/span><\/a><span style=\"font-weight: 400;\">, the idea was relatively straightforward. We proposed a set of preferences that creators could use to communicate with AI developers, relying on shared norms to guide behavior. It reflected how CC has historically operated. For 25 years, we have worked within copyright, building tools that expand access while maintaining a balance between creators and reusers. That history shaped our instincts. We assumed that a carefully calibrated, norms-based approach would move the ecosystem in a better direction.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">But as we began consulting with our community, it became clear that this approach was not enough. The feedback was direct and consistent in stating that preference signals without enforcement do not meaningfully shift power. Signals alone cannot create agency in a system that many people did not choose to participate in.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">That feedback forced us to confront some of our own assumptions. For a long time, copyright has been our primary tool, and with good reason. CC licenses have enabled the sharing of tens of billions of works and have helped build a more open internet. But relying on copyright as the default lens for every problem has its limits, especially in an AI-mediated environment.\u00a0<\/span><\/p>\n<h2><b>Beyond Copyright<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Over the past four months, we have been reexamining what it means to support the commons in this new context.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">CC licenses remain essential. They will continue to play a critical role in enabling human access to knowledge. However, when it comes to AI, copyright operates in a landscape that is uneven and often unclear. In many cases, CC license conditions do not apply to AI training. <\/span><a href=\"https:\/\/creativecommons.org\/using-cc-licensed-works-for-ai-training-2\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">In others, they might<\/span><\/a><span style=\"font-weight: 400;\">. In some jurisdictions, broad exceptions mean that using CC-licensed works for AI development is lawful regardless of license conditions. At the same time, the presence of a CC license is often interpreted as permission to use the work in this way. That interpretation follows from how the licenses were designed; they grant broad permissions with limited conditions.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The CC licenses were not designed with the scale and growing harms caused by the dominant, profit-driven approaches to AI in mind. And CC licenses do not capture the full range of intentions creators have in this AI-mediated world. Some creators are comfortable with their work being used in AI systems; others are not, and many fall somewhere in between.<\/span><\/p>\n<h2><b>Why New Tools Are Necessary<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">We also explored whether updating the CC licenses themselves, in the current paradigm, could provide a solution. Versioning has helped us adapt to new contexts before. But in this case, there are two novel factors at play.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The first is structural. CC licenses were designed not to enable control beyond copyright. They are intentionally scoped to copyright and related rights, and they explicitly do not allow additional restrictions that would limit uses outside that scope.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Our <\/span><a href=\"https:\/\/creativecommons.org\/policies\/#trademark\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">current trademark policy<\/span><\/a><span style=\"font-weight: 400;\"> reinforces this. If restrictions are added that limit the permissions granted by a CC license, the work can no longer be presented as CC-licensed. This reflects the critical role that standardization has played in the success of open licensing. When you access a CC-licensed work, you should be able to rely on the terms and conditions written in the license to determine what your reuse obligations are. Expanding the CC license suite beyond its original focus on copyright would represent a significant change to how the licenses operate, and it could have unintended consequences on the existing license ecosystem.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This brings us to the second factor, which is that CC licensors have such a wide spectrum of needs and values about how and whether their works are used in AI. It is possible that new tooling would better address what may be irreconcilable within the open movement: some see any tool that attempts to control AI uses that fall outside of copyright as a betrayal; others see it as an imperative.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">With the future of the commons in mind, at this time we believe that the best approach is to innovate with the development of new tools, where we can test and explore more freely. The CC licenses are one part of a larger strategy needed to meet this moment, which is evolving in an undefined legal landscape, just as it was 25 years ago when the CC licenses were first developed.\u00a0<\/span><\/p>\n<h2><b>The Stakes for the Commons<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Our north star remains the same: sustain access to human knowledge. Today, that means more than enabling sharing. It means questioning long-held assumptions, and ensuring communities are in control of their own data. It means holding the tension that, in some cases, conditional access is better than no access. The commons needs guardrails in order to thrive.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">AI systems are being built on an unprecedented scale of knowledge extraction, drawing heavily from the commons. The governance systems that made open sharing possible have not kept pace with this shift. There are limited mechanisms for attribution in AI systems, few pathways for consent, and little transparency.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When the commons weakens, power over information becomes more concentrated. Knowledge moves into private datasets and proprietary systems controlled by a small number of actors. That limits who can access, verify, and build on information. Democracies depend on broad access to reliable knowledge. <\/span><a href=\"https:\/\/publicinterest.ai\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">Public interest AI<\/span><\/a><span style=\"font-weight: 400;\"> depends on diverse, high-quality data.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A healthy commons is governed and sustained through systems that balance access with agency, openness with accountability. AI relies on the commons, not the other way around. If we want a future where knowledge is shared and where AI serves the public good, we need to ensure that the commons can thrive. This is the context in which we evolve CC signals.\u00a0<\/span><\/p>\n<h2><b>Strengthening CC Signals<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Our problem statement has not changed, and neither has our end goal. But what we are building to get there has.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">What began as a relatively narrow, tool-focused approach has evolved into something broader and more structural. CC signals is no longer limited to signaling preferences. CC signals is about addressing the underlying conditions that have made creator preferences so easy to ignore. This shift has led us toward work that is more ambitious, and necessarily more disruptive, in confronting the real harms to the commons emerging from dominant, profit-driven approaches to AI.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Check back with us next week, when we\u2019ll share more about the specific interventions we are building from this foundation.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>It\u2019s been a while since we last shared an update on CC signals and our work around AI and the commons. Over the past several months, we\u2019ve been deep in research, in conversation, and in active collaboration with communities, policymakers, and practitioners. We took the time to understand where power is consolidating, where harms are emerging, and where meaningful intervention is actually possible. We are now at a point where we believe we can act in ways that will have real impact.<\/p>\n","protected":false},"author":30,"featured_media":78030,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[3847,21],"tags":[3898],"acf":[],"_links":{"self":[{"href":"https:\/\/creativecommons.org\/wp-json\/wp\/v2\/posts\/78027"}],"collection":[{"href":"https:\/\/creativecommons.org\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/creativecommons.org\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/creativecommons.org\/wp-json\/wp\/v2\/users\/30"}],"replies":[{"embeddable":true,"href":"https:\/\/creativecommons.org\/wp-json\/wp\/v2\/comments?post=78027"}],"version-history":[{"count":4,"href":"https:\/\/creativecommons.org\/wp-json\/wp\/v2\/posts\/78027\/revisions"}],"predecessor-version":[{"id":78033,"href":"https:\/\/creativecommons.org\/wp-json\/wp\/v2\/posts\/78027\/revisions\/78033"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/creativecommons.org\/wp-json\/wp\/v2\/media\/78030"}],"wp:attachment":[{"href":"https:\/\/creativecommons.org\/wp-json\/wp\/v2\/media?parent=78027"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/creativecommons.org\/wp-json\/wp\/v2\/categories?post=78027"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/creativecommons.org\/wp-json\/wp\/v2\/tags?post=78027"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}