How it works
Check first. Approve exactly what will happen. Verify after.
Connecting a tool, changing a record or moving a domain can break something that works. The rule here is that nothing changes until you have seen what will change, and a change is not "done" until it has been checked.
"Today" means in the default install, which runs in shadow mode: actions are staged for approval and sends are simulated until you connect real accounts.
| Step | What it means | Today |
|---|---|---|
| Propose | The change is drafted with its evidence and shown as a preview. | Available |
| Approve | A person approves the exact content. The approval is single-use and no longer applies if the content changes. | Available |
| Act | The action runs once. If the outcome is uncertain it is held as "unknown" and checked before any retry, so nothing is sent twice. | Available |
| Verify | The result is checked against the system that holds the record, not taken from the agent's own report. | Available |
| Receipt | You get the approval, what was requested and what the other system answered. The event log is hash-chained so an edited or removed event is detected. | Available |
| Discover and baseline | Before a risky change, read the current setup (for example a domain's mail records) and record how it behaves now, read-only. | Planned |
| Preflight and dry run | Check prerequisites and show the difference the change would make, without making it. A simulation is labelled as one and is never presented as proof the live change worked. | Planned |
| Recovery plan | A written way back for each change, with a plain statement of what cannot be undone quickly (DNS propagation, delivered mail). | Planned |
What this does not promise
- No change is risk-free, and we do not say "no downtime" or "it won't break your email". We say what is checked before, what you approved, what was verified after, and how to go back.
- A passing check is evidence about the thing checked, nothing wider.
First planned use: domain check, which reads your email records and tells you what to expect before you touch anything. The engineering behind approvals and receipts is described on redevops.io.