# Recovery Capability Matrix ## Identification A proposed inventory of the distinct capabilities required for account, data, operating-system, firmware, network, and human-escalation recovery. ## Notebook evidence - [[Scanned_20260730-1719#PDF page 13 — Lost-access inventory|PDF page 13: Lost-access inventory]] — This is a blast-radius inventory: which capabilities disappear when identity or credentials fail. The list reveals that account recovery was not one service problem but a cross-platform continuity problem affecting phone numbers, publishing, audience access, source code, and stored credentials/cards. - [[Scanned_20260730-1719#PDF page 20 — macOS recovery and command-line tool inventory|PDF page 20: macOS recovery and command-line tool inventory]] — This is a rescue-shell vocabulary sheet: the commands most useful when the graphical system is unavailable or a disk, account, boot state, or network must be diagnosed from Recovery. - [[Scanned_20260730-1719#PDF page 27 — EWF forensics, libyal, GNS3, telecom signaling, and partition flags|PDF page 27: EWF forensics, libyal, GNS3, telecom signaling, and partition flags]] — The author is joining preservation and emulation. A disk image can be captured in a forensic format, mounted with open tooling, and then examined or booted in a virtual/network lab. The telecom fragments may be candidate protocols for that lab rather than observed traffic. - [[Scanned_20260730-1719#PDF page 33 — Libreboot, Chromebook firmware resources, mobile Linux, and disk archives|PDF page 33: Libreboot, Chromebook firmware resources, mobile Linux, and disk archives]] — The author is identifying projects that remove vendor firmware or mobile-OS dependence while retaining recoverable archives. The page joins laptop firmware freedom, mobile Linux, and portable backup. - [[Scanned_20260730-1719#PDF page 56 — Apple startup modes and a mistaken SIP command|PDF page 56: Apple startup modes and a mistaken SIP command]] — The page is a boot-access cheat sheet, but it also illustrates a dangerous category error: Gatekeeper, SIP, single-user mode, and firmware startup modes are distinct controls. - [[Scanned_20260730-1719#PDF page 57 — Mac NVRAM/SMC resets, safe boot, startup manager, and diagnostics|PDF page 57: Mac NVRAM/SMC resets, safe boot, startup manager, and diagnostics]] — The page is an attempted fault-isolation ladder: reset persistent settings, reset hardware management, boot minimally, choose another disk, then test hardware. Some shortcuts have been merged incorrectly. - [[Scanned_20260730-1719#PDF page 71 — Mac lock-screen, hashes, startup keys, NVRAM, and virtualization|PDF page 71: Mac lock-screen, hashes, startup keys, NVRAM, and virtualization]] — The author is trying to relate firmware reset, boot access, password/account recovery, and a VirtualBox/Java workspace. The page is mnemonic, not a verified runbook. - [[Scanned_20260730-1719#PDF page 72 — Single-user mode and root filesystem repair|PDF page 72: Single-user mode and root filesystem repair]] — This is the endpoint of the Apple shortcut pages: once single-user mode is reached, check the filesystem and make the root writable so repairs can be attempted. ## Relationships and overlays The source places this note in a shared evidence cluster with [[Base Station System Application Part|Base Station System Application Part]] · [[Buffer|Buffer]] · [[Catima|Catima]] · [[DAR|DAR]] · [[Expert Witness Compression Format|Expert Witness Compression Format]] · [[Facebook|Facebook]] · [[Gemini PDA|Gemini PDA]] · [[GitHub|GitHub]] · [[GNS3|GNS3]] · [[Google Fi|Google Fi]] · [[libewf|libewf]] · [[Libreboot|Libreboot]] · [[macOS Recovery|macOS Recovery]] · [[MagicJack|MagicJack]] · [[Mailchimp|Mailchimp]] · [[Mint Mobile|Mint Mobile]] · [[MrChromebox Firmware Utility Script|MrChromebox Firmware Utility Script]] · [[NVRAM|NVRAM]]. Within the larger collection, this evidence extends [[Vendor-Agnostic Recovery|vendor-agnostic recovery]] and [[Continuity Architecture|continuity architecture]] by showing how software, hardware, identity, and pre-OS control depend on recoverable interfaces. ## Evidentiary status and open leads Build a recovery matrix with service, owner identity, recovery channel, MFA method, export path, and current status. That operational artifact is missing from the notebook. ## Source - [[Scanned_20260730-1719|Scanned_20260730-1719]]