Non-bypassable checklist
A deployed integration provides non-bypassable protection when every authority capable of performing the selected operation is inside the declared Luvion enforcement boundary. This checklist establishes that deployment property.
Authority inventory
- enumerate every owner, administrator, guardian, upgrader, pauser, minter, signer manager, and emergency role;
- include proxy administrators, timelock proposers and executors, Safe modules, direct EOA paths, and upgrade or recovery contracts;
- identify offchain custody, deployment, CI, or automation credentials that can reach the same authority.
Migration requirements
- Select one protected operation and define its canonical fields.
- Install or configure one Luvion-aware enforcement point.
- Migrate the protected authority to that enforcement point.
- Remove, revoke, or explicitly exclude every legacy route that can perform the same operation.
- Require the active Luvion authorization key, policy version, validity window, replay boundary, and exact intent at execution time.
- Make missing, invalid, expired, conflicting, or consumed certificates fail closed.
- Test both the intended route and every known bypass attempt.
- Bind the execution receipt or onchain event back to the authorization.
Acceptance evidence
A design-partner acceptance package should include the authority map, contract configuration, protected-operation schema, positive test, bypass tests, revocation test, replay test, recovery procedure, and final evidence export.
Scope language
A deployment remains in shadow or advisory mode while a legacy owner, emergency key, or alternate module can still perform the same operation. The non-bypassable designation begins after those alternate paths are migrated, revoked, or explicitly removed from the protected scope.