You develop people — a college cohort, or your own team. Proof turns that into something a network of founders and leaders can read: the task you set, the work they did, your name on it.
Why you're hereA college cohort or a team of your own — the people you back grow in private. The network that hires never sees them. Your word lives in a WhatsApp thread: it can't be read, and it can't be checked.
↓so put it on the record
What a mentor doesGive one scoped task. Read what they build. Put your name on it — and plug them into the network that reads.
Your wordNotA reference nobody can check
ButA record: work they did, your name on it
↓the four moves · all on /mentor
1 · AddAdd an engineer by their Proof email. They sign up to Proof first — then you add them. RK pairs your first one; after that you add the rest yourself.
2 · AssignOne scoped task per engineer — a title, a short brief, an optional link, an optional due date. They see it the moment they open Proof.
3 · ReviewWhen they submit, read it, write feedback, mark it done. They can reply to what you wrote — the back-and-forth stays on the record.
4 · VouchOn finished work: a specific note, plus the shadow line — what you almost didn't see. It waits in their inbox; they publish it or challenge it.
↓where the work goes
The power of the networkYour people stop being a private list — they join a network that reads. 48+ founders and leaders reach out when hiring; RK curates the strongest logs. Students get read without a campus visit; your own team builds judgment daily, read by name only when they choose.
The promise to your peopleNamed only when they choose. Until then every writer is anonymized as #ZME-NNN — the founder reads the work, not the name.
↓what protects everyone
The rulesEngineers only — not founders, not yourself. They sign up first; no invite emails, so no one is brought in who didn't join themselves. The vouch is theirs to publish, hide, or challenge. You read and reply — you never edit their log.
StartRK pairs you with your first engineer. Open /mentor, give them a task, then add the rest of the people you back yourself.
To be a mentor
RK pairs you with your first engineer — trust-based, no public signup.
A professor, a community lead, a team lead, an experienced engineer — anyone who develops people.
To be a mentee
Any engineer on Proof — student or working, MCA to self-taught.
They sign up themselves first. Not founders, not yourself.
Does it cost anything?
No — free for you and your engineers.
How many engineers can I mentor?
As many as you bring. RK pairs the first; you add the rest yourself, by email.
Can I see other mentors' engineers?
No — only the engineers linked to you.
What does my engineer agree to?
They joined Proof themselves and accepted that logs get read. Mentoring adds assign, review, and vouch — their privacy doesn't change.
Can I edit their log, or make a vouch public myself?
No. Their words stay theirs; the vouch is theirs to publish, hide, or challenge.
Need to remove an engineer?
Ask RK — link changes go through RK for now.