sending-protect-real-profileslisted

# Real profiles never carry a mechanics experiment Split every experiment by what the platform sees. **Mechanics** is how we act on the platform: note or no note, a like before the invite, volume, a new action type, a new channel. Mechanics is tested only on a disposable profile and reaches real people's profiles already proven. **Text** is what we write: the platform does not score it, only the reader does, so voice and copy tests are fine on a real profile. A real profile is the founder's own, a partner's, and every profile that belongs to a client's employee. ## Why In our own engine the invitation note was exactly this kind of mechanics experiment, and it ran for three weeks on real people's profiles. In the last seven days of that run, four client profiles collected 20 refused invitations, and all 20 carried a note. The worst profile was refused 43% of the time. Our own measured norm for invites without a note was 0.3%. A refusal is a failed automated action, and the platform counts them. A disposable persona profile of ours died on day nine after eight invitations. A real person's profile dies the same way, except it cannot be bought back, and a client's profile also carries someone else's relationships. ## How to apply 1. Flag every profile in your data as protected or disposable. Protected: founder, partners, all client employees. 2. Before any change to how the engine acts on the platform, ask: which profiles will this run on? 3. If the answer includes a protect