## The problem

Professional identity is fragmenting.

People publish on LinkedIn, GitHub, personal sites, newsletters, short-form video, podcasts, and private communities. AI agents are starting to read those surfaces, summarize them, and make recommendations from partial context. The result is noisy for humans and brittle for machines.

SourceLink starts from a simple claim: professionals need a canonical source of truth that works for both people and AI systems.

If discovery is increasingly mediated by search, recommendations, agents, and social proof scattered across platforms, then a professional profile is no longer only a resume. It is part of how trust is assembled before a conversation starts.

## The initial positioning

SourceLink.pro is professional identity for the AI era.

It should help a person express who they are, what they have built, what they are available for, and which sources should be trusted. It should not be another social network. It should behave more like an identity layer, a structured profile, and a machine-readable context bundle.

The positioning should stay practical. The product is not “personal branding” in the vague sense. It is a way to make reputation more inspectable: proof of work, current offers, credible links, and a compact explanation of why this person is relevant to a specific problem.

## Who it is for first

The first users are likely independent technical people: engineers, consultants, fractional leaders, founders, and creators with meaningful public work spread across too many surfaces.

They already understand reputation. They already have artifacts. Their problem is not lack of activity. Their problem is coherence.

They also tend to grow through small communities and warm trust: referrals, niche Slack groups, open-source circles, founder networks, client introductions, and repeated public work. SourceLink should not fight that pattern. It should make those signals easier to organize and share.

## What has to be true

The product has to make the profile useful before a network exists. It also has to create a reason for the profile to stay current.

That means the first version should probably emphasize canonical links, structured context, readable summaries, proof of work, and AI-consumable exports. Distribution can come later, but utility cannot.

## What the profile has to do

A useful profile should reduce ambiguity.

It should help a visitor answer four questions quickly: what does this person understand, what can they help with, what evidence supports that claim, and what is the next reasonable step?

Those questions are product questions as much as public-context questions. If the profile cannot answer them, no amount of reach will fix the confusion.