Live
Public work
Source links, repos, work samples, and measurable outcomes attached to a claim.
TrueHire proof project
Your resume can be tailored. Your work still has to prove itself.
TrueHire stays as the credibility layer under RolePatch: costly signals, source-backed proof, and recruiter-ready evidence that users control before anything reaches an application.
Proof profile
Candidate credibility
88
sourced
Public sourcelinked
github.com/acme/checkout
Outcomemeasured
31% faster onboarding
Receipt boundarylocked
private until attached
No auto-share boundary
Proof moves into packets, receipts, or replies only after explicit user review.
Candidate proof profile
88
source-backed score
derived from public work and confirmed signals
Sources
12
links preserved
Claims
7
packet candidates
Sharing
opt-in
never automatic
Claim
Reduced onboarding time by 31%
Outcome, role, and source link stay together.
Evidence
Launch report, metrics screenshot, manager reference
Visible as review material before packet copy.
Receipt
Source included only after user-controlled sharing
Audit trail records what was available and what stayed private.
Costly signals over cheap claims
Keep the proof brand clean.
RolePatch should stay focused on applying. TrueHire should keep the sharper promise: evidence first, deterministic sources, and proof that is harder to fake than a rewritten resume.
Next
Employer verification
Confirmed roles and references stay in TrueHire until a consented bridge is ready.
Planned
Application proof
RolePatch packets can carry selected proof without rewriting the resume.
Planned
Recruiter evidence
Replies can reference proof only when the recruiter asks and the user opts in.
Derived, not declared
Proof should explain where trust came from.
This separate project path lets TrueHire keep its evidence-first voice while RolePatch uses the proof only at the moments that matter: evidence cleanup, packet review, receipt audit, and recruiter follow-up.
Derived, not declared
A proof record should point back to source material instead of asking candidates to decorate a claim.
Private until attached
RolePatch can preview and import proof, but applications only receive it through explicit user action.
Every number needs a source
Scores, receipts, and proof status stay inspectable so recruiters can audit the basis of a claim.
Separate by default
One ecosystem, two jobs.
This avoids confusing users with two dashboards. TrueHire is the public proof lane; RolePatch is the private workflow lane.
- 1TrueHire remains the proof front door and brand lane.
- 2RolePatch remains the private application operating surface.
- 3Imported proof becomes achievement evidence first, not automatic employer-facing content.
- 4Packets and receipts preserve source links for user-controlled sharing.
Your proof packet
Preview what can be shared.
This preview uses your existing achievement evidence. Items remain private and user-provided until you attach them to an application packet or a later verification flow ships.
0
Shareable
0
Needs work
No proof evidence yet
Add quantified achievements first, then return here to preview candidate proof packets.
Add evidenceTrueHire import preview
Inspect proof before any merge.
Paste a TrueHire handle to preview public score evidence and confirmed work history as RolePatch proof items. Previewing is read-only; importing saves private evidence for your review and still does not share anything.