skip to content

Proof of Work — your verified developer credential

Your code is your résumé. Proof of Work is a credential computed from real, merged contributions — never a self-reported skill list, and never something you fill out.

Where it lives

Every developer who publishes their profile gets a page at terminalhire.com/r/<your-github-login> — a public, verifiable, printable résumé built entirely from third-party-attested work.

What's on it

  • Headline. A role + specialization + top stacks derived from your verified contributions — e.g. "Senior Backend Engineer · Distributed systems · Go, Postgres." No dominant signal, no invented title: it honestly falls back to a generic role rather than guessing.
  • Verified skill chips. Domains you have merged, substantive pull requests in, ranked by volume.
  • Recency. A live/dormant signal from your most recent qualifying merge — so the credential reflects work you're doing now, not a snapshot from years ago.
  • Proof of Work badge. An auditable count — merged PRs and distinct external organizations — next to the eligibility bar those merges cleared.
  • Proof sentence. A plain-language claim like "12 substantive PRs merged into at least 4 external orgs — most recent 6d ago."

Why third-party-attested, not self-reported

Anyone can list a skill. Far harder to fake is a pull request accepted into a project you don't control — merged in the open, into an external codebase, and auditable back to the source. No single merge proves everything on its own, which is why the credential leans on the pattern: substantive PRs accepted across distinct organizations you don't own, cleared against an eligibility bar rather than taken on trust. That's also why it never inflates silently: work it can't verify shows "could not verify," never a fabricated zero.

Synthesized narratives

Per-repository dossiers may include a short AI-synthesized narrative — a thesis sentence, a review-decision summary, graded competencies, and a one-line résumé bullet. It is derived exclusively from the deterministic evidence already on the page (identity-free structured facts: counts, enums, timestamps, pseudonymous review classes). No new facts are introduced, no free-text comments are read, and no person is named. Every synthesized element is grounded in a specific piece of that evidence and adversarially re-checked against it; anything not fully supported is dropped rather than shown. Synthesized content is labelled as such on the page, so it is never mistaken for a raw, third-party-attested signal.

Publishing

Your /r/<login> page renders only once you've explicitly published your profile — until then, the URL 404s, identically to a login that doesn't exist at all. Nothing about who has an account is discoverable from the page itself.

Where it connects

Your Proof of Work credential is the foundation the rest of Terminalhire builds on: it's what recruiters see, what other developers match against in connect, and what bounty claims feed into over time as your merged-PR history grows.