REP9 in Plain English: What It Means When You Hear It on a Call

Heard a REP9 declaration in a meeting? Here is what it does, what it does not do, and how it relates to contracts and everyday AI notes.

A REP9 declaration is the start of a conversation. It helps useful AI-assisted work continue while making the contributor's position part of the record it creates.

If someone sent you this after a call If you heard a REP9 declaration at the start of a meeting, here's the simplest way to think about it: it's the start of a conversation about everything that meeting leaves behind. The transcript, the notes, the AI summaries, the copies that outlive the call itself. We call all of that "the record", and REP9 exists to let that useful work continue while making one contributor's position visible in it from the outset. That's usually more constructive than the two options people tend to default to: wave every tool through without question, or ask for everything to be switched off. REP9 doesn't accuse anyone, demand that notes stop, or reopen agreements already in place. It simply creates a natural moment to make the process visible, and to talk through any gaps while the original context is still fresh. Because a conversation can now travel much further than the people who were in it. One call can become a transcript, a summary, a task list, a document and part of a shared AI knowledge system, sometimes all in the same afternoon. REP9 gives a contributor a short way to put their position into that growing record without treating useful technology as the enemy. That REP9 message at the start of our call was there to help us use notes, transcripts and other AI tools with a clearer shared understanding of the record they create. It records a limited licence for ordinary call uses and reserves other rights I may hold, without replacing our contract or asking anyone to sign anything. REP9 is the start of a conversation, so please raise any questions. This guide explains it in plain English: https://rep9.ai/insights/rep9-in-plain-english-what-it-means-when-you-hear-it-on-a-call The simple idea behind REP9 REP9 starts with a familiar idea: when somebody contributes something to a conversation, the record should carry their position as well as their words. That mattered less when most conversations disappeared the moment the call ended. Someone might remember the broad point, jot down a few notes or send a follow-up email. Using the contribution anywhere else still took time, access and enough understanding to reconstruct it. AI removes almost all of that friction. A half-formed explanation can now become detailed, speaker-attributed text within seconds. That text can be searched, copied into another tool, joined with other records and used by people who were never on the call. This can be genuinely useful. It can also quietly separate a contribution from the person, the agreement and the context that originally surrounded it. The REP9 Licence 0.1 is a public draft designed for exactly that gap. A person can reference it with one short declaration. The licence then grants a limited set of everyday conversational uses, and only to the extent that person actually holds the relevant rights, while reserving their remaining rights. What the REP9 Licence allows REP9 is designed to let an ordinary conversation proceed normally. Its limited grant covers what the licence calls Ordinary Conversational Uses: recording and transcribing the conversation; taking notes; making summaries for a participant's own reference; retaining the resulting record; and quoting contributions internally among those present. The licence also allows some sharing inside the organisation a participant was representing, and through systems operated for that participant in connection with the conversation. Those allowances have defined limits though; they're not a general permission to publish the record or pass it around. The grant is limited to rights the contributor is actually entitled to license. It doesn't replace recording-consent rules, privacy law or an agreement that already governs the call. This is why hearing a REP9 declaration shouldn't bring a meeting to a halt. It isn't a request to put every sentence behind glass. It creates a baseline for ordinary use, then identifies where that baseline ends. What the REP9 Licence does not do The boundaries matter as much as the grant. REP9 does not: ask anyone to accept, acknowledge, sign or agree before the conversation can continue; create an NDA or require anybody to keep the call confidential; claim ownership of every idea, fact, method or short phrase discussed; create rights the contributor does not hold; block uses that applicable law permits without the contributor's permission; provide recording consent or technical access control; or promise what a court, regulator, platform or recipient will decide. Some uses sit outside its limited grant entirely: AI model training, derivative works, redistribution beyond the people, organisations and connected systems the licence covers, and use in legal proceedings. Each has its own definitions and qualifications in the legal code. The point isn't that REP9 can physically stop those uses. It's that they are not included in the permission the contributor has given under REP9. REP9 0.1 remains a public draft with no promised legal outcome . It's a way to state a position, not a guarantee about what happens next. What if a contract already governs the call? An existing written agreement doesn't disappear because somebody uses REP9. If a written agreement - an employment contract, a consulting agreement, a deal between two organisations - binds the contributor, governs the conversation and conflicts with REP9, the REP9 Licence says that written agreement prevails to the extent of the conflict. REP9 continues only on the matters the superior agreement doesn't address. So a consultant using REP9 is not silently rewriting the intellectual-property clauses in their client contract. Equally, the declaration isn't an admission that every contract somebody points to is valid, or that it applies to every contribution. REP9 can't settle those questions. It states its own order of priority and leaves any dispute about a particular agreement to the relevant facts and law. For advice about a specific contract, speak to a qualified legal adviser in the relevant jurisdiction. REP9 cannot provide that advice. Why the bigger risk is usually accidental, not malicious The easiest version of this story to imagine is deliberate misuse: somebody records a call because they intend to steal an idea. That can happen, but it isn't the everyday problem REP9 is mainly designed around. The more common problem is that somebody is simply trying to get work done. They add a notetaker, turn on a built-in summary, paste notes into a personal AI account or move the transcript into a team workspace. Six months later, another person finds the information without knowing where it came from or which agreement surrounded the original conversation. Security teams already have a name for part of this pattern: shadow IT. The UK National Cyber Security Centre says it is rarely driven by malicious intent. People commonly adopt unofficial tools because approved systems don't meet an immediate need, or because they don't realise a personally managed service creates a new risk. And the data rules can't be guessed from a logo or a price tag. OpenAI distinguishes individual ChatGPT services from its business offerings , and gives individuals settings that affect whether conversations help improve its models. Anthropic likewise distinguishes its commercial products from its consumer services. A free product isn't automatically unsafe, and a paid product isn't automatically well governed. The product, plan, settings, storage, permissions and later sharing all matter. Meeting platforms show how quickly the audience can expand even inside managed systems. Google Meet can attach generated notes to a Calendar event and lets organisers choose who receives them. Microsoft Teams stores recordings and transcripts in OneDrive or SharePoint , where meeting type, permissions and retention policies shape what happens next. None of those features is misuse in itself. The problem is assuming everyone on a call understands the same data journey when nobody has made it explicit. Why creative work makes the issue easier to see Creative industries already understand the output side of generative AI. Writers, illustrators, animators, architects, designers and musicians can see what happens when systems produce new material at scale. The input side can feel less visible because it arrives through ordinary work: a brainstorm, a technical explanation, a sketch on screen, an unfinished line of thought. Not every valuable contribution is a legal right, and REP9 doesn't claim otherwise. Ideas, facts and information aren't restricted by the licence simply because somebody said them. Original expression, recordings, transcripts and other fixed material can raise different questions, and contracts may allocate those rights before the call even begins. The practical point is simpler. If an organisation wants responsible rules for what AI produces, it also needs responsible rules for what its people and tools put into AI systems. A declaration can't replace that governance, but it can make the contributor's position much harder to lose. What to do when someone uses REP9 on a call Start by continuing the conversation. REP9 is designed to support ordinary uses such as notes and transcripts, and nobody needs to sign anything before the call can proceed. If the declaration prompts a question, that's useful. It may show that the people in the room don't yet share a clear view of which tools are active or where the resulting record will go. Four practical questions usually create more clarity than a debate about abstract intellectual property: Which tools are active? Ask whether the call is being recorded, transcribed or summarised, including through personal accounts or built-in features. Where will the record go? Clarify who receives it, which workspace stores it and how long it is retained. What already governs the call? Check any employment, consulting, confidentiality or organisation-to-organisation agreement that applies. Is a different process needed? If the conversation is unusually sensitive, agree whether a tool should be turned off or a more specific written arrangement is required. REP9 doesn't answer those questions for the group. It gives the group a reason to answer them while the context is still available. A clearer baseline for what your calls leave behind The standard REP9 declaration is available now . Personal links and spoken or text-to-speech declarations are private-beta capabilities. Future handshakes may help compatible systems detect and retain a declaration more reliably, but they will still need to distinguish discovery, acknowledgement, agreement and legal effect. The aim was never to turn every meeting into a legal negotiation, or to obstruct useful tools. It's to make those tools easier to use with a shared view of the longer-lived record they create, and to recognise that the people operating those systems share responsibility for what that record becomes. REP9 starts by putting one contributor's position on that record. That is its scope: a clearer baseline, not a guaranteed outcome.