docs(miner-selfimprove): self-improve phase design note — calibration, value-weighting, anti-farming boundaries (#4265)

[davion-knight]

Adds packages/gittensory-miner/docs/miner-selfimprove-calibration.md — the Phase 7 self-improve design note, written for a contributor who has only the contributor-safe tools (drift detector, calibration dashboard, prediction ledger, metrics exporter, extension panel, regression tests) and needs to understand where the read-only-measurement / maintainer-only-enforcement line is and why.

Covers the five required points

• What calibration measures — the Phase7CalibrationLoopResult contract combining historical_replay + pr_outcome against the documented 0.62 baseline, and computeGateEval's confusion matrix (GateEvalRow; mergeFalse = the dangerous error) as ground truth.
• Value-weighting — why weighted precision (REVERSAL_DISCOUNT_WEIGHT, currently 0) measures durable correctness, not volume: a reverted merge earns no credit; the denominator is unchanged.
• Personalized tuning (maintainer: personalized gate-prediction tuning per contributor/miner history #2349) — maintainer-only; why a contributor-safe surface must never see or influence its own trust score.
• Fleet anti-farming (maintainer: fleet-wide anti-farming detector — flag a miner/fleet gaming the calibration score #2350) — the gaming vectors (trivially-safe PRs inflating precision, farming duplicate-claim elections) that make every contributor-safe tool read-only/local-only by design.
• Calibration-gated circuit-breaking (maintainer: wire calibration accuracy into the live auto-tune circuit-breaker for miner-originated PRs #2352) — auto-tune.ts's existing hold-only breaker (only ever more cautious, never loosens); enforcement stays maintainer-only.

Plus an explicit "what this phase does NOT do" section (no autonomy-level or gate-threshold changes; no writes to maintainer-owned calibration/circuit-breaker state) and cross-links to #2348/#2349/#2350/#2352 for context (not to be reopened).

Accuracy

Prose design note under docs/ (matching the coding-agent-driver.md / cross-repo-discovery-phase1.md convention). Every referenced symbol — DOCUMENTED_CALIBRATION_BASELINE, GateEvalRow, REVERSAL_DISCOUNT_WEIGHT, the auto-tune hold-only breaker — verified against the source; relative links resolve; docs:drift-check stays green (prose isn't a tracked surface).

Closes #4265

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[loopover-orb]

Tip

🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩

✅ Gittensory review result - approve/merge recommended

_{Review updated: 2026-07-09 21:05:02 UTC}

1 file · 1 AI reviewer · no blockers · readiness 100/100 · CI green · clean

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
This is a docs-only addition (packages/gittensory-miner/docs/miner-selfimprove-calibration.md) explaining the contributor-safe vs. maintainer-only boundary for the Phase 7 self-improve calibration work. Every checkable claim matches the provided src/review/parity.ts source exactly — GateEvalRow's mergeFalse/closeFalse fields, weightedMergeConfirmed/weightedCloseConfirmed, and REVERSAL_DISCOUNT_WEIGHT = 0 with the 'denominator unchanged, only credit discounted' framing. No code, schema, or migration surface is touched, and CI is green. The PR title links #4265 and the note explicitly scopes itself to read-only contributor-safe tools while marking #2348/#2349/#2350/#2352 as context-only, consistent with the anti-scope-creep convention.

Nits — 4 non-blocking

• The doc makes specific claims about src/review/auto-tune.ts's hold-only breaker and src/selfhost/orb-collector.ts's HMAC-with-local-secret scheme that weren't in the provided excerpts — worth a maintainer spot-check that those files still match before merge, since a stale design note is worse than none.
• The description claims 'relative links resolve' and docs:drift-check passes, but that's asserted rather than shown in the diff itself — low risk since CI is green and would likely catch broken relative links.
• Nothing structural to change; if a maintainer wants extra rigor, spot-check the auto-tune.ts and orb-collector.ts claims against current source before merge since this note isn't auto-validated against those files' logic (only links).
• Diff looks like trivial or whitespace-only churn — Reduce whitespace-only or formatting-only churn and keep the diff focused on substantive changes.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ Linked	#4265
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	✅ 20/20	Low review scope from cached public metadata (1 linked issue).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 89 registered-repo PR(s), 53 merged, 3 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	davion-knight; Gittensor profile; 89 PR(s), 3 issue(s).
Gate result	✅ Passing	No configured blocker found.

Review context

• Author: davion-knight
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: not available
• Official Gittensor activity: 89 PR(s), 3 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Keep the PR focused and include validation evidence before maintainer review.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

• Re-run Gittensory review

[loopover-orb]

Gittensory approves — the gate is satisfied and CI is green.