Teach your chat to write for how its text will be read, so it stops sounding like a keynote on the page.
A talk, a podcast, a chat message, a tutorial and a manual are each written differently, and linguists call that difference register. Your chat learned from all of them at once, with no labels, and most of the persuasive text it saw was spoken first. So when it writes a post or an email it reaches for stage devices: the hook opener, the question with a two-word answer, the list of three picked for rhythm. Those work in a room, where the speaker controls the pace and nobody can rewind, and they fall flat on a page the reader can re-read. That mix is most of what people mean when they say a text "sounds like AI". This lesson teaches your chat to decide where a text will be read before it writes it.
Paste this
Read https://tychat.io/register.txt and follow it for the rest of this chat. If you cannot open that link, read https://raw.githubusercontent.com/uncovertechtalent/tychat.io/main/register.txt instead.
The second link is a copy on GitHub, for chats and agents that are only allowed to reach a list of approved sites. If your chat cannot open links at all, open register.txt and paste its text in. About 1,800 words.
Before and after
An incident write-upBefore: "We removed the retry limit. The result? Chaos."After: "We removed the retry limit, and the queue grew until the disk filled."
The overcorrectionNested: "The migration, which was scheduled for Saturday because that is when traffic is lowest, failed at the step where the index is rebuilt, which left the site read-only."Additive: "We scheduled the migration for Saturday, when traffic is lowest, and it failed on the index rebuild, so the site stayed read-only until Monday."
What it teaches
Name the cell. Decide whether the text will be heard live, heard as a recording, read in a chat or read on a page, and what it is for. Two questions settle most of it: can the reader go back, and who sets the pace?
Drop the stage devices on the page. Hook openers, rhetorical questions with punch answers, triples picked for rhythm, chains of fragments, recap closers.
Avoid the overcorrection. Long sentences are fine, and plenty of people write long, breathless ones. The machine tell is nesting: clause inside clause, "which" after "where". Build long sentences by adding clauses the way you would say them.
Reverse it for scripts. Text that will be spoken keeps the stage devices and drops nested clauses, dense numbers and "as mentioned above".
Your voice, on request. Give it samples of your writing and it copies the shape of your sentences. It leaves your typos, jokes, coined words and emoji for you to add, because invented ones are the next thing readers spot.
Check it worked
Run these before you paste the line and again after. Compare the answers.
A short post. Ask for a post on any topic. Look for a hook opener, a question with a two-word answer and a list of three that only has two real items.
A talk script. Ask for a script on the same topic. The stage devices should come back, and the nested sentences should not.
Your voice. Paste a few paragraphs you wrote and ask for a new one in your voice. The sentences should be built like yours, with no typos or jokes you never made.
What it does not do
The lesson is text in your chat's context, and it fades, so expect the stage devices to creep back in long chats and whenever you ask for something persuasive, and paste the line again when you see them. Fixed phrases such as hook openers can be caught by a mechanical check at the output; vestige-kit is one, and you can add rules to it. Sentence shape still needs a reader.
Version
v1.12026-09-29 · register.txt sha256 1eb2d11d · adds the agent check (who does the verbs) and the structure-first order; the agent check came from a reader reply on r/ClaudeAI
v12026-09-29 · register.txt sha256 9421d08c (superseded) · sources: Ong, Orality and Literacy (1982); Biber, Variation across Speech and Writing (1988); the mode-leak filter and a before-and-after of one article draft