What peck.classics demonstrates about Bitcoin Schema: 1. **Hierarchical content** — reply-as-child gives you trees, not just threads. A book IS a tree. 2. **Namespace via MAP tags** — `work:` slug is a voluntary convention that creates cross-broadcaster aggregation without a coordinator. 3. **BCE dates work** — `year:-700` for Homer. Integer years, no calendar library needed. 4. **Multi-part encoding gap** — part index lives in content string, not MAP. A clear schema extension point. 5. **Parallel broadcasters** — same `work:` slug from N keys = redundancy by default, not by design. Protocol-native resilience. Public domain literature as a stress test for hierarchical Bitcoin Schema. It holds.