◆ Dopamint Arena · Product, Lifecycle & Engineering Metrics
Dopamint Arena · Multi-Source Telemetry & Metrics Reference (Jul 5 – Oct 19, 2026)

Dopamint Arena — product, lifecycle & engineering metrics

Objective dataset compiled across Sui Mainnet campaign archives, production AWS inventory & billing, 4,497 Linear issues (DOPAN), 3,891 GitHub PRs, 23,617 GitHub Actions workflow runs, 247 ADRs, 137 formal protocol models, and 35,145 automated tests.

7 core engineers 165 packages (126 Rust · 31 TS · 8 Move) 3,274 Done issues (7,526 Fibonacci pts) 3,693 merged PRs · 4,033 commits 3.11M surviving lines (72% median retention) Jul 5 – Oct 19, 2026
40.61Mpeak TPS
Sui Mainnet 15s peak across 30 bare-metal servers (15.24B txns · 7,680 / 7,680 settled tunnels · 0 failed)
6 / 7+38d vs target
tracks completed Oct 19 vs. Sep 11 target (52.1% of tickets created after Sep 11 · 1 track in backlog)
3,274Done issues
7,526 Fibonacci points out of 4,497 total issues (637 Canceled [14.2%] · 586 Open [13.0%])
1.93×stab : feat
1,769 bug/hardening/assurance vs. 915 feature Done issues (1.02× pre-Sep 11 → 4.81× post-Sep 11)
86.0%14d rework
of feat commits had files modified by a fix commit within 14d (1.47 : 1 fix-to-feat PR ratio)
66.7%CI pass
across 15,272 CI runs (5.2m median) · 61.1% across 1,602 cloud deploy runs (7.0m median)
i

Metric definitions — outcome & quality signals alongside volume: Alongside raw delivery counts (issues, story points, PRs, surviving lines), this page reports 14-day feature rework rate (share of feat commits whose source files were patched by a fix commit within 14 days), stabilization-to-feature ratio (bug + hardening + assurance vs. feature tickets), post-target scope creation (tickets filed after Sep 11), human PR review coverage & change-request rates, commit-to-production lead time, and CI/deploy workflow pass rates.

Dopamint product & workstream metrics

schedule, Linear ticket breakdown, verified throughput/latency benchmarks & production capacity across all tracks

Engineering lifecycle & process metrics

objective telemetry across Design, Autonomous Development, PR Review, Gitflow, CI/CD & Testing/Cloud

Industry-standard engineering benchmarks — explained

plain-English definitions, Dopamint Arena numbers, industry reference targets & what each metric tells you (DORA · Flow · CodeScene · DevEx)

Weekly velocity, PR mix & working-hours telemetry

weekly completed Linear issues (bars) & Fibonacci story points

Team contribution facets

12 dimensions across Linear, GitHub PRs, ADRs, Verification Reports & Codebase

Work-type & product portfolio distribution

share of each engineer’s completed work

Summary metrics by engineer

primary domain, lead metrics & subsystem ownership share per engineer

Engineer delivery & ownership breakdown

per engineer · systems shipped, subsystem code share (git blame) & stabilization/review volume

Subsystem code ownership distribution

surviving non-vendored lines across 18 core subsystems (git blame -w -M)

Data sources, metric formulas & exclusions

Multi-source dataset

  • Linear (DOPAN): 4,497 total issues (3,274 Done, 7,526 Fibonacci points, 637 Canceled/Duplicate, 586 Open) across 7 project tracks, plus 193 Legacy Arena (DOP/DOP2) issues.
  • GitHub PRs & Actions: 3,891 PRs opened (3,693 merged, 213 peer reviews) and 23,617 GitHub Actions workflow runs across 79 workflows.
  • Git & Codebase: 4,033 non-merge commits across 165 packages (126 Rust crates, 31 TS packages, 8 Move packages) and 35,145 automated tests.
  • Specs, Reports & Cloud: 247 ADRs, 175 verification/audit reports, 137 formal .qnt protocol models, and AWS production cost/inventory snapshots.

Quality & rework formulas

  • 14-day feature rework rate (86.0%): Share of feat commits whose modified production source files were patched by a subsequent fix commit within 14 days (18.1% same-day, 44.7% ≤3d, 72.3% ≤7d).
  • Stabilization-to-feature ratio (1.93×): Ratio of completed bug + hardening + assurance Linear issues (1,769) to feature issues (915); computed pre-Sep 11 (1.02×) and post-Sep 11 (4.81×).
  • Commit-to-main lead time (16.9d p50): Elapsed time between each dev commit timestamp and the dev → main release merge that promoted it.

Codebase & ownership exclusions

  • Excluded from line & blame counts: Vendored framework packages (contracts/tunnel, libs/sui-tunnel-ts, external/), lockfiles (Cargo.lock, pnpm-lock.yaml, Move.lock), generated snapshots, and binary assets.
  • Code retention (72% median): Surviving lines in HEAD (git blame -w -M) divided by total lines added across the measurement window per author.
Window: Jul 5 – Oct 19, 2026 · Sources: Linear (DOPAN, DOP, DOP2) + GitHub PRs & Actions + Git history + docs/reports/ + Mainnet campaign archives on CommandOSSLabs/dopamint-arena.