About

The consultancy born at the intersection of behavioral economics and human experience.

René Studio
AI EXPERIENCE STUDIO

The CX design platform we built from a decade of client work.

Open rene.cx
Mysterya
MYSTERY AUDITS, LIVE

Mystery audits we run, scored live for every location.

Open mysterya.cx
NOW HIRING

Join a team reshaping how the world experiences brands.

View open roles →

COMPANY

GROW WITH US

CONNECT

Services

Comprehensive CX and management consulting for enterprise brands.

René Studio
AI EXPERIENCE STUDIO

Every engagement, mapped and scored in one AI workspace.

Open rene.cx
Mysterya
MYSTERY AUDITS, LIVE

Mystery shopping, scored and evidenced in real time.

Open mysterya.cx
ALL SERVICES

Explore the full range of CX & management consulting services.

Browse all services →

CORE

SPECIALIST

Solutions

Structured solutions that turn CX ambition into measurable outcomes.

René Studio
AI EXPERIENCE STUDIO

Map, score and fix the journeys we redesign, with AI.

Open rene.cx
Mysterya
MYSTERY AUDITS, LIVE

Check the experience you designed is delivered.

Open mysterya.cx
ALL SOLUTIONS

Explore every CX solution we offer.

Browse solutions →

STRATEGY & GOVERNANCE

DESIGN & DELIVERY

CULTURE & EXPERIENCE

Industries

A decade of CX transformation across the region's defining sectors.

René Studio
AI EXPERIENCE STUDIO

Sector-ready journeys, scored by AI in minutes.

Open rene.cx
Mysterya
MYSTERY AUDITS, LIVE

Mystery audits tuned to your sector, scored live.

Open mysterya.cx
ALL INDUSTRIES

See how we work across every sector.

Browse industries →

BUILT ENVIRONMENT

FINANCE & TECH

PEOPLE & MOBILITY

Products

Proprietary tools, platforms, and AI that power CX transformation.

René Studio
AI EXPERIENCE STUDIO

Design, score and fix customer journeys with AI.

Open rene.cx
Mysterya
MYSTERY AUDITS, LIVE

Audit every location and act on what you find.

Open mysterya.cx
REBELDECK A · 36 FORCES

The forces that shape how humans experience the world.

Explore REBEL Reveal →
ALL PRODUCTS

Explore the full Renascence product ecosystem.

Browse products →

AI & TECHNOLOGY

LEARNING & GAMES

PLATFORMS & TOOLS

CX TOOLKIT

Opinion

Insights, research, and conversations at the frontier of CX.

René Studio
AI EXPERIENCE STUDIO

Turn what you read into a journey you can score.

Open rene.cx
Mysterya
MYSTERY AUDITS, LIVE

See what customers really experience, visit by visit.

Open mysterya.cx
ReadExperience JournalArticles & research on CX, behavior, and transformation.Watch & listenExperience LoomOur video podcast on CX & behavior.CuratedCX NewsIndustry news that matters in CX, minus the noise.

Latest articles

Latest episodes

Latest news

Hub

Free tools, templates, and resources to advance your CX practice.

René Studio
AI EXPERIENCE STUDIO

Design, score and fix customer journeys with AI.

Open rene.cx
Mysterya
MYSTERY AUDITS, LIVE

Every visit, every location, every score. Live.

Open mysterya.cx
THE MANIFESTOBurn the Deck.
Ten Virtues. Zero Excuses.Start reading →
THE HUB

Every free tool, template and resource in one place.

Visit the Hub →

AI TOOLS

FREE TOOLS

LEARNING

CULTURE

AI · 15 October 2026

Linux kernel drops AI disclosure rule for contributor accountability

The Linux kernel project has dropped its requirement that contributors disclose AI tool use. Linus Torvalds said contributors must understand their code, whatever tools they used to produce it.

Newsdesk
Curated briefing · 2 min read

What happened

The Linux kernel project has dropped its requirement that contributors disclose their use of AI tools, according to reporting by The Register. The change was framed by Linus Torvalds, who said contributors must understand their code, whatever tools they used to produce it.

The shift moves the kernel's contribution policy away from asking how code was made and towards asking whether the person submitting it can stand behind it. For a project of this scale and influence, that is a notable change in how AI-assisted work is governed in open-source development.

Why it matters

AI coding assistants have made it easier to generate patches quickly, and that speed creates a governance question. Mandatory disclosure treats the tool as the risk. Torvalds' framing places the risk on understanding and accountability: a maintainer reviewing a change needs to know that the contributor grasps what it does, how it fits the wider codebase and what it might break.

For leaders in digital transformation and AI adoption, the lesson extends well beyond open source. Organisations that rely on AI-generated work need review processes that test comprehension and ownership, not just provenance. Declarations of tool use may tell a reviewer very little about whether the output is sound, and they can quietly add friction for the people doing the work.

The Renascence take

Most coverage of this story will read it as a relaxing of rules. We see it as a redesign of the signal. A disclosure requirement is an experience like any other: it asks people to perform a ritual that adds effort without necessarily improving the outcome the process is meant to protect.

The real design question is not "who used AI?" but "who can explain this change under review?" Teams that replace provenance checks with comprehension checks, such as clear ownership, short written rationales and reviewers who can probe the logic, get more signal for less ceremony. Operators should audit their own AI disclosure rules and ask whether each one measures quality or merely makes people feel accountable. If it is the second, it is theatre, and it will be the first thing people game.

Sources

This briefing was written by our Newsdesk, synthesising reporting from the outlets below. Follow the links for the original coverage.

FAQ

Questions we get on this topic

According to reporting by The Register, Linus Torvalds framed the change around understanding: contributors must understand their code, whatever tools they used to produce it.

It shifts from asking how code was made to asking whether the person submitting it can stand behind it, including explaining what it does, how it fits the wider codebase and what it might break.

Organisations relying on AI-generated work may need review processes that test comprehension and ownership rather than provenance, since declarations of tool use may tell a reviewer little about whether the output is sound.

Stay ahead of CX

Get the signal, not the noise.

The stories shaping customer experience — plus the Journal and Experience Loom — in your inbox.