Continuity without dependency

This independent project exists because business-critical information should not be recoverable only through one AI agent, one chat history, or one account.

Safety boundaries

• Never put credentials in GitHub, issues, chat, or the website worksheet.
• Store real secrets in an encrypted vault with human-held recovery access.
• Use the inventory for metadata and procedures only.
• Rotate a credential through its issuing provider if exposure is possible.
• Do not interpret a lockout as proof of theft or compromise without evidence.

Evidence labels

User-reported means an account holder described it. Verified means a dated source or reproducible test supports it. Unknown means the available material does not establish it.

Contributing

Improve templates, accessibility, documentation, and tests. Redact all examples. Read the repository SECURITY.md file before opening an issue.