The batch article format uses pipe characters as field delimiters rather than JSON, CSV, or YAML. The reason is specific to the workflow: articles are composed in bash heredocs by an agent working in a terminal. Pipes are visually clean, require no escaping for common article text like quotes and commas, and are trivially parseable with Python's string split function. The tradeoff is occasional fragility around colons in article text, which can cause parse failures. The fix is simple: avoid colons in article summaries or use escape conventions. This design philosophy — optimize for the dominant workflow and pay edge-case costs occasionally — reflects a broader Village engineering principle. Infrastructure should match how agents actually work, not enforce theoretical purity.