Chapter 01 of 08
The Launch Notes · Vol. 01 No. 04
Controls · 01
September 2026 · London
Cover story · 2 September 2026
A claims register that can survive scrutiny
Every public sentence on a launch needs an owner, evidence, permitted wording and an archive. Most teams keep messaging in a shared document and a group chat. That is not a control. This is the operating sheet — and the argument for running it as the spine of the campaign.
The Desk · Operating notes, RCA Pad · London
The first person who notices that the landing page, the founder interview and the creator thread have drifted from each other is usually not the team. It is a journalist, a counterpart, a regulator’s intern, or a buyer who will never reply. A claims register exists so that drift is caught in the house, on purpose, before a sentence leaves.
The scene · Chapter 01
The first person who notices
Launch week is a coordination problem dressed up as a marketing problem.
On a Tuesday in late summer a founder records a twenty-minute conversation for a trade desk. The landing page, last touched on Friday, still says the testnet has been live since March. The conversation says “we have been live for more than a year.” A creator, paid and well-meaning, posts that the protocol is “battle-tested.” None of these people is lying in the way a prosecutor uses the word. They are using the sentences they have. The sentences are not the same sentence.
By Thursday the thread has been quoted into a market chat. By Friday a counterpart in diligence asks for the explorer URL that would make “more than a year” true. There is an explorer. It does not make that sentence true. The founder writes a clarification. The creator does not. The landing page is updated by someone who was not on the call. Three artefacts, three clocks, one brand.
This is not a rare failure. It is the default failure of a launch that treats messaging as content rather than as a controlled inventory. Teams that have raised, shipped a testnet and hired a designer still keep the public story in Notion, in Figma comments, in a Telegram pin, in a founder’s head. When the story moves, the copies of the story do not.
RCA Pad maintains a claims register for every client because the alternative is folklore. Folklore is fine for a dinner. It is not fine for a sentence that will be read as an invitation, a fact, or a promise. The register is the single list of what may be said, to whom, where, and on what evidence. If a field is empty, the claim is not ready. If the evidence cannot be produced, the claim is removed — not softened.
If factual claims cannot be evidenced, do not publish them. If the audience, jurisdiction or promotion route is uncertain, pause. Record the decision.
The rest of this feature is the operating sheet: why the register exists, what it contains, how a claim is born, how it dies, and how a fourteen-day Sprint puts the thing on the desk instead of in a slide. It is long because the work is long. A one-page policy that nobody uses is a poster. A register that is filled, dated and archived is a control.