Coding Systems and Obfuscation
Simple Ciphers: Replace letters with symbols or shift them by a certain number. While not spy-level encryption, it deters casual readers.
Contextual Codes: Use everyday words to represent places or people. “Going to the orchard” might mean “Meet at the second cache.” Without knowing the codebook, it’s innocuous.
Layered Meanings: A single message could have a literal reading and a hidden meaning. Only those you’ve trained in interpreting the code understand the hidden instructions.
Regularly change the meaning of your code words. If “apple” once meant “north,” next month make it mean “west.” This rotation keeps outsiders guessing.
Digital Data Safeguards
Encryption Tools (If Accessible): If you have a working device, use offline encryption software to password-protect files. Keep keys or passphrases in your head, not written down.
Minimal Digital Footprint: Avoid broadcasting sensitive details via radios, phones, or any network that could be intercepted. The best digital security often means using digital communication sparingly.
Regularly Change Access Keys: If multiple people must access a device or file, rotate passwords or keys. If someone is captured or turns traitor, changing keys locks them out.
If you must store digital maps or notes, break them into separate encrypted files. Without all the pieces and keys, adversaries get only partial, useless data.
User-Friendly Navigation
Start Pages and Landing Screens: If using an e-ink reader or a simple tablet, have a dedicated “START_HERE.txt” file to guide newcomers.
Offer a brief primer on how your files are organized, what formats they’re in, and how to open them.
Plain Language Descriptions: Keep directories named simply: “MEDICINE_FIRSTAID,” “FOOD_GROWING,” “WATER_PURIFICATION.”
Avoid cryptic abbreviations. Clear names speed learning and retrieval.
Versioning and Updates: Keep old versions of documents in an “Archive_Old” folder if they might still have value. For critical docs, note changes in a “Changelog.txt.”
Color Coding (If Using Icons): If your device supports colored icons or tags, assign colors for urgency (e.g., red for emergency guides, green for sustainable practices).
Testing Your Backup System
Simulate Loss: Imagine your main camp burns down. Can you still retrieve essential data from a remote cache? Test the scenario. This ensures your backup plan is functional, not just theoretical.
Cross-Platform Compatibility: Ensure your documents can be read on different operating systems or even on simpler devices (e.g., e-readers for PDFs).
Keep a Low-Power Reader Device: A cheap, low-power e-ink reader or old tablet dedicated just for reading stored documents conserves battery and offers a stable reading platform.
As you gather more data, update backups accordingly. Refresh old media after a few years —magnetic drives degrade, optical discs fade. Remain flexible: if you find a better storage medium or more durable format, migrate your data. Your methods should evolve as you discover what works best in your environment and as your library grows in scope and depth.
Formats for Knowledge Preservation: Practical Notes
Pre-Reading Testing: Before final storage, open each file in a minimal viewer (like a text editor for txt, universal image viewer for png) to confirm accessibility. Audio Record Key Instructions: Audio recordings on stable digital formats: if reading screens fail, audio can still transmit instructions, requiring only a player and speaker/headphones. Periodic Refreshing: Every few years, migrate data to fresh media—like copying from an old USB stick to a new one—to prevent bitrot.
Universal Access Codes: Store a sheet explaining file extensions and how to interpret them—future generations might need a crash course in what “.pdf” means. Stone or Clay Tablets: Extremely low-tech and permanent—if you can inscribe essential steps onto clay tablets and bake them, they rival metal plates in durability. Multiple Layers of Redundancy: Don’t rely solely on digital—if it’s extremely important, have a paper version, a digital version, and maybe a microfilm copy.
Test access and recovery together
Trace an important record from creation to backup and deletion. Identify authorized users and what happens if the device, account, or custodian becomes unavailable. Protect sensitive information while ensuring authorized people have a workable recovery process.
Test recovery with a non-sensitive sample. Confirm the copy opens, instructions are understandable, and required credentials can be retrieved through the agreed process. Keep public coordination information separate from private records. When roles change, update permissions and recovery details together. Security that blocks unauthorized use but also permanently prevents intended users from reaching essential records has not solved the full problem. Document the successful test and when it should be repeated.