Corridor edits and the freeze you can actually keep
Ask a pack owner when last month’s figures actually froze. Many will name a calendar time and then describe the exception: a vice president asked for a restatement after a customer call. That restatement is a corridor edit. It may be justified. It is still a second pack.
Cadence design starts by writing the freeze in language a sceptical auditor would accept. “Tuesday 16:00, pack owner’s clock, no restatement without a dated exception note.” The note is visible on the canvas, not buried in a chat. Readers can see that a figure moved and why.
Functions will lobby to keep their own back doors. Finance wants late accruals. Operations wants yesterday’s outage. People wants a hire that closed at 17:10. A cross-functional charter lists which of those doors exist and which sitting is allowed to hear them. The others wait for the next cycle.
Releasepathgrid’s local tracking utility, when used, is a record of what was published, not a second unofficial pack. Compatibility mentions with other market names are about reading exported files for record-keeping. They are not a channel for restating figures after lock.