Keeping the session off the record

The chat is a scratchpad. The briefing is a slice you chose. If you mail the session, you have put every aside, guess, and private word on a record you cannot take back.

3 min read

A long session feels like the work. When someone asks what you figured out, the session is the object you have. Forwarding it feels complete. It is also how you put a scratchpad into correspondence: every aside, every cruel option, every private nickname, every guess the model wrote as a fact.

A briefing is a composed page, not an export. The chat can stay messy. The record should be a slice you chose.

The session is not a document you can stand behind

Context does not transfer. Worse, the parts that do copy are the parts you would never put in a letter. The joke about their VP. The working name you use for a parent. The third vendor you insulted while thinking. Those lines are easy to scroll past when you are the only reader. They are permanent when they arrive under your name.

Nicknames are private on RelayLink for that reason. The server will refuse a private word in the package. It will not refuse a paragraph of colour you left in because you pasted the thread. Approval is the rest of the filter. If you never look, the session is the record.

Attachments are out of scope. That is not only a product limit. A file of the chat would be the same mistake with a paperclip.

The slice is the honest artifact

What belongs on the record:

  • The question you still want answered.
  • The options you closed, and why.
  • The facts you can point at.
  • The guesses, marked as guesses.
  • The sentence you will stand behind.

That set is smaller than the session. That is the point. You are not hiding the work. You are refusing to publish the parts that were never for them.

If they ask how you got there, give them the rejected paths in lines. That is the useful residue. They do not need the twenty turns where you and a model were wrong together.

Two audiences, two objects

The session is for you and a model that already holds your constraints. The package is for a person who may have no AI, or a different one, and who may read it on Monday. Writing one object for both audiences is how the scratchpad leaks.

A hand-off to yourself follows the same split. The other model should see the words you approved, not window one. Address the briefing to your own email. The chat stays where it is.

You cannot unsend a session

Once the paste is in their mailbox, it is theirs. You can send a correction. You cannot make them unsee the aside. You cannot pretend the guess was labelled after the fact. You cannot take the nickname back.

Compose the slice. Confirm it. Let the session remain a session — useful, lossy, and off the record. The correspondence is what you were willing to put a signature on. Everything else can stay in the window you do not share.

Frequently asked questions

Should I attach the chat or paste it under the brief?
No. Attachments are out of scope, and a paste is still the session. Compose the slice: ask, closed options, labelled guesses, a note you approved.
What if they ask to see how I got there?
Tell them the rejected paths and the premises, in sentences. That is the useful part of the session. The rest is scratch.
Does a hand-off to myself put the chat on a record?
Only what you approve. Address a briefing to yourself and the other model sees that slice — not the first window.