Almost every enterprise system offers a confirmation dialog and calls it safety. Asking whether you are sure is not the same as being able to put something back. In AEROSS every governed action has a reversal registered against it, and reversing something writes its own record rather than editing the original.
Twenty-four hours. After that the action stands and putting it back is new work with its own approval. The window is a constant in the code rather than a policy setting that can be quietly extended.
No. Every reversal is an operation inside AEROSS. Nothing calls out to a system AEROSS wrote into on your behalf, so undoing a governed write into one of your own platforms is a second approved action rather than something that happens automatically.
It is append-only: there is no edit or delete path for anyone using the platform, in any role, and reversing something writes a new record rather than erasing one. It carries no hash chain and no signature, so AEROSS does not describe it as cryptographically sealed or tamper-evident.
Yes. Systems that guard against duplicate requests usually swallow the repeat. Here the guard checks whether the earlier action was reversed, and if it was, the repeat executes properly rather than returning the original result.