Name the flag for the change.
Name the flag for the change. When the change is in, delete the name. A flag that stays is just another setting nobody owns.
A Flagholm flag is one change, one owner, and one number. The app asks a single question: for this person, is it on? On is the new behavior. Off is the one you already shipped.
One change
The name is the change a person would say out loud. Receipt copy. Delivery window. Gift note. Not a program name, and not a ticket number. If you cannot say the change, you do not have a flag yet. You have a wish.
One owner
One person can turn it off without asking the room. Other people can look. Looking is not flipping. If five people can flip it, nobody flipped it, and the bad change stays on.
One number
The number is named before the flag goes on. Tickets. Late orders. A task that finishes. We do not open a flag so a meeting can go find a number afterwards. The gift note is still off for that reason.
Shipping a change should not take a meeting. The flag goes on a small slice first. One metric says whether it stays or comes back.
Off is the old path
Both paths stay in the code until the flag is deleted. Off does not mean a blank screen. It means the behavior customers already have. If Flagholm does not answer, the app keeps the last answer. If it never had one, the flag stays off.
Then the name comes off
Once the change is in for everyone, the flag is removed. The old path goes with it. A flag left on forever is a setting. Settings do not have owners. That is how a simple screen fills up with switches nobody will turn.
The rules are short on purpose. The rollout is the order we follow. The calls are what the rules look like on a real change.