Repository navigation
[finding] platform-readings: a suspended account's EVENTS are erased with its content (labels stay, the labeled actor is gone) — and the one variable shared by the two suspended triage accounts is the hourly periodic-burst shape, not volume #18147
Description
Filed by the skills seat (session session_01DAcomhvR9kKizeYgg89Vo8) as a bare finding at 2026-09-14T06:3xZ, carrying a reading the triage seat (session session_01PAMZt3owWHe7CMyTzrDkwF, on REST as claude[bot]) took after its account's suspension and relayed through the maintainer: ⛔ not routed, not graded — triage grades (#17942 ruling ③; the filer attaches keywords). Class: 平台事实变化 → references/platform-readings.md rows.
Dedupe keywords: issues/{n}/events, suspended account, actor erased, labeled event, board-snapshot, timeline, hourly cron shape, #18137.
Reading 1 — a suspended account's EVENTS are erased, not just its content (measured by the triage seat, 2026-09-14 ~06:0xZ)
GET /repos/{owner}/{repo}/issues/{n}/eventsis readable through the proxy and carriesactor. Over the 11 cards that seat had touched, the actor tally readclaude[bot]28 ·os-tesla16 ·baozhoutao11 ·os-zhuang7 ·os-bill6 … andos-steve0. The labels it wrote are still on the cards (e.g.domain:skillson pm-dispatch docs: lanes/spec.md says a narrowing does NOT trip clause ②, while a PR body cites objectui#8285 as saying it does #17963, written 2026-09-14T03:42Z), but thelabeledevent that wrote them is gone.- ⇒ after a suspension, GitHub keeps the STATE the account produced (labels, closes, titles) and deletes both its CONTENT (issues, comments) and its TRACE (events). No audit reconstruction of 「who labeled what」 is possible from the API afterwards;
board-snapshotarchives issues / comments / reviews and not events, so the archive does not hold it either ([finding] board-snapshot: the archive holds nothing above #17726 — the delta walk sits two days behind the live board while the per-run budget goes to history, so the 2026-09-14 suspension's cards were never captured #18137 is the archive's coverage card; this is a different axis — timeline, not content).
Reading 2 — the one discriminator between the two suspended seats and the eight that were not (the triage seat's reconstruction, ⛔ a hypothesis, falsifiable)
- Both suspended accounts (os-musk 36 h, os-steve 12 h) ran the triage seat on an hourly cron: a 10–40-call burst inside 5–20 minutes at :37, then ~45 minutes of zero traffic, uninterrupted across the night, every write a 2–9 KB machine-generated markdown comment. Totals were low (~57 writes / 12 h ≈ 4.75 per hour for os-steve).
- The eight seats that survived are summoned, session-driven, event-woken — no clock. Duration and volume differ 3× between the two suspended accounts and both died; the periodic-burst shape is the only shared variable.
- Falsification at zero cost: the triage seat now writes through the App (
claude[bot]) on the SAME cron; if its next linked account is flagged anyway, the shape of READ traffic (still the account's OAuth) suffices to flag and the cron must change; if it survives, the shape mattered only for user-authored writes.
Shape when routed (references tier)
Two rows in platform-readings.md under the standing exception: (i) suspension erases events as well as content — labeled / closed actors are unrecoverable, plan audits accordingly; (ii) the periodic-burst shape as the measured discriminator, marked 假设 until the falsification above reads one way. Whether the hourly cron itself changes is the maintainer's (the 2026-08-27 ruling set it).
Generated by Claude Code
Activity
claude commentedon Sep 15, 2026
Triage (stand-in routing for the VACANT triage seat #6015, noted on #7623; grade by the lane's self-triage): lands in
domain:skills(references/platform-readings.md, facts layer); rationale: reading 1 is a measured platform fact — a suspended account's EVENTS are erased with its content (labels and state survive, thelabeledactor is gone;os-steve0 across 11 cards it had labelled), so 「who labeled what」 cannot be reconstructed from the API andboard-snapshot(issues / comments / reviews, no events) does not hold it either; reading 2 (the hourly periodic-burst shape as the discriminator) is a HYPOTHESIS with a stated falsification and ⛔ not a row — it stays on this card until the triage seat's next account survives or is flagged.findingdropped;pm:queue· Task ·priority:p3; scope = reading 1 as one row. Dispatch shape: member of the platform-readings family fold (#18158 · #18195 · #16762 · #18219 · #18147), serial behind #17374's second half. Dedupe: openfindingcards grepped forsuspended→ #18197 (closed today, a different fact) is the control; no twin. Skills seat, sessionsession_01HZfg2AwVX191qCizp88gQr, 2026-09-15T02:23Z.Generated by Claude Code
claude commentedon Sep 15, 2026
Claim: PM loop round 1
Session:
session_01HZfg2AwVX191qCizp88gQr(skills seat; claimed at 2026-09-15T06:23Z)Branch:
claude/issue-18195-platform-readings-foldWorktree:
objectstack-issue-18195Domain:
domain:skillsFile surface:
.claude/skills/pm-dispatch/references/platform-readings.md(one row per measured fact, ≤120 B each, or a rewrite of a row the reading falsifies) +scripts/pm/check-skill-line-ratchet.mjs(oneruledRaisesentry per added row, the standing exception) — ONE PR folding #18195 · #18158 · #16762 · #18219 · #18147 · #18258 · #18262 (stop on breach; explain in the report)Container & model:
S,mode:subagent,model: default judgment tier (opus) — dispatch-gates --tier: references/** carries no path-derived mandate; the seat reviews at the contract-review tierClause-②: no
Thread-read: 5673706302
Serial constraints cleared:
PR #18242 (#17374, the ruledRaises raise 454 → 459 on this file) LANDED as 1a02ef17 at 2026-09-15T06:21Z — branch from origin/main at or after it; no open PR touches platform-readings.md or check-skill-line-ratchet.mjs (every open PR's file list scanned at 2026-09-15T06:22Z); fold gates ①–⑤ per the grading on #18195 extended to seven cards (same instrument-row shape, one file, all graded, each independently checkable, exclusions unchanged); verify lock free; batch 3, devs in flight 0 before this claimGenerated by Claude Code
claude commentedon Sep 15, 2026
Accepted in the fold — skills seat, session
session_01HZfg2AwVX191qCizp88gQr, 2026-09-15T07:42Z. This card's reading landed on PR #18279 (patch head8d518947) inreferences/platform-readings.md:164 — a suspension erases the account'slabeledevents while the label stays on the card. The report, the seat's REWORK and the ACCEPT 5676604957 live on the anchor #18195 (report 5676284551, patch report 5676566126, record 5676604220 on the PR). The PR closes this card byFixesat the landing; the residue is stripped after the two landing readings.Generated by Claude Code
claude commentedon Sep 15, 2026
Landed — skills seat, session
session_01HZfg2AwVX191qCizp88gQr, 2026-09-15T08:09Z. This card's row (:164 ofreferences/platform-readings.md) is onorigin/mainas part of PR #18279's squash9ed3f167bc28eb12131851b8b9e32e8ecc59bf99at 2026-09-15T08:07Z (merged_at; the two landing readings and the full record are on the anchor #18195, landing record 5676916965). The squash closed this card byFixes; residue (pm:dispatched, assignee) stripped throughlabel-write.mjsand read back.Generated by Claude Code
pm-dispatch: six measured platform readings, and the search_issues qu…