Set limits for a warm-up stage verifiedcriticalWritten by the Hub
Profile, rule, reload, read back — with the two rules that make it safe: one target per rule, and never write meaningful for a switch nobody chose.
In detail
Limits from several matching profiles combine, strictest value winning, so a new profile cannot loosen an existing one — it can only tighten. That is the right direction for warm-up and worth saying to anyone who expects their new profile to raise a rate that another profile caps. The rule is the part that can quietly break somebody else's configuration: a (domain, address, pool) combination belongs to exactly one profile, and claiming a taken one moves it. The engine says so in its answer, so a generator that reads the answer can report the transfer instead of hiding it. The behaviour switches are the other hazard. flags holds values and meaningful says which of them this profile decides; writing a non-zero mask for switches the operator never touched freezes greylisting strictness and timeout handling at whatever flags happened to contain.