Suggest an Expedition

What qualifies

The Archaeologist covers two kinds of entries. For repositories: open-source projects with a genuine architectural story — infrastructure, developer tooling, ML systems, compilers, databases. The kind of codebase where reading the structure teaches you something about the problem domain, not just the syntax.

For engineering blogs: publications with a real RSS feed, a consistent technical voice, and a track record of posts that age well. Company blogs that write honestly about trade-offs, not just product launches.

What we skip

• Tutorial repos or demo code — no architectural depth to excavate
• Blogs without RSS or with paywalled full-text
• Projects under 500 lines — too thin for a meaningful narrative
• Anything primarily a landing page with a small code appendix

How to submit

Open a GitHub issue with the URL, type (repo or blog), and a sentence on why it’s interesting. The pipeline runs manually for new entries — turnaround is usually within a week.