Context
A brand-new miner identity making its first PR against an unfamiliar repo is, from the maintainer's point of view, indistinguishable from a spam or low-effort account — there is no way to signal that the submitting identity has a track record without either the maintainer trusting the gate blindly or the miner leaking internal scoring detail it should never expose. The miner design already treats reward-MERGED-net-positive as an internal outcome measure and keeps trust/reward internals server-side; none of that is meant to be surfaced externally. What is missing is a small, portable, non-gameable summary a miner can present on first contact — in the PR body or an initial comment — that gives an unfamiliar maintainer a fast, honest read on whether this identity has a real history, without exposing anything about how the miner is scored or ranked internally.
Goal
Define and compute a portable, client-side track-record summary — net-positive merge rate, tenure, and a zero-code-of-conduct-incidents attestation — that a miner can present to a maintainer on first contact.
Requirements
- Compute the summary entirely from real, verifiable, already-public outcomes (the miner's own merged/closed PR history and any public moderation/ban record), never from internal scoring, reward, or trust-weight state.
- Net-positive merge rate must be computed from actual PR outcomes (merged vs closed-without-merge) attributable to the miner's identity, not a self-reported or self-attested number.
- Tenure must be derived from a verifiable start point (for example, first recorded claim or first merged PR timestamp), not a value the miner can set arbitrarily.
- The zero-code-of-conduct-incidents claim must be checked against the existing banned-contributors/moderation record rather than asserted unconditionally; if the miner has any such incident, the summary must not claim a clean record.
- The summary must not include or imply any trust score, reward value, ranking, or other internal metric — this is a hard boundary already established for anything client-facing.
- Format the summary as a short, deterministic block suitable for inclusion in a PR description or first comment, generated client-side by the miner runtime (not fetched from a server call that could be spoofed independently of real outcomes).
- Make inclusion configurable per miner (some operators may prefer not to self-report at all) rather than mandatory.
Deliverables
Expected outcomes
- Maintainers unfamiliar with a given miner identity have a verifiable first-contact trust signal without any internal scoring exposure
- Zero instances of internal trust/reward field names appearing in any rendered summary, enforced by the boundary test
Context
A brand-new miner identity making its first PR against an unfamiliar repo is, from the maintainer's point of view, indistinguishable from a spam or low-effort account — there is no way to signal that the submitting identity has a track record without either the maintainer trusting the gate blindly or the miner leaking internal scoring detail it should never expose. The miner design already treats reward-MERGED-net-positive as an internal outcome measure and keeps trust/reward internals server-side; none of that is meant to be surfaced externally. What is missing is a small, portable, non-gameable summary a miner can present on first contact — in the PR body or an initial comment — that gives an unfamiliar maintainer a fast, honest read on whether this identity has a real history, without exposing anything about how the miner is scored or ranked internally.
Goal
Define and compute a portable, client-side track-record summary — net-positive merge rate, tenure, and a zero-code-of-conduct-incidents attestation — that a miner can present to a maintainer on first contact.
Requirements
Deliverables
Expected outcomes