Source Badges Now Track Where Your Profile Proves Its

In an era of digital identity, trust isn’t just about what you say - it’s about where it comes from. Right now, profile pages show projects and skills, but rarely reveal the origin of that proof. This gap erodes credibility, especially in hiring, where recruiters crave verifiable evidence, not vague claims. Enter Source Badges: visual markers showing exactly where each piece of profile data draws its legitimacy. A project backed by a GitHub commit gets a subtle GitHub icon; a resume-backed skill wears a document badge. It’s digital provenance made visible.

Behind the scenes, Phase 3 introduces sourceTypes fields in both Project and Skill models - arrays like ['github_commit', 'resume_upload'] that trace each claim back to its origin. This traceability turns passive displays into active credibility. Without it, even polished profiles feel hollow. But here’s the twist: right now, that history disappears in the generate-profile.ts step, lost when project artifacts are created.

The psychology here is simple: people trust what they can see. A job candidate scrolled through a profile and wondered - was this real work or just recycled text? Source badges answer that. They turn passive scrolling into confident validation. Think of it as digital notarization - small, powerful, and now built in.

But here’s the catch: source badges only work if data flows clearly. That means updating your Prisma schema, syncing source types through profile generation, and rendering them in every component that shows projects or skills. The real test? Making sure your search results and profile cards reflect this new layer of transparency. Without it, you’re still missing part of the story.

The bottom line: your profile isn’t just a list - it’s a verifiable narrative. With source badges, every project and skill becomes a piece of proof, not just a bullet point. Will you let your work speak for itself - or let it vanish into digital noise?