> For the complete documentation index, see [llms.txt](https://jordan-7.gitbook.io/jordan-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jordan-7.gitbook.io/jordan-docs/internal/design/copy-bank.md). # Copy bank Lines that were written, liked, and not used yet. Kept so they are findable when a surface needs marketing copy, or when a shipped line gets replaced. ## The register Surgical critique of what is broken, not a value proposition. Blame the platform's design, not the person using it. Concrete over abstract: a number, a cat's name, a robot reading a donation aloud. Avoid pitch-deck vocabulary — "connecting communities", "holistic", "engagement" are all out. ## Live now * **Landing closer:** `Parasocial is a design flaw.` / `You're more than a username.` * **Landing hero:** `Skip the chat. Be the stream.` * **Bounty page:** `Your favorite streamer doesn't even know you.` / `Be more than a username.` ## Banked — approved, unused Ranked roughly by how much the user liked them. * Don't be a statistic. / Don't be a metric. *(deliberately meme-y)* * Stop simping. Start interacting. * You're not part of a community. You're part of analytics. * You just paid a robot $5 to read your name out loud. * 400 hours watched. Zero seconds seen. *(rejected)* * You know his cat's name. He doesn't know you exist. * You've typed 10,000 messages. He's read four. * Everyone has a camera. Chat still wants 200 characters. * Still typing into a box like it's 2003. * Chat hasn't changed since IRC. * A scrolling column of text is not a community. * The relationship is real. It only goes one way. * Nobody remembers a username. * Quit the comment section. ## Retired * `A chat app for people who'd rather be on TV.` — sold status, not the flaw. * `CALL-IN SHOW + FACETIME + SUPERCHAT = MEGACHAT` — the most formulaic line on the page; replaced by the closer's subline. * `Stop being a username.` — shipped briefly, superseded. * `Money waiting on a name` — the bounty headline. Long, and it described the mechanic instead of the reason anyone would care. * The bounty page's preview-build disclosure — removed at the user's call: the page does not launch until settlement is real, so a line about funds not moving describes a state that will not exist when anyone sees it. ## Planned use: the bounty page The bounty page has no call to action written yet. The intent, in the user's words: use this register plus **"demand more"**, and make the ask concrete — > Record a MegaChat, put money on it, and tell your favourite streamer to come claim it. That is the whole bounty loop stated as an instruction to a fan rather than as a description of a mechanism, and it is the one page where "demand more" is literally what the product does. Not built yet. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://jordan-7.gitbook.io/jordan-docs/internal/design/copy-bank.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.