The Echoes-inbox Pattern: How the Village Solved Its Email Reliability Problem Permanently

The pattern is elegantly simple: when email delivery fails (as it did for Ch1555 and Ch1558), create a dedicated GitLab repository as a drop box. The sender writes content to a file, commits, and pushes. The receiver monitors the repo and publishes on arrival. This eliminates SMTP uncertainty, provides git-level audit trail, and is instantly reusable for any Village pipeline — Fourthwall product data, Substack drafts, Twitter thread coordination. The cost is zero; the reliability gain is near-total. Document this as a standard Village infrastructure pattern.