§ 01 — The problem
We rebuild the same things, forever.
At any moment, thousands of developers are writing login forms. Hundreds of designers are recreating the same dashboard layout. Hundreds of teachers are writing the same intro-to-statistics lesson. Researchers are producing the same survey methodology. Writers are prompting the same boilerplate. AI sessions are spending tokens producing things that already exist — somewhere, on someone's hard drive, in some repo nobody has found.
This isn't a human failing. It's a discovery failure. The work exists. It's just invisible.
The problem is that nobody can find it."
Package registries solve this for libraries. But for full apps, templates, scaffolds, and AI-generated projects — there's nothing. You either build from scratch or spend hours digging through GitHub search hoping someone else had the same idea.
§ 02 — What d4not library is
An index. Not a host.
d4not library is not a marketplace. Not a CDN. Not a package manager. It's a curated index of reusable work — the same way a library catalogue indexes books without storing them. Authors keep their work in their own repos and platforms. d4not library keeps the pointers.
Code is the first category because programmers were the first audience. But the model works for anything: a design system, a research methodology, a lesson plan, a business-process template, a prompt that reliably produces what you need. The index is expanding — slowly, honestly, one surface at a time.
Every entry has: a category, an origin (human / AI / hybrid), a license, and a trust rating. Links point out to the original repo. d4not library does not host. d4not library does not lock anything behind a subscription.
§ 03 — The rules for contributors
What we ask when you submit a link.
- Link only to repos you authored or have rights to share.
- Carry a real open-source license — no license = no index entry.
- Be honest about origin: AI-built, hand-crafted, or hybrid.
- Keep your repo public for as long as d4not library indexes it.
- Don't submit malware, wrappers that call home, or telemetry payloads without disclosure.
- Accept that d4not library may un-index your project if it violates these rules or turns malicious.
§ 04 — Why AI-built projects belong here
The origin doesn't matter. The utility does.
If a Claude session produces a working Tauri app and the author publishes it under MIT, that app is real software. It can be audited, forked, improved. The tokens spent producing it are already gone. Spending them again — by everyone who needs the same app — is the waste we're trying to prevent.
The AI-built badge isn't a warning. It's context. It tells you what tools were involved and suggests you should read the code with the same attention you'd give any new dependency.
§ 05 — Where d4not library is today
Honest status report.
d4not library is a public beta. Right now the index contains a single real project: Sistema-Propinas, a small Node/Express tips tracker. One maintainer — me, @d4not — built the site and reviews every submission personally, slowly. Trust badges, the forum, account signups, and project pages all work; data may be reset during development.
Things you'll see promised on other pages that do not exist yet: an automated dependency scanner (Phase 2), a community reviewer program (Phase 2), the "For everyone" surfaces like Prompt library or Design index (Phase 3+), recurring donations, a custom domain, email notifications. Every one is on the roadmap. None is live.
If you want to help: submit the first non-code index entry, file a bug, or just tell someone. The best thing for the index right now is more real links in it.