No. 01
Submit.
Drop your repository URL. Our parser reads your readme so you don't re-write it. Add a cover, pick a category, done in under two minutes.
Vol. I · MMXXVI
A Registry
Where
Engineering
Finds Its
Audience.
A curated registry of engineering work — where builders are read, and readers find builders. No infinite scroll. No trending tabs. Just projects worth publishing.
Currently Featured
—
Awaiting publication
Published Projects
—
Builders
—
Review Standard
Human
Submissions
Open
Loading the index…
Loading the index…
Loading the index…
02 — The Process
II.
From readme
to registry.
Three steps, reviewed by editors. No ranking games, no engagement metrics. If your work teaches, we publish it.
No. 02
Review.
Editors read for clarity, technical honesty, and scope. No vanity work. If the readme lies, it doesn't ship. If it teaches, it does.
No. 03
Publish.
Your project enters the index — discoverable by peers, visible to people hiring, and credited to your name. Forever, not for 48 hours.
03 — The Tenets
III.
What we
publish.
Editor's Note
"Most platforms reward what performs. We publish what holds up. These tenets explain why a project gets in — and why most don't."
-
01
Engineering, not marketing.
We publish the decisions, the trade-offs, and the failure modes — not the launch tweet.
-
02
Depth over polish.
A rough schematic that teaches beats a glossy render that doesn't. We optimize for what you can learn from the work.
-
03
Readmes for peers.
Write for the engineer who'll actually try to reproduce it. HR departments read later, not first.
-
04
Credit is permanent.
Your byline stays on your work. No feed decay, no algorithmic burial. The index is forever.
-
05
No ranking games.
We don't sort by likes, trends, or time. Readers browse the index; editors choose what's featured. That's it.
Submissions Open
Have something
worth publishing?
If you built it with care, reviewed it honestly, and think another engineer might learn from it — send it in. We read every submission. We publish the ones that teach.