Document escrow. The know-how behind the code.

Steps 1 and 2: the exposure and the shift, for documentation. Production asks four questions ("What happens if operational knowledge isn't accessible?"…) and closes with "Losing documentation means losing the context, clarity, and instructions your software needs". The point is kept, calmly: recovery that depends on a few people's memory is slow. Production's "Essential documentation is stored independently and always accessible when needed" is an absolute and is gone.

Steps 3 and 4: from the wiki to the proof. Documentation kept in a repository arrives with the code; ShareFile has an integration page in the kit. ShareFile is a manual integration (an upload folder), so it is no longer described as syncing daily, which contradicted its own page. "50+ integrations" is production's figure, kept and flagged (agreed: production stats stay, flagged). The hub has setup pages for 24 platforms and production's grid shows 40, so Product must confirm the real count.md. "Sync daily" is a production claim, flagged. The proof steps are confirmed facts: an automated check with a vault report and a Software Resilience Certificate with every protection; on Escrow Pro, Resilience Pro and Continuity Pro, Agentic Verification (the Codekeeper AI Verification Lab, no vendor help, hours, missing items flagged, monitoring between runs). The ladder is the agreed proof ladder, kept short; its last line keeps the agreed wording on release rights. A rebuild writes up the build steps it followed, which is a confirmed deliverable; the page doesn't claim the agents grade the documentation. The real test of documentation is a team without the original developers, which is the Exit Exercise, so step 4 says that. 16 Oct: Continuity Pro added; base Continuity no longer includes Agentic Verification, so the Recoverability Certificate rung names Continuity Pro.

Close the loop on the story: one application, eight kinds of material. Production's "Cover your full software infrastructure" block links to only two to five of the other asset pages, and files them under three old products (Software, SaaS and Continuity Escrow). Here all eight appear in the same order on every page, with this one marked, because one application usually needs several of them to come back. The order follows a recovery: what it's built from, how it's built, what it runs on, how to run it, what it calls, the thinking behind it, where it runs and the keys to it. The names match the footer. The links underneath go to the application pages, which say which materials each application type usually deposits, and to the guides hub instead of production's per-page e-book block.