Boundary-led profile
Show open lanes, not-a-fit rules, availability, and required context before someone starts a request.
Introducing structured access
Meet your access layer. Reach the professional behind the profile.
SourceLink turns professional inbound into a bounded path: public terms, guided context, and private review without social noise.
Incoming requestContext complete
Intent, timing, open lane, and boundary fit are ready for review.
- Profile terms
- Public
- Guided request
- Required
- Private review
- Private
Built around controlled professional access
Public cardGuided requestOwner reviewFirst-party analyticsAvailability rulesPrivate briefsBoundary controlsCanonical profile
Empower inbound with context
Ask for intent, timing, constraints, and fit before access reaches the owner.
Guided request intake
Ask for intent, timing, scope, and constraints while the requester still has attention and context.
FitPending…
Private review brief
Turn inbound into a concise owner-side brief with fit signals and missing details.
First-party visibility
Track profile views and request conversion without feeds, follower counts, or third-party analytics.
SourceLink is not another place to perform. It is a private path for serious opportunities to arrive with context and boundaries.
Simple. Bounded. Private.
Discover how SourceLink turns a profile visit into a reviewable request.
- 01
Publish access terms
A SourceLink Card states what the professional is open to, what is not a fit, and what context is required.
- 02
Capture the request
The requester explains why they are reaching out, what they need, and when they need it.
- 03
Prepare the brief
Structured answers become a private review surface for the professional behind the profile.
- 04
Improve the rules
Owners can adjust availability and boundaries without turning inbound into a public performance loop.
Built for controlled access
Where professional boundaries meet private request handling, designed to reduce inbound overload.
Access before attention
The requester sees boundaries before sending anything, which keeps low-fit outreach from becoming review work.
Private by default
Requests are reviewed behind the profile without public threads, comments, likes, or reputation pressure.
Access that scales with reach
Pick the surface you want to inspect first. No pricing, billing, or public social mechanics are part of v0.
Visible
For professionals who want their access terms discoverable.
- Public profile URL
- Open lanes
- Not-a-fit rules
Selective
For tagged mentions and profile visitors that should start with structured context.
- Intent capture
- Timing and scope
- Private owner brief
Private
For managing profile data, requests, routing, and availability.
- Canonical profile
- Request queue
- First-party analytics
Requests become review work
Sample inbound briefs show how context, fit, and missing details stay private.
Founder needs diligence support for a fintech launch in Q3. Budget range still missing.
Operator wants a warm review path for a logistics partnership with a time-bound pilot.
Event asks for a keynote, but the topic and audience fit need confirmation.
Angel syndicate requests sector feedback and provides scope, timing, and next step.
Recruiter starts with a senior role but conflicts with current not-a-fit rules.
Team provides a project outline, constraints, and why this professional is relevant.
Frequently Asked Questions
Answers to common questions about the SourceLink v0 access layer.
Is SourceLink a social profile?
No. SourceLink is an access layer: a professional card, guided request flow, and private review workspace.
Does the intake rely on live LLM decisions?
No. The v0 intake is deterministic and bounded. It collects requester-provided context and prepares a structured brief.
Can requesters contact the owner directly?
The public path routes them through the profile's access terms and guided request flow before owner review.
What happens to analytics?
SourceLink uses first-party product analytics language for profile views and request conversion, not social engagement metrics.
Where should I start?
Open the example profile, review the access terms, then try the request flow for Alex Rivera.
The cleanest professional profile flow I have seen in a while. The access terms are doing real work.
@alexrivera
This is how profiles should handle context. No guessing, no weird detours, just a clear path.
@alexrivera
Tagged this because the profile card finally explains what someone is open to before you reach out.
@alexrivera
The guided request flow feels obvious in hindsight. Every public professional page should have this.
@alexrivera
Hand-picked this one for the team. The boundary language is sharp without feeling defensive.
@alexrivera
The profile makes fit visible before the message. That is the piece most personal sites miss.
@alexrivera
The access layer idea is strong. Public enough to be useful, bounded enough to stay sane.
@alexrivera
This solves the awkward part of reaching out: what should I include and is this even a fit?
@alexrivera
A good example of making professional access explicit without turning it into a social feed.
@alexrivera
The best part is the ask has to be specific. It changes the tone of the whole interaction.
@alexrivera
Saved this as a reference for profile design. It says what is open, what is not, and why.
@alexrivera
The handoff from public profile to structured request is exactly where this becomes useful.
@alexrivera