01
Inventory
Record services, owners, permissions, recovery links, rotation procedures, and last-tested dates.
No secret valuesIndependent • backup-first • metadata only
Don’t depend on an AI agent to give your business its data back.
Keep an independent, encrypted, regularly tested backup before an agent ever receives access. This kit helps you document what exists, who owns it, and how to recover—without collecting secrets.
Never enter secrets here. This site is not a password manager. Do not enter passwords, API keys, tokens, or other secrets. Payment details and customer data are also prohibited.
The continuity model
Three layers keep one lockout from becoming a business outage.
Separate the inventory, the secret storage, and the recovery evidence.
02
Encrypted vault
Keep actual credentials in a dedicated vault with a human-held recovery path outside any single agent.
Independent control03
Fallback evidence
Maintain redacted procedures, manual alternatives, provider sources, and an incident log.
Tested continuityOffline worksheet
Build a metadata-only inventory
Saved locally in this browser. Nothing is submitted to a server.
Incident tracker
Track elapsed time, not a promised unlock deadline.
This local tracker records follow-ups and recovery actions only.
No incident timer started.
Not started
Support follow-ups
Recovery actions
Evidence over assumptions
Label what you know.
Lockouts and refusals are observable events, not automatic proof of theft.
Source discipline: provider-specific instructions need a source URL and last-verified date. Unknown behavior stays unknown.
Ready for the next incident
Make the fallback boring before it is urgent.
Download the redacted templates from the repository and test them with dummy data.