Resilience
When something fails.
A piece goes down, or something goes genuinely wrong. The system is designed to give the same answer to both: stop what is risky, and keep your customer answered.
01
A failure becomes a handoff
When a step cannot be done safely, Razviel does not attempt it. It escalates. If a piece Razviel depends on is unavailable, the system stops touching money and credentials and sends tickets to your own helpdesk, where your team answers them in the tool it already uses.
02
A ladder, not a switch
Containment steps down in stages. First Razviel keeps answering but stops moving money. Then it stops touching credentials too, and hands everything to your helpdesk. The same ladder serves an outage and an attack, so a defense can be strict without leaving your customers unanswered.
03
Contained per store
Every stage is set store by store. Containing one store never degrades another, and nothing that watches one store reads another’s evidence. The same isolation that exists for security keeps a problem in one place.
04
Money: it happened, or it did not
Every money action is written down as intended before it is sent, and recorded as done only when the platform confirms it. If the platform does not answer, the same request is resent with the same ID, so the platform can recognize it as a repeat. After a set time, Razviel reads the order itself and acts on its real state, never resending blind.
05
Irreversible steps belong to a person
Destroying a key, rotating a customer’s credentials, notifying customers or authorities, rolling back a release: none of these is left to automation, and containment is never left to the AI. Leaving a state that an attack triggered is a person’s judgment too.
06
Evidence the running code cannot erase
Every decryption and every money action leaves a record. The primary record lives in your workspace; a copy goes to a separate evidence store, kept apart by design from the environment that runs the service, so that compromising one cannot reach or erase the other. The record of each decryption carries metadata, never the content itself.
07
If there is an incident
Razviel notifies you without undue delay and in no event later than 72 hours. Where Shopify-protected customer data is involved, Shopify is also notified within 24 hours. These are two distinct clocks, and both apply.
As the controller of your customers’ data, you decide how and when they are told, and Razviel gives you the facts to do it.