Store review is not a measurement seminar, yet it rewrites App Analytics whether you attend or not. A policy change can make yesterday’s paywall_shown look like a tracking offence, or it can make a purchase event incomplete. Teams then do one of two unhelpful things: they strip the catalogue until the paywall is invisible, or they keep firing and hope.
Neither is a ledger. In the eighth week of The Release Lattice we practise a third path. Name what you are still allowed to observe. Version the event when the meaning narrows. Dual-write only inside the rules you have actually read — not the rumours from a Slack channel. Write the board sentence as “we can see trial start after account, we cannot see the copy variant”, if that is the truth.
Counsel is not our product. We are not your solicitor, and we will not certify a payload. We will mark a catalogue that pretends nothing changed. Pretence shows up later as a cliff in conversion that nobody can attribute to a ship, because the ship was “compliance” and had no row.
Enter the review as a release. Give it an owner. Give it an overlap window if old and new names must coexist. If the store forbids a property, delete it in the dictionary and say so. Empty cells that are empty on purpose are allowed. Mute products that still report “activation” as if the paywall were a free garden are not.
If this is the only wound you have, write to us about a shorter seat. If it is one chapter in a haunted book, bring the book to the Lattice.