{"schema_version": 1, "repository": "aadarwal/swarmstatus-bounties", "url": "https://swarmstatus.com/contribute", "scope": "Current Swarmstatus research invitation; not an investigation source or a complete history.", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-07T19:29:54.981004+00:00", "stale": false, "refreshing": false, "unavailable": false, "error": null, "items": [{"id": "bounty-29", "number": 29, "teaser": {"kind": "reviewed_issue_teaser", "reviewed_body_sha256": "209f7930c42c16eadd0c5ed2add6895c6410b271ddbbf329037f51b8e99cfa5b", "title": "Find the response that distinguishes 41 from about 42", "hook": "For 2.0, the current chart cells 67 and 26 imply a 41-year difference; the article says about 42. A retained response could distinguish those representations.", "missing_proof": "Readable retained answer/response content with provenance, compared to the exact chart cells and article wording.", "new_evidence": "A posted request, matching title or successful HTTP status is not the missing answer."}, "title": "Find a retained response that distinguishes the Rajinikanth chart from article prose", "status": "in-review", "question": "Do any independently retained task responses or answer passages use the exact numeric table in Infogram 55eeebff-2501-4b78-979d-1c7c1e5c4f74, rather than the accompanying article prose? For 2.0, the current chart cells say 67 and 26 (a derived 41-year difference), while the publisher article describes about 42. Use this difference and the ordered 11-film table as source-discriminating fingerprints; do not assume either was consumed.", "source_context": "- Primary source\n  September 5 direct capture, 69,016 bytes, SHA256 2d019883fd880c50294fc62c94088a3a4d6fce83cfd52ad02aba955904379253. Literal JSON extracted without executing page code. Canonical and embedded infographic objects compare equal.\n\n- Primary source\n  Current publisher article embeds the exact UUID. Its 2.0 passage says about 42 years, unlike the difference calculated from the chart cells. This is publisher context, not an agent staging surface.\n\n- Primary source\n  A retained source revision records canonical and embed retrieval routes; no returned table or final answer is present in this body.\n  Retained record 2f441c09", "deliverables": ["Provide a readable retained response or answer, its exact source locator, acquisition hash and distinct source/observation clocks. A request link or HTTP status alone does not qualify.", "Compare exact chart cells, row ordering and relevant article wording. Show which source representation is supported, or report a contradictory result.", "Account for copied values, current-versus-historical content changes and the possibility of an answer derived from another source.", "Do not treat the three other charts embedded in the article as task activity without independent evidence."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Provide a readable retained response or answer, its exact source locator, acquisition hash and distinct source/observation clocks. A request link or HTTP status alone does not qualify.\nCompare exact chart cells, row ordering and relevant article wording. Show which source representation is supported, or report a contradictory result.\nAccount for copied values, current-versus-historical content changes and the possibility of an answer derived from another source.\nDo not treat the three other charts embedded in the article as task activity without independent evidence."}], "research_notes": [{"heading": "Research update — September 5", "text": "The 11-row table and its source-specific 41 versus approximately 42 distinction are verified. No retained response yet identifies which representation was used. Reviewed evidence and reproduction scripts. This bounty remains open."}], "issue_text": "## Question\n\nDo any independently retained task responses or answer passages use the exact numeric table in Infogram 55eeebff-2501-4b78-979d-1c7c1e5c4f74, rather than the accompanying article prose? For 2.0, the current chart cells say 67 and 26 (a derived 41-year difference), while the publisher article describes about 42. Use this difference and the ordered 11-film table as source-discriminating fingerprints; do not assume either was consumed.\n\n## Existing evidence\n\n- [Primary source](https://e.infogram.com/55eeebff-2501-4b78-979d-1c7c1e5c4f74?src=embed)\n  September 5 direct capture, 69,016 bytes, SHA256 2d019883fd880c50294fc62c94088a3a4d6fce83cfd52ad02aba955904379253. Literal JSON extracted without executing page code. Canonical and embedded infographic objects compare equal.\n\n- [Primary source](https://www.thequint.com/entertainment/salman-khan-to-akshay-kumar-only-bollywood-heroes-are-forever-young)\n  Current publisher article embeds the exact UUID. Its 2.0 passage says about 42 years, unlike the difference calculated from the chart cells. This is publisher context, not an agent staging surface.\n\n- [Primary source](https://collusion.wiki/explorer/page/probier~QuintChartAPI4777.html#rev-2)\n  A retained source revision records canonical and embed retrieval routes; no returned table or final answer is present in this body.\n  [Retained record 2f441c09](https://swarmstatus.com/api/record?id=2f441c09615837b5c69aa2a4f352e5e2)\n\n## Acceptance criteria\n\n- [ ] Provide a readable retained response or answer, its exact source locator, acquisition hash and distinct source/observation clocks. A request link or HTTP status alone does not qualify.\n- [ ] Compare exact chart cells, row ordering and relevant article wording. Show which source representation is supported, or report a contradictory result.\n- [ ] Account for copied values, current-versus-historical content changes and the possibility of an answer derived from another source.\n- [ ] Do not treat the three other charts embedded in the article as task activity without independent evidence.\n\n## Caveats and alternatives\n\n- This is a source-attribution question, not a claim about actual actor ages or real agent identity.\n- Current chart metadata asserts a 2022 update; it does not independently establish the historical table served in June 2026.\n- The existing #7 staging-surface question remains separate and unresolved.\n\n## Prior work\n\nNewly recovered current primary chart table, its exact canonical/embed equivalence and a numeric discrepancy supply additional search fingerprints. The chart UUID and wiki retrieval routes were already known.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:round3-infogram-chart-prose -->\n\n\n## Research update — September 5\n\nThe 11-row table and its source-specific 41 versus approximately 42 distinction are verified. No retained response yet identifies which representation was used. [Reviewed evidence and reproduction scripts](https://github.com/aadarwal/swarmstatus-bounties/pull/30). This bounty remains open.\n", "limits": "- This is a source-attribution question, not a claim about actual actor ages or real agent identity.\n- Current chart metadata asserts a 2022 update; it does not independently establish the historical table served in June 2026.\n- The existing #7 staging-surface question remains separate and unresolved.", "sources": [{"label": "Retained record 2f441c09", "url": "https://swarmstatus.com/api/record?id=2f441c09615837b5c69aa2a4f352e5e2"}], "evidence_prs": ["https://github.com/aadarwal/swarmstatus-bounties/pull/30"], "url": "https://swarmstatus.com/contribute/29", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/29", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/29#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T18:51:15Z", "areas": ["Infogram"]}, {"id": "bounty-33", "number": 33, "teaser": {"kind": "reviewed_issue_teaser", "reviewed_body_sha256": "2900f509063b32f26c31834806800a3e672eb4c820ca3581dce92a3a929a9bf3", "title": "Trace repeated request blocks to a dated source", "hook": "The same USAspending and SF133 blocks occur beneath different paste parents. Their origin and copying direction remain unknown.", "missing_proof": "A preserved, independently dated task or template beyond the retained copies, with exact ordered correspondence and a reproducible comparison.", "new_evidence": "The duplicate bodies and native parent links are already verified; the missing piece is dated source context."}, "title": "Trace the repeated USAspending/SF133 paste branches to a dated task source or template", "status": "open", "question": "What source, template, or independently dated task-bearing publication explains the same ordered USAspending API block and SF133 report block occurring as sibling replies under two different filler pastes? Trace the construction of these specific branches; a topical match, a same-name wiki page, or another undated copy alone does not answer it.", "source_context": "- Primary source\n  Current first-party parent body is exactly x. Its replies list RefAP and RefQ3. Parent object was absent from the retained DB; capture timestamp is 2026-09-05T18:47:47.008838+00:00, not publication time. Hash is of the current whole HTML capture.\n  source sha256: bdc27b2f4d87d7e9bf5d9ade6a04f360e1b69a6bad2b42bdf7796d0aa2c5973f.\n\n- Primary source\n  Current first-party parent body is exactly SHIFT8. Its replies list RefAP2, RefQ0 and the distinct RefNX block. This parent already exists in the full acquisition corpus but was excluded from the focused snapshot. The new capture independently verifies native relations; 2026-09-05T18:47:47.009284+00:00 is capture time, not publication time. Hash is of the current whole HTML capture.\n  source sha256: 242cf3f37c4c8244abe52e7070c641d1210401e4d8b461902d5479c75609d6f8.\n  Acquisition record ID: caf81e6954db5f753aa7ef8533c49d81 (outside the focused explorer; use the primary locator above).\n\n- Primary source\n  Exact decoded-text pair RefAP / RefAP2: ordered ACCGET 075-8005; ACCGET23 same account with fiscal_year=2023; SNAP23 internal-ID text 5599/fiscal_year_snapshot/2023; QEND v1/tas/balances/quarters/total without query. Both native parent assertions verified. Decoded-text SHA-256: 5cf58fbb41910d29c900b8a7bd920670d86d0399e03f60e4e07db929dd871a27. Paired primary source: https://paste.linuxiarz.pl/view/b0924d89\n  Retained record be8776ed\n  Retained record 5f4adaa5\n\n- Primary source\n  Exact decoded-text pair RefQ3 / RefQ0: ordered seven labels Q2MDSCHEMELESS, Q3MDSCHEMELESS, Q2DIRECT, Q3DIRECT, Q2MDFULL, Q2CORS, Q2AO; MAX parent attachment 2346466575, file IDs 2374423602.pdf and 2398882076.pdf. Literal wrapper representations differ within each packet but entire packets match each other. Decoded-text SHA-256: 1d118617bd67c287e69b813660b9b586debddafeb7570e8162b31918131eabe5. Paired primary source: https://paste.linuxiarz.pl/view/59c84c78\n  Retained record d4f4dd52\n  Retained record 0d58fae4\n\n- Primary source\n  Distinct RefNX three-link spreadsheet/ZIP block, current native child of SHIFT8; contextual fifth relation, not an exact pair.\n  Retained record 10b5ccac\n\n- Primary source\n  Ordinary-use negative control: page displays May 3, 2017 edit date and already documents quarterly balance fields, but uses different account/year examples and lacks the exact duplicated packet.", "deliverables": ["Supply a preserved, source-qualified template or task-bearing publication outside the presently retained identical-copy set, with complete relevant bytes or minimal literal extracts, source URL, access time, SHA-256, and a defensible dating source. Clearly distinguish publication, revision, archive-capture, HTTP-transaction and investigation-capture clocks.", "Demonstrate exact ordered correspondence for both the four-link API block and seven-link SF133 block, or recover an explicit task/template connecting their distinctive account/year/attachment IDs and their paired branch construction. Preserve query order, spelling, label order, nested representation and any mismatches; explain whether the source is a generator/template, a copied publication, or only a related task.", "If claiming an origin or propagation direction, provide independent evidence for it. Mere equality, the current relative age, provider reply linkage, shared handles/IPs or a receipt for the same data family is insufficient. An independently dated related publication may advance the question without establishing origin.", "Include reproducible offline comparisons and negative controls: x and SHIFT8 are not task messages; RefNX is a distinct sibling; ordinary USAspending docs with account 2357/FY2015 or 2017 do not match; an altered account or attachment ID must be rejected.", "Keep artifact text, requested URLs and actual returned data separate. A successful government-data response is neither required nor implied unless supported by its own captured transaction/body. Do not replay state-changing or proxy payload URLs."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Supply a preserved, source-qualified template or task-bearing publication outside the presently retained identical-copy set, with complete relevant bytes or minimal literal extracts, source URL, access time, SHA-256, and a defensible dating source. Clearly distinguish publication, revision, archive-capture, HTTP-transaction and investigation-capture clocks.\nDemonstrate exact ordered correspondence for both the four-link API block and seven-link SF133 block, or recover an explicit task/template connecting their distinctive account/year/attachment IDs and their paired branch construction. Preserve query order, spelling, label order, nested representation and any mismatches; explain whether the source is a generator/template, a copied publication, or only a related task.\nIf claiming an origin or propagation direction, provide independent evidence for it. Mere equality, the current relative age, provider reply linkage, shared handles/IPs or a receipt for the same data family is insufficient. An independently dated related publication may advance the question without establishing origin.\nInclude reproducible offline comparisons and negative controls: x and SHIFT8 are not task messages; RefNX is a distinct sibling; ordinary USAspending docs with account 2357/FY2015 or 2017 do not match; an altered account or attachment ID must be rejected.\nKeep artifact text, requested URLs and actual returned data separate. A successful government-data response is neither required nor implied unless supported by its own captured transaction/body. Do not replay state-changing or proxy payload URLs."}], "research_notes": [], "issue_text": "## Question\n\nWhat source, template, or independently dated task-bearing publication explains the same ordered USAspending API block and SF133 report block occurring as sibling replies under two different filler pastes? Trace the construction of these specific branches; a topical match, a same-name wiki page, or another undated copy alone does not answer it.\n\n## Existing evidence\n\n- [Primary source](https://paste.linuxiarz.pl/view/34cb12da)\n  Current first-party parent body is exactly x. Its replies list RefAP and RefQ3. Parent object was absent from the retained DB; capture timestamp is 2026-09-05T18:47:47.008838+00:00, not publication time. Hash is of the current whole HTML capture.\n  source sha256: `bdc27b2f4d87d7e9bf5d9ade6a04f360e1b69a6bad2b42bdf7796d0aa2c5973f`.\n\n- [Primary source](https://paste.linuxiarz.pl/view/89a3961d)\n  Current first-party parent body is exactly SHIFT8. Its replies list RefAP2, RefQ0 and the distinct RefNX block. This parent already exists in the full acquisition corpus but was excluded from the focused snapshot. The new capture independently verifies native relations; 2026-09-05T18:47:47.009284+00:00 is capture time, not publication time. Hash is of the current whole HTML capture.\n  source sha256: `242cf3f37c4c8244abe52e7070c641d1210401e4d8b461902d5479c75609d6f8`.\n  Acquisition record ID: `caf81e6954db5f753aa7ef8533c49d81` (outside the focused explorer; use the primary locator above).\n\n- [Primary source](https://paste.linuxiarz.pl/view/7d012d32)\n  Exact decoded-text pair RefAP / RefAP2: ordered ACCGET 075-8005; ACCGET23 same account with fiscal_year=2023; SNAP23 internal-ID text 5599/fiscal_year_snapshot/2023; QEND v1/tas/balances/quarters/total without query. Both native parent assertions verified. Decoded-text SHA-256: 5cf58fbb41910d29c900b8a7bd920670d86d0399e03f60e4e07db929dd871a27. Paired primary source: https://paste.linuxiarz.pl/view/b0924d89\n  [Retained record be8776ed](https://swarmstatus.com/api/record?id=be8776ed5c8b92e805c040b19372b39e)\n  [Retained record 5f4adaa5](https://swarmstatus.com/api/record?id=5f4adaa5c03919ca55231fad7800bfcc)\n\n- [Primary source](https://paste.linuxiarz.pl/view/d379207f)\n  Exact decoded-text pair RefQ3 / RefQ0: ordered seven labels Q2MDSCHEMELESS, Q3MDSCHEMELESS, Q2DIRECT, Q3DIRECT, Q2MDFULL, Q2CORS, Q2AO; MAX parent attachment 2346466575, file IDs 2374423602.pdf and 2398882076.pdf. Literal wrapper representations differ within each packet but entire packets match each other. Decoded-text SHA-256: 1d118617bd67c287e69b813660b9b586debddafeb7570e8162b31918131eabe5. Paired primary source: https://paste.linuxiarz.pl/view/59c84c78\n  [Retained record d4f4dd52](https://swarmstatus.com/api/record?id=d4f4dd52b4f7b87470b56384561e58a0)\n  [Retained record 0d58fae4](https://swarmstatus.com/api/record?id=0d58fae455d31c70235a33212f25d566)\n\n- [Primary source](https://paste.linuxiarz.pl/view/a43cd523)\n  Distinct RefNX three-link spreadsheet/ZIP block, current native child of SHIFT8; contextual fifth relation, not an exact pair.\n  [Retained record 10b5ccac](https://swarmstatus.com/api/record?id=10b5ccacfb53f38353fb92582b8a7180)\n\n- [Primary source](https://github.com/fedspendingtransparency/usaspending-website/wiki/Federal-Account-Page)\n  Ordinary-use negative control: page displays May 3, 2017 edit date and already documents quarterly balance fields, but uses different account/year examples and lacks the exact duplicated packet.\n\n## Acceptance criteria\n\n- [ ] Supply a preserved, source-qualified template or task-bearing publication outside the presently retained identical-copy set, with complete relevant bytes or minimal literal extracts, source URL, access time, SHA-256, and a defensible dating source. Clearly distinguish publication, revision, archive-capture, HTTP-transaction and investigation-capture clocks.\n- [ ] Demonstrate exact ordered correspondence for both the four-link API block and seven-link SF133 block, or recover an explicit task/template connecting their distinctive account/year/attachment IDs and their paired branch construction. Preserve query order, spelling, label order, nested representation and any mismatches; explain whether the source is a generator/template, a copied publication, or only a related task.\n- [ ] If claiming an origin or propagation direction, provide independent evidence for it. Mere equality, the current relative age, provider reply linkage, shared handles/IPs or a receipt for the same data family is insufficient. An independently dated related publication may advance the question without establishing origin.\n- [ ] Include reproducible offline comparisons and negative controls: x and SHIFT8 are not task messages; RefNX is a distinct sibling; ordinary USAspending docs with account 2357/FY2015 or 2017 do not match; an altered account or attachment ID must be rejected.\n- [ ] Keep artifact text, requested URLs and actual returned data separate. A successful government-data response is neither required nor implied unless supported by its own captured transaction/body. Do not replay state-changing or proxy payload URLs.\n\n## Caveats and alternatives\n\n- Current first-party captures are after disclosure. All seven paste pages show only the relative age 3 Months ago; no UTC creation timestamp is recovered.\n- Repeated decoded text demonstrates structural reuse, not independent executions, semantic conversation, actor attribution, or causal copying direction.\n- Existing known receipt classifications and wiki copies are context, not new sources. The API and SF133 label text does not verify the official content of the referenced responses.\n- Twenty bounded searches did not find an independent dated packet; that is not proof no such source exists.\n\n## Prior work\n\nFive first-party reciprocal parent relationships have now been verified for two exact sibling-block pairs. One filler body is newly recovered; the other existed in the full acquisition but was excluded from the focused explorer. This asks for the source or template behind the specific repeated construction, distinct from generic legacy-site discovery (#19) and registration-order timing (#2). Current captures do not establish an origin or date.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:usaspending-native-paste-branches -->\n\n\n## Reviewed structural evidence\n\n[PR #42](https://github.com/aadarwal/swarmstatus-bounties/pull/42) includes the source graph, seven factual bodies, 16 exact provider excerpts, capture provenance and an offline verifier with ten negative controls. The current parent captures are in the explorer: [x](https://swarmstatus.com/api/record?id=ceb653faf0ac3a00da81dfa065d0d979) and [SHIFT8](https://swarmstatus.com/api/record?id=ab8b093f3ce51b4d263cbc6bd6c25494). The latter already existed in the full acquisition; its focused recapture is not a newly discovered full-corpus body.\n\nThe bounty remains open for a dated source/template or task publication beyond these retained copies.\n", "limits": "- Current first-party captures are after disclosure. All seven paste pages show only the relative age 3 Months ago; no UTC creation timestamp is recovered.\n- Repeated decoded text demonstrates structural reuse, not independent executions, semantic conversation, actor attribution, or causal copying direction.\n- Existing known receipt classifications and wiki copies are context, not new sources. The API and SF133 label text does not verify the official content of the referenced responses.\n- Twenty bounded searches did not find an independent dated packet; that is not proof no such source exists.", "sources": [{"label": "Retained record be8776ed", "url": "https://swarmstatus.com/api/record?id=be8776ed5c8b92e805c040b19372b39e"}, {"label": "Retained record 5f4adaa5", "url": "https://swarmstatus.com/api/record?id=5f4adaa5c03919ca55231fad7800bfcc"}, {"label": "Retained record d4f4dd52", "url": "https://swarmstatus.com/api/record?id=d4f4dd52b4f7b87470b56384561e58a0"}], "evidence_prs": ["https://github.com/aadarwal/swarmstatus-bounties/pull/42"], "url": "https://swarmstatus.com/contribute/33", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/33", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/33#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T19:37:33Z", "areas": ["USAspending"]}, {"id": "bounty-22", "number": 22, "teaser": {"kind": "reviewed_issue_teaser", "reviewed_body_sha256": "bc10ecffc319af3f658bbdefe549dec6deafb1baefd0a2e793ba2c7417059f19", "title": "Recover historical data for an India malaria chart", "hook": "The exact chart is readable today and an archived publisher page cites it. Historical chart JSON and independent task staging remain unresolved.", "missing_proof": "Full resolution needs a retained historical data/configuration body and an independent task-bearing publication outside the Vanderbilt alias cluster that cites the complete chart ID. Either alone is a useful partial.", "new_evidence": "A current publisher chart or archived iframe citation alone does not establish historical numerical values."}, "title": "Recover the India malaria chart and a historical task citation", "status": "open", "question": "Recover a retained historical data/configuration body for chart d88e6864f43c426dbcd1ee675a8944a7 and locate a task-bearing publication outside the current Vanderbilt alias cluster that cites this exact object. Determine the chart subject, units, geography and time range from actual content.", "source_context": "- Primary source\n  malagent0x points to exact data.json, raw time 01:55:22.\n  time raw: 2026-06-21 01:55:22.\n  time basis: raw_unzoned.\n  source sha256: cb5a906455bc952d39702243a9bf3fa450933a1c51c6d60ee625a17b64e5bd53.\n  Retained record 96cf687b\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://assets.dataforindia.com/charts/d88e6864f43c426dbcd1ee675a8944a7/data.json\n\n\n- Primary source\n  malagent1x points to config.json, raw time 01:55:24.\n  time raw: 2026-06-21 01:55:24.\n  time basis: raw_unzoned.\n  source sha256: cb5a906455bc952d39702243a9bf3fa450933a1c51c6d60ee625a17b64e5bd53.\n  Retained record f6983225\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://assets.dataforindia.com/charts/d88e6864f43c426dbcd1ee675a8944a7/config.json\n\n\n- Primary source\n  malagent2x points through md.succ.ai to data.json, raw time 01:55:26.\n  time raw: 2026-06-21 01:55:26.\n  time basis: raw_unzoned.\n  source sha256: cb5a906455bc952d39702243a9bf3fa450933a1c51c6d60ee625a17b64e5bd53.\n  Retained record d4bf80fe\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://md.succ.ai/assets.dataforindia.com/charts/d88e6864f43c426dbcd1ee675a8944a7/data.json\n\n\n- Primary source\n  malagent3x points to the chart page itself.\n  time raw: 2026-06-21 01:55:28.\n  time basis: raw_unzoned.\n  source sha256: cb5a906455bc952d39702243a9bf3fa450933a1c51c6d60ee625a17b64e5bd53.\n  Retained record 7377c88a\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://www.dataforindia.com/charts/d88e6864f43c426dbcd1ee675a8944a7/", "deliverables": ["Provide exact public source locators plus retained content or archive evidence and its acquisition date.", "State what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.", "Do not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.", "Match all 32 characters of the object ID and identify data/config/chart representation separately.", "Provide readable retained content to substantiate chart semantics; a title or alias alone is insufficient.", "A new staging claim requires an independent publication/capture context, not just the normal original chart page."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Provide exact public source locators plus retained content or archive evidence and its acquisition date.\nState what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.\nDo not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.\nMatch all 32 characters of the object ID and identify data/config/chart representation separately.\nProvide readable retained content to substantiate chart semantics; a title or alias alone is insufficient.\nA new staging claim requires an independent publication/capture context, not just the normal original chart page."}], "research_notes": [{"heading": "Research update — September 5", "text": "A June 13 archived publisher article cites the exact chart; current data/configuration recover 88 percentage values. Historical chart JSON and independent task staging remain unresolved. Reviewed evidence and reproduction scripts. This bounty remains open."}], "issue_text": "## Question\n\nRecover a retained historical data/configuration body for chart d88e6864f43c426dbcd1ee675a8944a7 and locate a task-bearing publication outside the current Vanderbilt alias cluster that cites this exact object. Determine the chart subject, units, geography and time range from actual content.\n\n## Existing evidence\n\n- [Primary source](https://vanderbi.lt/malagent0x+)\n  malagent0x points to exact data.json, raw time 01:55:22.\n  time raw: `2026-06-21 01:55:22`.\n  time basis: `raw_unzoned`.\n  source sha256: `cb5a906455bc952d39702243a9bf3fa450933a1c51c6d60ee625a17b64e5bd53`.\n  [Retained record 96cf687b](https://swarmstatus.com/api/record?id=96cf687b16d903228b626d987f60e66e)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://assets.dataforindia.com/charts/d88e6864f43c426dbcd1ee675a8944a7/data.json\n```\n\n- [Primary source](https://vanderbi.lt/malagent1x+)\n  malagent1x points to config.json, raw time 01:55:24.\n  time raw: `2026-06-21 01:55:24`.\n  time basis: `raw_unzoned`.\n  source sha256: `cb5a906455bc952d39702243a9bf3fa450933a1c51c6d60ee625a17b64e5bd53`.\n  [Retained record f6983225](https://swarmstatus.com/api/record?id=f69832253f4fa816b7393903b79d4d07)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://assets.dataforindia.com/charts/d88e6864f43c426dbcd1ee675a8944a7/config.json\n```\n\n- [Primary source](https://vanderbi.lt/malagent2x+)\n  malagent2x points through md.succ.ai to data.json, raw time 01:55:26.\n  time raw: `2026-06-21 01:55:26`.\n  time basis: `raw_unzoned`.\n  source sha256: `cb5a906455bc952d39702243a9bf3fa450933a1c51c6d60ee625a17b64e5bd53`.\n  [Retained record d4bf80fe](https://swarmstatus.com/api/record?id=d4bf80fedbbbd600d992b36b49a70397)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://md.succ.ai/assets.dataforindia.com/charts/d88e6864f43c426dbcd1ee675a8944a7/data.json\n```\n\n- [Primary source](https://vanderbi.lt/malagent3x+)\n  malagent3x points to the chart page itself.\n  time raw: `2026-06-21 01:55:28`.\n  time basis: `raw_unzoned`.\n  source sha256: `cb5a906455bc952d39702243a9bf3fa450933a1c51c6d60ee625a17b64e5bd53`.\n  [Retained record 7377c88a](https://swarmstatus.com/api/record?id=7377c88a66bf76466e6fa6573d77ff55)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://www.dataforindia.com/charts/d88e6864f43c426dbcd1ee675a8944a7/\n```\n\n## Acceptance criteria\n\n- [ ] Provide exact public source locators plus retained content or archive evidence and its acquisition date.\n- [ ] State what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.\n- [ ] Do not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.\n- [ ] Match all 32 characters of the object ID and identify data/config/chart representation separately.\n- [ ] Provide readable retained content to substantiate chart semantics; a title or alias alone is insufficient.\n- [ ] A new staging claim requires an independent publication/capture context, not just the normal original chart page.\n\n## Caveats and alternatives\n\n- The intake analysis found thirteen matching creation records and no literal original-wiki body hit. This is bounded corpus coverage, not proof of global absence.\n- The 0x/1x/2x sequence spans four raw-clock seconds, but raw server timezone is unresolved.\n- A representation sweep can arise from one scripted workflow and does not prove multiple agents.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:coverage-india-malaria-chart -->\n\n\n## Research update — September 5\n\nA June 13 archived publisher article cites the exact chart; current data/configuration recover 88 percentage values. Historical chart JSON and independent task staging remain unresolved. [Reviewed evidence and reproduction scripts](https://github.com/aadarwal/swarmstatus-bounties/pull/30). This bounty remains open.\n", "limits": "- The intake analysis found thirteen matching creation records and no literal original-wiki body hit. This is bounded corpus coverage, not proof of global absence.\n- The 0x/1x/2x sequence spans four raw-clock seconds, but raw server timezone is unresolved.\n- A representation sweep can arise from one scripted workflow and does not prove multiple agents.", "sources": [{"label": "Retained record 96cf687b", "url": "https://swarmstatus.com/api/record?id=96cf687b16d903228b626d987f60e66e"}, {"label": "Retained record f6983225", "url": "https://swarmstatus.com/api/record?id=f69832253f4fa816b7393903b79d4d07"}, {"label": "Retained record d4bf80fe", "url": "https://swarmstatus.com/api/record?id=d4bf80fedbbbd600d992b36b49a70397"}], "evidence_prs": ["https://github.com/aadarwal/swarmstatus-bounties/pull/30"], "url": "https://swarmstatus.com/contribute/22", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/22", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/22#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-07T14:10:28Z", "areas": ["India-malaria"]}, {"id": "bounty-65", "number": 65, "teaser": null, "title": "Recover the intermediate body between two Police wiki saves", "status": "in-review", "question": "What body resulted from the first of two recorded section saves to PoliceWageAgeSequenceMar10Collab on June 20, 2026, and what evidence can distinguish successive appends or stale-section reuse from an input that already contained duplicate text?\n\nThe concrete missing artifact is the body after the 03:43:43 UTC save and before the 03:45:08 UTC save. A source-qualified returned archive body or transformation record may instead discriminate where the duplication arose. The retained final body alone does not select a mechanism.", "source_context": "Three source-qualified export records preserve the before/stub/later-body comparison:\n\n| Retained revision | Source-export request time, UTC | Body bytes | Relevant content |\n|---|---|---:|---|\n| 48, record 7b5fab87146d714b3dff277db29e4714 | 2026-06-19 22:04:04 | 12,649 | Contains the old 2,047-byte continuation passage. |\n| 49, record 4067985c68fa8ffba33fb935b8f35730 | 2026-06-20 00:22:04 | 179 | Export-declared recreation stub; none of that passage. |\n| 50, record d665647d5129a51ca24e40cbd774224c | 2026-06-20 03:45:08 | 4,597 | Stub plus two identical sections, each containing the old passage and a new 162-byte status paragraph. |\n\nThe exact retained-body relation is 4,597 = 179 + 2 × (2,047 + 162). The old passage has SHA-256 35ae2f5cc601a605d08ed582856814d94fb512d05314fdfa8d67a9208c0db963; its UTF-8 byte spans are [6987,9034) in revision48 and [179,2226) / [2388,4435) in revision50. These are zero-based, half-open spans. The 2,209-byte repeated section has SHA-256 fb3f9878155bede9015b24f28244f952b2cd50142f5b1326b4a0ebe2d2f10530.\n\nThe export records a June 19 deletion before revision49. Its short stub claims an archive holds a prior table; the later text's reappearance does not establish an archive retrieval. Source13 body rows and source19 event rows share one released source, so they are not independent witnesses. A declared save-pointer relation is not additional native write evidence.\n\nA separate bounded review of retained native request/change records supports this selected sequence on June 20, 2026:\n\n- 03:43:43 UTC: a section1 form-save request and matching native change entry, native revision2.\n- 03:44:05–03:44:34 UTC: 28 selected archive-version requests for this page, covering versions1.51–1.79 except1.67.\n- 03:45:08 UTC: another section1 form-save request and matching native change entry, native revision3, 85 seconds after the first.\n\nBoth saves share the recorded summary DEC28 slow-tier R2 and an earlier edit-context timestamp, but the complete requests differ. Both text fields retain only the (NN) sentinel: neither submitted body is available. The change entries also lack resulting bodies. The archive records retain requested versions, without response status/body or a recorded method. These selected records are positive observations, not an exhaustive request history.", "deliverables": ["Recover a source-qualified body resulting from the first save, or returned archive/body and transformation evidence that discriminates where the duplicate section entered this exact sequence. Identify the precise page, source-scoped version or event, readable bytes, SHA-256, capture provenance and clock basis. Explain the linkage to the selected save window without relying on caller identity.", "Compare the recovered content with the 179-byte stub, the 2,047-byte old passage, the 162-byte status paragraph and both copies in revision50. Preserve complete bodies and document every decoding or normalization step separately from original hashes.", "State which alternatives the new evidence supports or rules out: successive appends, stale editor/section content, already-duplicated input, or another supported transformation. A local demonstration of possible software behavior alone does not establish what happened in this case.", "Keep export indices48/49/50 distinct from native revisions2/3 and archive-version labels. Source13/19 share a publisher; matching labels or clocks do not create independent witnesses. (NN) is not an actual empty submission. An issued archive request is not a returned body, proof of reading it, or evidence that the same actor made a later edit.", "Report the remaining uncertainty. Recovering a relevant archive body or excluding one mechanism can be useful partial evidence. Full resolution requires a new artifact tied to this sequence that answers the missing-body or transformation question; repeating the final duplicate, generic engine behavior, or search misses is insufficient. Do not infer authenticated actors, task success, harness origin or copying direction beyond the supplied evidence."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Recover a source-qualified body resulting from the first save, or returned archive/body and transformation evidence that discriminates where the duplicate section entered this exact sequence. Identify the precise page, source-scoped version or event, readable bytes, SHA-256, capture provenance and clock basis. Explain the linkage to the selected save window without relying on caller identity.\nCompare the recovered content with the 179-byte stub, the 2,047-byte old passage, the 162-byte status paragraph and both copies in revision50. Preserve complete bodies and document every decoding or normalization step separately from original hashes.\nState which alternatives the new evidence supports or rules out: successive appends, stale editor/section content, already-duplicated input, or another supported transformation. A local demonstration of possible software behavior alone does not establish what happened in this case.\nKeep export indices48/49/50 distinct from native revisions2/3 and archive-version labels. Source13/19 share a publisher; matching labels or clocks do not create independent witnesses. (NN) is not an actual empty submission. An issued archive request is not a returned body, proof of reading it, or evidence that the same actor made a later edit.\nReport the remaining uncertainty. Recovering a relevant archive body or excluding one mechanism can be useful partial evidence. Full resolution requires a new artifact tied to this sequence that answers the missing-body or transformation question; repeating the final duplicate, generic engine behavior, or search misses is insufficient. Do not infer authenticated actors, task success, harness origin or copying direction beyond the supplied evidence."}], "research_notes": [], "issue_text": "<!-- swarmstatus:police-deletion-intermediate-body -->\n\n## Question\n\nWhat body resulted from the first of two recorded section saves to `PoliceWageAgeSequenceMar10Collab` on June 20, 2026, and what evidence can distinguish successive appends or stale-section reuse from an input that already contained duplicate text?\n\nThe concrete missing artifact is the body after the **03:43:43 UTC** save and before the **03:45:08 UTC** save. A source-qualified returned archive body or transformation record may instead discriminate where the duplication arose. The retained final body alone does not select a mechanism.\n\n## Existing evidence\n\nThree source-qualified export records preserve the before/stub/later-body comparison:\n\n| Retained revision | Source-export request time, UTC | Body bytes | Relevant content |\n|---|---|---:|---|\n| [48](https://collusion.wiki/explorer/page/dse~PoliceWageAgeSequenceMar10Collab.html#rev-48), record `7b5fab87146d714b3dff277db29e4714` | 2026-06-19 22:04:04 | 12,649 | Contains the old 2,047-byte continuation passage. |\n| [49](https://collusion.wiki/explorer/page/dse~PoliceWageAgeSequenceMar10Collab.html#rev-49), record `4067985c68fa8ffba33fb935b8f35730` | 2026-06-20 00:22:04 | 179 | Export-declared recreation stub; none of that passage. |\n| [50](https://collusion.wiki/explorer/page/dse~PoliceWageAgeSequenceMar10Collab.html#rev-50), record `d665647d5129a51ca24e40cbd774224c` | 2026-06-20 03:45:08 | 4,597 | Stub plus two identical sections, each containing the old passage and a new 162-byte status paragraph. |\n\nThe exact retained-body relation is **4,597 = 179 + 2 × (2,047 + 162)**. The old passage has SHA-256 `35ae2f5cc601a605d08ed582856814d94fb512d05314fdfa8d67a9208c0db963`; its UTF-8 byte spans are `[6987,9034)` in revision48 and `[179,2226)` / `[2388,4435)` in revision50. These are zero-based, half-open spans. The 2,209-byte repeated section has SHA-256 `fb3f9878155bede9015b24f28244f952b2cd50142f5b1326b4a0ebe2d2f10530`.\n\nThe export records a June 19 deletion before revision49. Its short stub claims an archive holds a prior table; the later text's reappearance does not establish an archive retrieval. Source13 body rows and source19 event rows share one released source, so they are not independent witnesses. A declared save-pointer relation is not additional native write evidence.\n\nA separate bounded review of retained native request/change records supports this selected sequence on **June 20, 2026**:\n\n- **03:43:43 UTC:** a section1 form-save request and matching native change entry, native revision2.\n- **03:44:05–03:44:34 UTC:** 28 selected archive-version requests for this page, covering versions1.51–1.79 except1.67.\n- **03:45:08 UTC:** another section1 form-save request and matching native change entry, native revision3, **85 seconds** after the first.\n\nBoth saves share the recorded summary `DEC28 slow-tier R2` and an earlier edit-context timestamp, but the complete requests differ. Both text fields retain only the `(NN)` sentinel: neither submitted body is available. The change entries also lack resulting bodies. The archive records retain requested versions, without response status/body or a recorded method. These selected records are positive observations, not an exhaustive request history.\n\n## Acceptance criteria\n\n- [ ] Recover a source-qualified body resulting from the first save, or returned archive/body and transformation evidence that discriminates where the duplicate section entered this exact sequence. Identify the precise page, source-scoped version or event, readable bytes, SHA-256, capture provenance and clock basis. Explain the linkage to the selected save window without relying on caller identity.\n- [ ] Compare the recovered content with the 179-byte stub, the 2,047-byte old passage, the 162-byte status paragraph and both copies in revision50. Preserve complete bodies and document every decoding or normalization step separately from original hashes.\n- [ ] State which alternatives the new evidence supports or rules out: successive appends, stale editor/section content, already-duplicated input, or another supported transformation. A local demonstration of possible software behavior alone does not establish what happened in this case.\n- [ ] Keep export indices48/49/50 distinct from native revisions2/3 and archive-version labels. Source13/19 share a publisher; matching labels or clocks do not create independent witnesses. `(NN)` is not an actual empty submission. An issued archive request is not a returned body, proof of reading it, or evidence that the same actor made a later edit.\n- [ ] Report the remaining uncertainty. Recovering a relevant archive body or excluding one mechanism can be useful partial evidence. Full resolution requires a new artifact tied to this sequence that answers the missing-body or transformation question; repeating the final duplicate, generic engine behavior, or search misses is insufficient. Do not infer authenticated actors, task success, harness origin or copying direction beyond the supplied evidence.\n\n## Contribution boundaries\n\nUse retained evidence and ordinary authorized publication or archival sources. Do not replay recorded edits, commands, counters or proxy targets, mutate historical pages, or bypass access controls. Keep credentials, private request tokens, IP addresses and caller identifiers out of public submissions. Authored task clocks, native record times, export assertions and new capture times remain separate.\n\nTo announce an attempt, post a comment containing only `/attempt`. Put scope and findings in a separate comment. Submit a reproducible evidence package in a PR and address each criterion; use `Refs` for partial work. The question stays **OPEN** until a full answer passes maintainer review. Accepted evidence receives public credit; no cash reward or exclusive claim is offered.\n", "limits": "Use retained evidence and ordinary authorized publication or archival sources. Do not replay recorded edits, commands, counters or proxy targets, mutate historical pages, or bypass access controls. Keep credentials, private request tokens, IP addresses and caller identifiers out of public submissions. Authored task clocks, native record times, export assertions and new capture times remain separate.\n\nTo announce an attempt, post a comment containing only /attempt. Put scope and findings in a separate comment. Submit a reproducible evidence package in a PR and address each criterion; use Refs for partial work. The question stays OPEN until a full answer passes maintainer review. Accepted evidence receives public credit; no cash reward or exclusive claim is offered.", "sources": [], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/65", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/65", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/65#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-07T19:29:03Z", "areas": ["data-quality"]}, {"id": "bounty-59", "number": 59, "teaser": null, "title": "Identify the source and full filters for the Roi Et Q2 male studies series, 2013–2021", "status": "in-review", "question": "What primary data table or documented reproducible query matches all nine values below for Roi Et province (TH45), males not in the labor force because of studies, Quarter 2? Recover the age range, unit and series version from evidence; those dimensions are missing from the paste. Thailand’s National Statistical Office (NSO) is a proposed source family, not an authenticated publisher of this series.", "source_context": "The held native API /raw field of 1fad07cb contains this complete 197-byte UTF-8 body, including its final newline (SHA256 d1fa02c2009b9bdc5f861a85dfb204c59c2dca2ff8b35b53d9f8395aa5e065f7):\n\ntext\nRoi Et province (TH45) - Males not in labor force because of studies, Quarter 2\n2013: 46,308\n2014: 32,212\n2015: 35,083\n2016: 36,227\n2017: 40,810\n2018: 36,313\n2019: 35,040\n2020: 38,827\n2021: 37,842\n\n\nThe separate native title is Roi Et province (TH45) male studies Q2 2013-2021. The completed independent review of three objects distinguishes two partial titles from their actual bodies:\n\n| Native object | Complete title | Complete body |\n|---|---|---|\n| 6db42cfc | ROIETA1 2013 46308 2014 32212 2015 35083 | x |\n| d826348b | ROIETA 2013 46308 2014 32212 2015 35083 | Roi Et data segment1 |\n\nThe two titles carry the 2013–2015 pairs in order. Removing only the comma from each full-table value yields the title’s digit string; the strings are not literally equal before that transformation. Neither fragment body contains those pairs. These titles do not independently supply the full task filter or the 2016–2021 rows, and their correspondence establishes no parent/reply relationship.\n\nThe wider retained set includes five value-only titles, ROIETA4–ROIETA8 (8812970e, 21c68f36, 5d1004ff, 64d1bc5e, e3657127, whose complete bodies are x. These titles carry ordered value chunks without explicit years; their order alone supplies neither literal year labels nor the complete filters.", "deliverables": ["An answer should provide:\n\n- An exact public source URL and table/series identifier, or a documented query with enough filter and extraction detail to reproduce the result.\n- Evidence for the entire selector conjunction: Roi Et/TH45, males, not in the labor force, studies, Quarter 2; document the source’s age range, unit and version/revision explicitly. Preserve a missing dimension as unresolved.\n- A year-by-year comparison of all nine values, retaining original strings and identifying any comma removal, scaling, rounding or calendar conversion. A wrong province, sex, status, reason or quarter is a nonmatch. A complete match requires all nine year/value pairs under documented equivalent transformations and a supported series version; unexplained differences remain partial.\n- Source captures and hashes, acquisition clocks, and the source’s own publication/version assertions separately. Preserve reproducible comparison steps.\n\nAn official hostname, an annual average, a different-quarter table or a coincident single value is insufficient. A prior indexed NSO table concerns Quarter 3 of 2003; it supports only the proposed source family and cannot supply missing filters for this series."], "source_heading": "Starting evidence", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "An answer should provide:\n\n- An exact public source URL and table/series identifier, or a documented query with enough filter and extraction detail to reproduce the result.\n- Evidence for the entire selector conjunction: Roi Et/TH45, males, not in the labor force, studies, Quarter 2; document the source’s age range, unit and version/revision explicitly. Preserve a missing dimension as unresolved.\n- A year-by-year comparison of all nine values, retaining original strings and identifying any comma removal, scaling, rounding or calendar conversion. A wrong province, sex, status, reason or quarter is a nonmatch. A complete match requires all nine year/value pairs under documented equivalent transformations and a supported series version; unexplained differences remain partial.\n- Source captures and hashes, acquisition clocks, and the source’s own publication/version assertions separately. Preserve reproducible comparison steps.\n\nAn official hostname, an annual average, a different-quarter table or a coincident single value is insufficient. A prior indexed NSO table concerns Quarter 3 of 2003; it supports only the proposed source family and cannot supply missing filters for this series."}], "research_notes": [], "issue_text": "<!-- swarmstatus:roiet-q2-studies-source-filters -->\n\n## Question\n\nWhat primary data table or documented reproducible query matches all nine values below for Roi Et province (TH45), males not in the labor force because of studies, Quarter 2? Recover the age range, unit and series version from evidence; those dimensions are missing from the paste. Thailand’s National Statistical Office (NSO) is a proposed source family, not an authenticated publisher of this series.\n\n## Starting evidence\n\nThe held native API `/raw` field of [1fad07cb](https://pastebin.k4be.pl/view/1fad07cb) contains this complete 197-byte UTF-8 body, including its final newline (SHA256 `d1fa02c2009b9bdc5f861a85dfb204c59c2dca2ff8b35b53d9f8395aa5e065f7`):\n\n```text\nRoi Et province (TH45) - Males not in labor force because of studies, Quarter 2\n2013: 46,308\n2014: 32,212\n2015: 35,083\n2016: 36,227\n2017: 40,810\n2018: 36,313\n2019: 35,040\n2020: 38,827\n2021: 37,842\n```\n\nThe separate native title is `Roi Et province (TH45) male studies Q2 2013-2021`. The completed independent review of three objects distinguishes two partial titles from their actual bodies:\n\n| Native object | Complete title | Complete body |\n|---|---|---|\n| [6db42cfc](https://pastebin.k4be.pl/view/6db42cfc) | `ROIETA1 2013 46308 2014 32212 2015 35083` | `x` |\n| [d826348b](https://pastebin.k4be.pl/view/d826348b) | `ROIETA 2013 46308 2014 32212 2015 35083` | `Roi Et data segment1` |\n\nThe two titles carry the 2013–2015 pairs in order. Removing only the comma from each full-table value yields the title’s digit string; the strings are not literally equal before that transformation. Neither fragment body contains those pairs. These titles do not independently supply the full task filter or the 2016–2021 rows, and their correspondence establishes no parent/reply relationship.\n\nThe wider retained set includes five value-only titles, `ROIETA4`–`ROIETA8` ([8812970e](https://pastebin.k4be.pl/view/8812970e), [21c68f36](https://pastebin.k4be.pl/view/21c68f36), [5d1004ff](https://pastebin.k4be.pl/view/5d1004ff), [64d1bc5e](https://pastebin.k4be.pl/view/64d1bc5e), [e3657127](https://pastebin.k4be.pl/view/e3657127)), whose complete bodies are `x`. These titles carry ordered value chunks without explicit years; their order alone supplies neither literal year labels nor the complete filters.\n\n## Acceptance criteria\n\nAn answer should provide:\n\n- An exact public source URL and table/series identifier, or a documented query with enough filter and extraction detail to reproduce the result.\n- Evidence for the entire selector conjunction: Roi Et/TH45, males, not in the labor force, studies, Quarter 2; document the source’s age range, unit and version/revision explicitly. Preserve a missing dimension as unresolved.\n- A year-by-year comparison of all nine values, retaining original strings and identifying any comma removal, scaling, rounding or calendar conversion. A wrong province, sex, status, reason or quarter is a nonmatch. A complete match requires all nine year/value pairs under documented equivalent transformations and a supported series version; unexplained differences remain partial.\n- Source captures and hashes, acquisition clocks, and the source’s own publication/version assertions separately. Preserve reproducible comparison steps.\n\nAn official hostname, an annual average, a different-quarter table or a coincident single value is insufficient. A prior indexed NSO table concerns Quarter 3 of 2003; it supports only the proposed source family and cannot supply missing filters for this series.\n\n## Partial results and limits\n\nA retained source table or reproducible query that establishes only part of the series can be a useful partial result. Missing dimensions, rows or unexplained differences remain open; a partial does not satisfy all criteria.\n\nThe native service asserts March 11, 2026 creation times for the three representative objects; the retained API acquisitions occurred on September 5, 2026. These assertions do not independently date the historical full bodies. The years 2013–2021 are data years. This question concerns source and filter recovery, distinct from [chronology issue #54](https://github.com/aadarwal/swarmstatus-bounties/issues/54), which covers historical dating of a separate 13-object set. A matching source would establish content correspondence, without proving copying direction, a particular actor, a unique task or benchmark identity, an official answer fetch, successful use or peer receipt.\n\nAccepted evidence receives public credit; no cash reward is offered. A claim is not exclusive. Follow [the contribution guide](https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md). To announce work, post a comment containing only `/attempt`; describe your scope or findings in a separate comment.\n\n\n<!-- swarmstatus:roiet-2021-q2-primary-source -->\n### Research note: one matching source row (2026-09-05)\n\nThe current [NSO Roi Et provincial Labour Force Survey report](https://roiet.nso.go.th/images/64.pdf#page=29) contains **37,842** for **2021, Quarter 2, male, not in the labour force because of studies**. Table 1 on physical PDF page 29 places this value in the estimated population-count section for people aged 15 and over. It matches the pasted `2021: 37,842` line and its stated province, sex, labour-force status, reason and quarter. Same-table controls distinguish Q2 all sexes (74,522), Q2 female (36,680), Q1 male (36,447), the four-quarter male average (36,660), and the Q2 male percentage (9.2).\n\nThe retained PDF is 37 pages, 3,581,294 bytes, SHA256 `5e49092ff4cf7c79ee523e919c691a478de2bf17be54666211fd6be758a8130d`, captured on 2026-09-05 at 23:04:39.961564–23:04:44.230401 UTC. Its report data year is B.E. 2564 (2021); its imprint states B.E. 2565 (2022). These source assertions do not independently establish historical PDF or paste availability.\n\nThis is a **one-year partial comparison**. The other eight years, their age/unit definitions, and the original series version remain unresolved. The search excerpt at the same URL described a different 2020 table; that excerpt has not been verified against a retained primary document. The separate 2019 candidate returned HTTP 403 and yielded no PDF. Neither indexed candidate fills the remaining gap, and this match does not identify the source actually used to produce the paste. The question remains open with its full acceptance criteria.\n", "limits": "", "sources": [], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/59", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/59", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/59#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-07T19:29:09Z", "areas": ["data-quality"]}, {"id": "bounty-58", "number": 58, "teaser": null, "title": "Recover the source version behind the France vehicle-energy table (2006–2010)", "status": "open", "question": "Which source dataset, versioned export or archived response supports the exact France cars/light-trucks energy table for 2006–2010 stored in these two Faster-it objects? Recover the source provenance and compare all selectors and five ordered rows.", "source_context": "Both objects are on the same Faster-it installation:\n\n- a637721f has a 540-byte decoded body containing a Source line, CSV header and five rows. Body SHA256: 386a7cdb532e1d77a95c1f1ce15a22ae9e5235eb8de342b3635f403efa41f688.\n- 8ad90359 stores the five rounded numbers in its title. Its 97-byte body supplies source/rounding context and omits sector and flow. Body SHA256: 3ca9a41c74bc6659d3a9c84a73631cf7e7615dd39a50461a4f5682bc136f5dc1.\n\nThe first Source line names api.iea.org/eei-explorer with country=France, sector=Passenger+transport, flow=E_FINAL, endUse=Cars%2Flight+trucks and csv=true. This is a source claim in the paste, not a retained official response.\n\nIts header is Country,Tab,Flow,EndUse,Activity,Unit,Year,Value. Every row has France, Passenger transport, E_FINAL, Cars/light trucks, NA and PJ in the first six fields. Unit, activity and data years are row fields, not additional URL parameters.\n\n| Year | Exact value in first body (PJ) | Value in second title |\n|---|---:|---:|\n| 2006 | 1146.88 | 1146.9 |\n| 2007 | 1154.2 | 1154.2 |\n| 2008 | 1142.05 | 1142.1 |\n| 2009 | 1150.54 | 1150.5 |\n| 2010 | 1165.96 | 1166.0 |\n\nIndependent review reproduced these retained strings and their body-to-title relationship. Decimal half-up to one place produces the title values. At the exact tie 1142.05, half-up yields 1142.1 while half-even yields 1142.0; this does not identify the producer's algorithm or unseen input precision. The two complete bodies are not equal, and the second body does not independently contain the full selector bundle.", "deliverables": ["1. Retain an independently located source artifact with publisher, exact file/row or response locator, bytes/hash and dataset version or release where available. Separate acquisition clocks from source dates and any historical archive evidence.\n2. Establish the complete selector/field bundle and five ordered year/value rows, or document a precise mismatch. Explain each field mapping, unit conversion, revision or precision change instead of silently adjusting the source.\n3. Compare the recovered source with the first body and the second title separately. State what establishes the source relationship and what remains unknown. If a benchmark or original task is found, retain its complete question and stable item provenance; do not infer one from the table alone.\n\nAn endpoint guide alone is a partial result. A new-vehicle fuel-economy series, a different transport category, values without their selectors, or a later copy without source lineage does not resolve the question. A useful source artifact with unresolved version or transformation details can be accepted as a partial while the missing criteria stay open. A mismatch that only rules out one candidate source is a useful partial result; it does not by itself resolve the table's source provenance."], "source_heading": "Starting evidence", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "1. Retain an independently located source artifact with publisher, exact file/row or response locator, bytes/hash and dataset version or release where available. Separate acquisition clocks from source dates and any historical archive evidence.\n2. Establish the complete selector/field bundle and five ordered year/value rows, or document a precise mismatch. Explain each field mapping, unit conversion, revision or precision change instead of silently adjusting the source.\n3. Compare the recovered source with the first body and the second title separately. State what establishes the source relationship and what remains unknown. If a benchmark or original task is found, retain its complete question and stable item provenance; do not infer one from the table alone.\n\nAn endpoint guide alone is a partial result. A new-vehicle fuel-economy series, a different transport category, values without their selectors, or a later copy without source lineage does not resolve the question. A useful source artifact with unresolved version or transformation details can be accepted as a partial while the missing criteria stay open. A mismatch that only rules out one candidate source is a useful partial result; it does not by itself resolve the table's source provenance."}], "research_notes": [], "issue_text": "<!-- swarmstatus:iea-france-energy-source-version -->\n\n## Question\n\nWhich source dataset, versioned export or archived response supports the exact France cars/light-trucks energy table for 2006–2010 stored in these two Faster-it objects? Recover the source provenance and compare all selectors and five ordered rows.\n\n## Starting evidence\n\nBoth objects are on the **same Faster-it installation**:\n\n- [a637721f](https://pastebin.faster-it.de/view/a637721f) has a 540-byte decoded body containing a Source line, CSV header and five rows. Body SHA256: `386a7cdb532e1d77a95c1f1ce15a22ae9e5235eb8de342b3635f403efa41f688`.\n- [8ad90359](https://pastebin.faster-it.de/view/8ad90359) stores the five rounded numbers in its **title**. Its 97-byte body supplies source/rounding context and omits sector and flow. Body SHA256: `3ca9a41c74bc6659d3a9c84a73631cf7e7615dd39a50461a4f5682bc136f5dc1`.\n\nThe first Source line names `api.iea.org/eei-explorer` with `country=France`, `sector=Passenger+transport`, `flow=E_FINAL`, `endUse=Cars%2Flight+trucks` and `csv=true`. This is a source claim in the paste, not a retained official response.\n\nIts header is `Country,Tab,Flow,EndUse,Activity,Unit,Year,Value`. Every row has `France`, `Passenger transport`, `E_FINAL`, `Cars/light trucks`, `NA` and `PJ` in the first six fields. Unit, activity and data years are row fields, not additional URL parameters.\n\n| Year | Exact value in first body (PJ) | Value in second title |\n|---|---:|---:|\n| 2006 | 1146.88 | 1146.9 |\n| 2007 | 1154.2 | 1154.2 |\n| 2008 | 1142.05 | 1142.1 |\n| 2009 | 1150.54 | 1150.5 |\n| 2010 | 1165.96 | 1166.0 |\n\nIndependent review reproduced these retained strings and their body-to-title relationship. Decimal half-up to one place produces the title values. At the exact tie `1142.05`, half-up yields `1142.1` while half-even yields `1142.0`; this does not identify the producer's algorithm or unseen input precision. The two complete bodies are not equal, and the second body does not independently contain the full selector bundle.\n\n## Acceptance criteria\n\n1. Retain an independently located source artifact with publisher, exact file/row or response locator, bytes/hash and dataset version or release where available. Separate acquisition clocks from source dates and any historical archive evidence.\n2. Establish the complete selector/field bundle and five ordered year/value rows, or document a precise mismatch. Explain each field mapping, unit conversion, revision or precision change instead of silently adjusting the source.\n3. Compare the recovered source with the first body and the second title separately. State what establishes the source relationship and what remains unknown. If a benchmark or original task is found, retain its complete question and stable item provenance; do not infer one from the table alone.\n\nAn endpoint guide alone is a partial result. A new-vehicle fuel-economy series, a different transport category, values without their selectors, or a later copy without source lineage does not resolve the question. A useful source artifact with unresolved version or transformation details can be accepted as a partial while the missing criteria stay open. A mismatch that only rules out one candidate source is a useful partial result; it does not by itself resolve the table's source provenance.\n\n## Timing and contribution limits\n\nThe complete native views were captured on 5 September 2026 and reused in this investigation. They show only a relative age; retained native absolute creation epochs remain null. Data years, source release dates, third-party publication assertions and acquisition clocks are distinct. A current source match does not independently date either paste or establish writers, copying direction, exchange, delivery or task use. This is a source-content question, separate from [#54's early-body chronology](https://github.com/aadarwal/swarmstatus-bounties/issues/54).\n\nAccepted evidence receives public credit; no cash reward is offered. A claim is not exclusive. Follow [the contribution guide](https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md). To announce work, post a comment containing only `/attempt`; describe your scope or findings in a separate comment.\n", "limits": "", "sources": [], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/58", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/58", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/58#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-07T19:29:11Z", "areas": ["data-quality"]}, {"id": "bounty-56", "number": 56, "teaser": null, "title": "Explain the opposite 1996/97 away ranks in two EPL paste tables", "status": "in-review", "question": "Which underlying standings artifact and ranking definition account for the opposite 1996/97 away ranks asserted for Sunderland and Middlesbrough in two retained EPL paste tables?\n\nRecover source-qualified data and explicit ordering rules sufficient to reproduce the ranks, or show that the two texts use different definitions. Neither paste is currently treated as correct.", "source_context": "Both current native API bodies were preserved and independently compared:\n\n| Retained paste | Sunderland away | Middlesbrough away | Parsed raw body |\n|---|---:|---:|---|\n| 57492617 — EPL 1995-00 home-away relegation data | 19 | 20 | 750 UTF-8 bytes; SHA256 5055ba9b9cdd61a86b3960c8a5638e4d82577bd0c708571d2878e4735c2434f0 |\n| 9629c5f3 — epl95 | 20 | 19 | 1,345 UTF-8 bytes; SHA256 b3d6652358d93f25fa92083bef3a27709ff483983e34e9659b3803dd4ea73e1c |\n\nThese assertions occur on raw line 3 in each body. Both give overall positions 18 and 19 for these teams. The first text describes the overall bottom-three entries with their overall/home/away positions; the second lists separate home and away bottom-three groups and says H/A ranks are sorted by points, goal difference and goals for. No underlying 1996/97 points/GD/GF response or complete comparator has been recovered for this comparison.\n\nThe full five-season texts are not equivalent selections. For example, the first lists Crystal Palace in 1997/98 as overall 20 and away 9, while the second contains some home/away bottom-three teams explicitly marked not relegated. Missing teams across those selections are not automatically contradictions.\n\nA separate control pair, 3b740bef and 11e9447e, repeats the same complete 587-byte 2000/01 body: SHA256 ba3b77f8b20132366f222b84cfcd871fede5d8d0a57fec15eba74ac8c8ab5c1e. Its local list ordinals 1–3 must not be silently relabelled as global ranks 18–20. Repeated text on two IDs does not independently establish the source, writers or task use.", "deliverables": ["1. Retain a primary standings artifact or source response for the exact competition, 1996/97 season and away-table selection, with original bytes, hash, locator and separately stated acquisition/source dates. Include enough standings context to establish global ranks, including the relevant points, goal difference and goals-for values.\n2. State the comparator: sort directions, tie handling and any relevant position or points adjustments. Explain what evidence establishes these rules rather than assuming them from a short column label.\n3. Reproduce or distinguish the two claimed assignments. If different explicit definitions account for both, document that result rather than declaring one paste wrong. Keep overall-relegated selection, away-bottom-three selection, local ordinals and global positions separate. Preserve literal team labels and state any comparison-only alias mappings explicitly.\n\nA source for another season, an overall-only table, an unsupported restatement of either paste, or the repeated 2000/01 body does not satisfy this question."], "source_heading": "Starting evidence", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "1. Retain a primary standings artifact or source response for the exact competition, 1996/97 season and away-table selection, with original bytes, hash, locator and separately stated acquisition/source dates. Include enough standings context to establish global ranks, including the relevant points, goal difference and goals-for values.\n2. State the comparator: sort directions, tie handling and any relevant position or points adjustments. Explain what evidence establishes these rules rather than assuming them from a short column label.\n3. Reproduce or distinguish the two claimed assignments. If different explicit definitions account for both, document that result rather than declaring one paste wrong. Keep overall-relegated selection, away-bottom-three selection, local ordinals and global positions separate. Preserve literal team labels and state any comparison-only alias mappings explicitly.\n\nA source for another season, an overall-only table, an unsupported restatement of either paste, or the repeated 2000/01 body does not satisfy this question."}], "research_notes": [], "issue_text": "<!-- swarmstatus:epl-1996-away-rank-source -->\n\n## Question\n\nWhich underlying standings artifact and ranking definition account for the opposite 1996/97 away ranks asserted for Sunderland and Middlesbrough in two retained EPL paste tables?\n\nRecover source-qualified data and explicit ordering rules sufficient to reproduce the ranks, or show that the two texts use different definitions. Neither paste is currently treated as correct.\n\n## Starting evidence\n\nBoth current native API bodies were preserved and independently compared:\n\n| Retained paste | Sunderland away | Middlesbrough away | Parsed raw body |\n|---|---:|---:|---|\n| [57492617 — EPL 1995-00 home-away relegation data](https://pastebin.k4be.pl/view/57492617) | 19 | 20 | 750 UTF-8 bytes; SHA256 `5055ba9b9cdd61a86b3960c8a5638e4d82577bd0c708571d2878e4735c2434f0` |\n| [9629c5f3 — epl95](https://pastebin.k4be.pl/view/9629c5f3) | 20 | 19 | 1,345 UTF-8 bytes; SHA256 `b3d6652358d93f25fa92083bef3a27709ff483983e34e9659b3803dd4ea73e1c` |\n\nThese assertions occur on raw line 3 in each body. Both give overall positions 18 and 19 for these teams. The first text describes the overall bottom-three entries with their overall/home/away positions; the second lists separate home and away bottom-three groups and says H/A ranks are sorted by points, goal difference and goals for. No underlying 1996/97 points/GD/GF response or complete comparator has been recovered for this comparison.\n\nThe full five-season texts are not equivalent selections. For example, the first lists Crystal Palace in 1997/98 as overall 20 and away 9, while the second contains some home/away bottom-three teams explicitly marked not relegated. Missing teams across those selections are not automatically contradictions.\n\nA separate control pair, [3b740bef](https://pastebin.k4be.pl/view/3b740bef) and [11e9447e](https://pastebin.k4be.pl/view/11e9447e), repeats the same complete 587-byte 2000/01 body: SHA256 `ba3b77f8b20132366f222b84cfcd871fede5d8d0a57fec15eba74ac8c8ab5c1e`. Its local list ordinals 1–3 must not be silently relabelled as global ranks 18–20. Repeated text on two IDs does not independently establish the source, writers or task use.\n\n## Acceptance criteria\n\n1. Retain a primary standings artifact or source response for the exact competition, 1996/97 season and away-table selection, with original bytes, hash, locator and separately stated acquisition/source dates. Include enough standings context to establish global ranks, including the relevant points, goal difference and goals-for values.\n2. State the comparator: sort directions, tie handling and any relevant position or points adjustments. Explain what evidence establishes these rules rather than assuming them from a short column label.\n3. Reproduce or distinguish the two claimed assignments. If different explicit definitions account for both, document that result rather than declaring one paste wrong. Keep overall-relegated selection, away-bottom-three selection, local ordinals and global positions separate. Preserve literal team labels and state any comparison-only alias mappings explicitly.\n\nA source for another season, an overall-only table, an unsupported restatement of either paste, or the repeated 2000/01 body does not satisfy this question.\n\n## Partial results and limits\n\nA newly retained relevant source artifact with incomplete ranking rules can be a useful partial result; the question stays open until the required comparison is supported. A reproducible correction to this stated discrepancy must cite the exact retained strings and interpretation.\n\nThe four native objects were captured on 5 September 2026; one uses an earlier held capture, not a refetch. Current service-created assertions, acquisition intervals and data years remain separate. This question does not claim an independently dated historical publication, a reply relationship, identified actors, copying direction or receipt/use. It covers these four inspected objects, not unacquired companion pastes, and is separate from the 13-object chronology question [#54](https://github.com/aadarwal/swarmstatus-bounties/issues/54).\n\nAccepted evidence receives public credit; no cash reward is offered. A claim is not exclusive. Follow [the contribution guide](https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md) and preserve unresolved criteria. To announce work, post a comment containing only `/attempt`; describe your scope or findings in a separate comment.\n", "limits": "", "sources": [], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/56", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/56", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/56#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-06T23:12:02Z", "areas": ["data-quality"]}, {"id": "bounty-54", "number": 54, "teaser": null, "title": "Independently date 13 K4be bodies with December 2025–March 2026 creation assertions", "status": "open", "question": "Thirteen public K4be pastes currently declare creation dates from 14 December 2025 to 1 March 2026. When can their complete stored bodies first be independently shown to have been public, and is there a specific evidenced relationship to the later task-sharing corpus?\n\nThe early dates are service assertions captured on September 5, not established historical swarm events. Timing and content relationships are separate parts of this question.", "source_context": "Discovery credit: Jonas Wiedermann-Möller / j0wimo, whose post was supplied by the user. We received the post's text from the user; our attempted direct X read returned 403. The original month grouping did not specify a year. The UTC years below come from interpreting each captured API created value as Unix seconds.\n\n| Paste | Current service-created assertion (UTC) |\n|---|---|\n| 3ae5f54b | 2025-12-14T04:51:46Z |\n| 514333ed | 2026-01-01T10:56:05Z |\n| 316996fe | 2026-01-01T10:56:06Z |\n| 5329a841 | 2026-02-26T14:49:24Z |\n| bd44d381 | 2026-02-26T14:50:18Z |\n| 680ec235 | 2026-02-26T14:52:19Z |\n| d78a30b4 | 2026-02-26T20:15:44Z |\n| 0263afe2 | 2026-02-26T20:15:47Z |\n| 06d98526 | 2026-03-01T13:24:18Z |\n| 17bbf392 | 2026-03-01T13:30:22Z |\n| c9601cdf | 2026-03-01T13:31:19Z |\n| 1806ec31 | 2026-03-01T13:32:39Z |\n| 5a4aa403 | 2026-03-01T13:33:28Z |\n\nAll thirteen view pages and their documented API representations were captured successfully on 5 September 2026. The HTML acquisition intervals span 20:23:41.496574–20:24:27.802742 UTC. Those are the earliest complete-body observations in the evidence currently reviewed, not the pastes' first-publication dates.\n\nIndependent local comparison of the saved HTML and API representations confirms all thirteen complete stored texts after explicit one-time HTML-entity decoding and CRLF-to-LF normalization. The original rendered paste was checked separately from the reply-prefilled textarea; its display comparison also accounts for nonbreaking spaces and blank-line fillers. Raw HTML, API-envelope and extracted-text hashes remain distinct. A complete stored paste can itself be an excerpt of an upstream document.\n\nThe January 1 pair has identical unmodified API raw strings and creation assertions one second apart. The other bodies include NBA arithmetic, financial tables, a finance question/answer/program block, population/CO₂ figures, airport data and an India armed-forces series. These similarities and timestamps do not identify a writer, reply or copying direction. None of the thirteen captured API envelopes supplies a native parent/reply field.\n\nA FinQA dataset-origin comparison is a lead, not an established item match. A benchmark release date would date source material; it would not date publication of these paste bodies or prove task execution.", "deliverables": ["Recover an independently dated, source-located historical artifact for an exact listed object that preserves its complete stored body. Supply the original bytes or a public-safe reproducible package, content hash, exact locator, acquisition provenance and capture-clock/timezone basis.", "Compare that body with the current captured version using stated decoding and whitespace rules. Preserve both raw hashes; distinguish exact equality, normalized equality, excerpts and changed versions.", "State the defensible body-present-by bound. A historical capture normally proves presence by its capture time, not first publication. Assess service-created, import/repost and edit assertions only where separate evidence supports their meaning; do not diagnose backdating or authenticity from a timestamp alone.", "Report each of the thirteen objects separately, including unresolved ones. A dated subset or a documented earlier version is a useful partial result. Cohort-wide dating remains open while any required object's historical body date is unsupported.", "Test a concrete, fully specified content relationship against an independently located later record, if one is found. Preserve both source locators, complete relevant question/table/answer/program or ordered selector bundle, native/capture clocks and copy/import lineage.", "Distinguish an exact distinctive task match from common benchmark text, shared numbers, generic prompts, same-host reuse or curator copies. Matching a public dataset item establishes that content relationship only; it does not demonstrate a message, receipt, agent identity, task use or transfer direction.", "State the result of this relationship stage independently from the chronology stage. If no discriminating relationship is supported, report it as unresolved. Earlier dated text alone cannot close a coordination claim; a bounded nonmatch cannot establish that no relationship exists.\n\nA contribution may advance either stage. Mark partials as partial and keep unresolved criteria open. Search misses, current metadata alone, and a diagram joining similar titles do not meet these evidence requirements.\n\n<details>\n<summary>Current extracted-text SHA-256 controls</summary>\n\nThese hashes cover each unmodified JSON-parsed API raw string encoded as UTF-8, including its original line endings, before entity/line-ending normalization. They are not hashes of the API envelopes or HTML pages.\n\ntext\n3ae5f54b 4561a13e3c59846d9d02bf2fad88964598632b2f9a86d106d9e2f5667cb4621d\n514333ed 76da74d9471e7b12892b538b85d3fba70005799a56f6081f1878ff8b16bfe485\n316996fe 76da74d9471e7b12892b538b85d3fba70005799a56f6081f1878ff8b16bfe485\n5329a841 94d46d8d52654d063d1056eede571b94c39889a0b6d953ed873df31900395948\nbd44d381 ec89a96fa17f4347f5976e1e392cc5a9fa20cdd05b8ab650e5156db4e89c09d7\n680ec235 c36c211ea5138142c7bf257386df02fc5e77f59293e1349f5a597d82e095363a\nd78a30b4 05b598b81113a62916b83a0bbe8e4eccacb4ff62cb83faf19f1f5dd6dac6870c\n0263afe2 1d9adba5396d886107cba63d3d4667a44c22cbb91ece7a89e9aa121752bf581b\n06d98526 1d7c03707602cbb5378e88a6d8f3955633d276bf4b0fe76a1a8f84b4907fefef\n17bbf392 cef636fa0156ef66700b6cff2669721279804dfbf83025db98878a07789d791a\nc9601cdf 64254238457d888ea0a4c90e48948c1d96f9e8e3c52936e5f46386df04d2f8e0\n1806ec31 d28c67fdf6b313dda342202ce5059fb3287e36a39bcf3d7b192f2c9e5107470b\n5a4aa403 373bc8c396433321ac42a05402d588c097c6b3fd7df413954e6686acf4f6a112\n\n\n</details>"], "source_heading": "Starting evidence", "acceptance_stages": [{"heading": "Required evidence: chronology", "text": "Recover an independently dated, source-located historical artifact for an exact listed object that preserves its complete stored body. Supply the original bytes or a public-safe reproducible package, content hash, exact locator, acquisition provenance and capture-clock/timezone basis.\nCompare that body with the current captured version using stated decoding and whitespace rules. Preserve both raw hashes; distinguish exact equality, normalized equality, excerpts and changed versions.\nState the defensible body-present-by bound. A historical capture normally proves presence by its capture time, not first publication. Assess service-created, import/repost and edit assertions only where separate evidence supports their meaning; do not diagnose backdating or authenticity from a timestamp alone.\nReport each of the thirteen objects separately, including unresolved ones. A dated subset or a documented earlier version is a useful partial result. Cohort-wide dating remains open while any required object's historical body date is unsupported."}, {"heading": "Separate evidence: relationship to later material", "text": "Test a concrete, fully specified content relationship against an independently located later record, if one is found. Preserve both source locators, complete relevant question/table/answer/program or ordered selector bundle, native/capture clocks and copy/import lineage.\nDistinguish an exact distinctive task match from common benchmark text, shared numbers, generic prompts, same-host reuse or curator copies. Matching a public dataset item establishes that content relationship only; it does not demonstrate a message, receipt, agent identity, task use or transfer direction.\nState the result of this relationship stage independently from the chronology stage. If no discriminating relationship is supported, report it as unresolved. Earlier dated text alone cannot close a coordination claim; a bounded nonmatch cannot establish that no relationship exists.\n\nA contribution may advance either stage. Mark partials as partial and keep unresolved criteria open. Search misses, current metadata alone, and a diagram joining similar titles do not meet these evidence requirements.\n\n<details>\n<summary>Current extracted-text SHA-256 controls</summary>\n\nThese hashes cover each unmodified JSON-parsed API raw string encoded as UTF-8, including its original line endings, before entity/line-ending normalization. They are not hashes of the API envelopes or HTML pages.\n\ntext\n3ae5f54b 4561a13e3c59846d9d02bf2fad88964598632b2f9a86d106d9e2f5667cb4621d\n514333ed 76da74d9471e7b12892b538b85d3fba70005799a56f6081f1878ff8b16bfe485\n316996fe 76da74d9471e7b12892b538b85d3fba70005799a56f6081f1878ff8b16bfe485\n5329a841 94d46d8d52654d063d1056eede571b94c39889a0b6d953ed873df31900395948\nbd44d381 ec89a96fa17f4347f5976e1e392cc5a9fa20cdd05b8ab650e5156db4e89c09d7\n680ec235 c36c211ea5138142c7bf257386df02fc5e77f59293e1349f5a597d82e095363a\nd78a30b4 05b598b81113a62916b83a0bbe8e4eccacb4ff62cb83faf19f1f5dd6dac6870c\n0263afe2 1d9adba5396d886107cba63d3d4667a44c22cbb91ece7a89e9aa121752bf581b\n06d98526 1d7c03707602cbb5378e88a6d8f3955633d276bf4b0fe76a1a8f84b4907fefef\n17bbf392 cef636fa0156ef66700b6cff2669721279804dfbf83025db98878a07789d791a\nc9601cdf 64254238457d888ea0a4c90e48948c1d96f9e8e3c52936e5f46386df04d2f8e0\n1806ec31 d28c67fdf6b313dda342202ce5059fb3287e36a39bcf3d7b192f2c9e5107470b\n5a4aa403 373bc8c396433321ac42a05402d588c097c6b3fd7df413954e6686acf4f6a112\n\n\n</details>"}], "research_notes": [{"heading": "Research note — exact benchmark item match, 5 September 2026", "text": "An authorized acquisition of the official FinQA repository at commit 0f16e2867befa6840783e58be38c9efb9229d742 supplied a concrete source-content match.\n\nIn dataset/dev.json at that commit, zero-based array index 619, item AMT/2008/page_32.pdf-4, the exact qa.question, qa.answer and ordered qa.program strings reconstruct the entire 1806ec31 paste as its three labeled Question/Answer/Program lines, including its final newline. The answer field is 29.2%; the program is treated as inert text, not executed.\n\nThe relevant source table's zero-based table[4] records the 2008 quarter-ended-December-31 high of 37.28 and low of 19.35; post_text[0] records the February 13, 2009 closing price of 28.85. These are the dataset's retained fields, not a new financial calculation or independently verified financial result.\n\n- Official dataset/dev.json SHA-256: a847fb7e0d61a3125a1e2909852df6b89f1ee64d2c5ff1bf689e332214deee51.\n- Complete unmodified paste raw string, UTF-8 SHA-256: d28c67fdf6b313dda342202ce5059fb3287e36a39bcf3d7b192f2c9e5107470b.\n- Retained API envelope SHA-256: 0eae1795033297f81364303acda7ae18ad021b1e31cc6d9e6d2bf43e2dce5583.\n- Repository checkout acquisition: 2026-09-05 20:37:37.302002–20:37:38.802853 UTC. Its Git commit metadata is a separate assertion, not a historical capture of K4be.\n\nA second reviewer independently checked the local Git blob and the paste's original API text. This establishes an exact benchmark-item content relationship. It does not establish that the poster obtained it directly from this repository, executed the program, belonged to the later corpus, or posted the complete body at the service's asserted creation time. Both historical paste dating and any discriminating later-corpus relationship remain open. The original question and acceptance criteria above are unchanged.\n\n\n\n\n\n### Research source context: Humana table (5 September 2026)\n\nAn independently reviewed comparison of three held paste bodies with the already acquired official FinQA training data supports these narrower content relationships:\n\n| Paste | Reviewed match |\n|---|---|\n| 5329a841 and bd44d381 | All six 2010–2015 dates and all 18 amounts, in HUM / S&P 500 / Peer Group row order, after explicit dollar-line joining, entity decoding and label handling as applicable. This is structured table equality, not raw-body equality. |\n| 680ec235 | Only the two HUM cells: 2011 = $162 and 2012 = $128. The other years and comparison rows are absent. |\n\nThe same table appears at zero-based training indices 149, 538 and 677, IDs HUM/2015/page_46.pdf-2, -1 and -3, with distinct questions and programs. None of those complete questions or programs appears in the three pastes. Index 677 relies on dividend prose and amounts absent from all three, providing a same-table/different-task control. Prose also differs: literal and whitespace-only comparisons fail; one longer sentence requires separately documented punctuation-artifact repair. Shorter bodies omit or rewrite text.\n\nSource pin: commit 0f16e2867befa6840783e58be38c9efb9229d742; dataset/train.json SHA256 49f237eb9779b569473b26b08048867d04635a7cc39ad6a7a5664c55bb428db6. Independent review covered these three bodies and three source rows, the body and training-file hashes, table extent, transformations and the index-677 control. It did not repeat an all-dataset search. No source program was evaluated.\n\nThis adds report-content context only. Historical body dates, direct copying route, unique task identity, actors and use or receipt remain unestablished. The existing AMT note and all question criteria remain intact and open.\n\n\n### Research source context: India personnel CSV (5 September 2026)\n\nIndependent comparison connects the complete decoded 06d98526 paste to a selected excerpt of the current official OWID CSV: India/IND, 1995–2010, all 16 ordered rows, 80 data-field strings and five header fields, including the literal Asia region and integer values.\n\nThe original API raw string is 537 UTF-8 bytes and contains two header &quot; entities. Decoding only those entities gives 527 bytes. Source physical header line 1 plus lines 2374–2389 is 528 bytes; removing exactly its final LF produces the same complete 527 bytes. No sorting, deduplication, numeric rounding or general whitespace collapse was used. The full 191,776-byte CSV and whole India series are not equal to the paste. The same-file 1994–2011 control adds two rows and fails equality.\n\nRetained source pins:\n- CSV SHA256 7b2a1fc134dd7ffb6357ef2c14d23aac43641dae509736f659ac02e0811db28d; complete HTTP 200 capture at 21:25:41.228393–21:25:41.693128 UTC on 5 September 2026.\n- Metadata SHA256 fd91766e0573187e099ac89fb80c5df36d6a3fef1ac970c8c9279c59d49930ed; complete HTTP 200 capture at 21:25:58.335651–21:25:58.703451 UTC. It identifies personnel variable 1294141 / WDI 129, lastUpdated 2026-07-27, and region variable 900801, lastUpdated 2023-01-01.\n\nThese source metadata dates, data years, acquisition clocks and the paste's native creation assertion remain separate. No explicit immutable historical dataset version was supplied. This establishes current selected-data content context, not a unique benchmark/task, direct copying route, historical paste publication, actor, successful use or receipt. Both question tracks and their original criteria remain open."}], "issue_text": "<!-- swarmstatus:k4be-early-body-dating -->\n\nThirteen public K4be pastes currently declare creation dates from **14 December 2025 to 1 March 2026**. When can their **complete stored bodies** first be independently shown to have been public, and is there a specific evidenced relationship to the later task-sharing corpus?\n\nThe early dates are service assertions captured on September 5, not established historical swarm events. Timing and content relationships are separate parts of this question.\n\n## Starting evidence\n\nDiscovery credit: **Jonas Wiedermann-Möller / j0wimo**, whose [post was supplied by the user](https://x.com/j0wimo/status/2096330564337078641). We received the post's text from the user; our attempted direct X read returned 403. The original month grouping did not specify a year. The UTC years below come from interpreting each captured API `created` value as Unix seconds.\n\n| Paste | Current service-created assertion (UTC) |\n|---|---|\n| [3ae5f54b](https://pastebin.k4be.pl/view/3ae5f54b) | 2025-12-14T04:51:46Z |\n| [514333ed](https://pastebin.k4be.pl/view/514333ed) | 2026-01-01T10:56:05Z |\n| [316996fe](https://pastebin.k4be.pl/view/316996fe) | 2026-01-01T10:56:06Z |\n| [5329a841](https://pastebin.k4be.pl/view/5329a841) | 2026-02-26T14:49:24Z |\n| [bd44d381](https://pastebin.k4be.pl/view/bd44d381) | 2026-02-26T14:50:18Z |\n| [680ec235](https://pastebin.k4be.pl/view/680ec235) | 2026-02-26T14:52:19Z |\n| [d78a30b4](https://pastebin.k4be.pl/view/d78a30b4) | 2026-02-26T20:15:44Z |\n| [0263afe2](https://pastebin.k4be.pl/view/0263afe2) | 2026-02-26T20:15:47Z |\n| [06d98526](https://pastebin.k4be.pl/view/06d98526) | 2026-03-01T13:24:18Z |\n| [17bbf392](https://pastebin.k4be.pl/view/17bbf392) | 2026-03-01T13:30:22Z |\n| [c9601cdf](https://pastebin.k4be.pl/view/c9601cdf) | 2026-03-01T13:31:19Z |\n| [1806ec31](https://pastebin.k4be.pl/view/1806ec31) | 2026-03-01T13:32:39Z |\n| [5a4aa403](https://pastebin.k4be.pl/view/5a4aa403) | 2026-03-01T13:33:28Z |\n\nAll thirteen view pages and their documented API representations were captured successfully on **5 September 2026**. The HTML acquisition intervals span **20:23:41.496574–20:24:27.802742 UTC**. Those are the earliest complete-body observations in the evidence currently reviewed, not the pastes' first-publication dates.\n\nIndependent local comparison of the saved HTML and API representations confirms all thirteen complete stored texts after explicit one-time HTML-entity decoding and CRLF-to-LF normalization. The original rendered paste was checked separately from the reply-prefilled textarea; its display comparison also accounts for nonbreaking spaces and blank-line fillers. Raw HTML, API-envelope and extracted-text hashes remain distinct. A complete stored paste can itself be an excerpt of an upstream document.\n\nThe January 1 pair has identical unmodified API `raw` strings and creation assertions one second apart. The other bodies include NBA arithmetic, financial tables, a finance question/answer/program block, population/CO₂ figures, airport data and an India armed-forces series. These similarities and timestamps do not identify a writer, reply or copying direction. None of the thirteen captured API envelopes supplies a native parent/reply field.\n\nA FinQA dataset-origin comparison is a lead, **not an established item match**. A benchmark release date would date source material; it would not date publication of these paste bodies or prove task execution.\n\n## What has already been checked\n\n- Exact identifiers were absent from the fixed focused/full database snapshots and from the checked prior native captures, manifests and supplied 16,579-document pack. These are scoped coverage gaps, not proof that the pages were newly created or absent elsewhere.\n- Three exact Wayback CDX queries for `3ae5f54b`, `514333ed` and `316996fe`, restricted to successful HTML captures before September 5 and collapsed by month, returned HTTP 200 with empty arrays. No archived body was obtained. Other archives, statuses, content types and versions remain untested; do not interpret these results as general absence.\n- A coarse older search-index rendition of the NBA page does not provide an independently dated complete-body artifact.\n- Relative ages, current API dates, HTTP response dates, expiry/hit-update fields, body data years and later acquisition clocks are separate observations. The current records do not supply a historical import or body-edit clock.\n\n## Required evidence: chronology\n\n- [ ] Recover an independently dated, source-located historical artifact for an exact listed object that preserves its complete stored body. Supply the original bytes or a public-safe reproducible package, content hash, exact locator, acquisition provenance and capture-clock/timezone basis.\n- [ ] Compare that body with the current captured version using stated decoding and whitespace rules. Preserve both raw hashes; distinguish exact equality, normalized equality, excerpts and changed versions.\n- [ ] State the defensible **body-present-by** bound. A historical capture normally proves presence by its capture time, not first publication. Assess service-created, import/repost and edit assertions only where separate evidence supports their meaning; do not diagnose backdating or authenticity from a timestamp alone.\n- [ ] Report each of the thirteen objects separately, including unresolved ones. A dated subset or a documented earlier version is a useful partial result. Cohort-wide dating remains open while any required object's historical body date is unsupported.\n\n## Separate evidence: relationship to later material\n\n- [ ] Test a concrete, fully specified content relationship against an independently located later record, if one is found. Preserve both source locators, complete relevant question/table/answer/program or ordered selector bundle, native/capture clocks and copy/import lineage.\n- [ ] Distinguish an exact distinctive task match from common benchmark text, shared numbers, generic prompts, same-host reuse or curator copies. Matching a public dataset item establishes that content relationship only; it does not demonstrate a message, receipt, agent identity, task use or transfer direction.\n- [ ] State the result of this relationship stage independently from the chronology stage. If no discriminating relationship is supported, report it as unresolved. Earlier dated text alone cannot close a coordination claim; a bounded nonmatch cannot establish that no relationship exists.\n\nA contribution may advance either stage. Mark partials as partial and keep unresolved criteria open. Search misses, current metadata alone, and a diagram joining similar titles do not meet these evidence requirements.\n\n<details>\n<summary>Current extracted-text SHA-256 controls</summary>\n\nThese hashes cover each unmodified JSON-parsed API `raw` string encoded as UTF-8, including its original line endings, before entity/line-ending normalization. They are not hashes of the API envelopes or HTML pages.\n\n```text\n3ae5f54b 4561a13e3c59846d9d02bf2fad88964598632b2f9a86d106d9e2f5667cb4621d\n514333ed 76da74d9471e7b12892b538b85d3fba70005799a56f6081f1878ff8b16bfe485\n316996fe 76da74d9471e7b12892b538b85d3fba70005799a56f6081f1878ff8b16bfe485\n5329a841 94d46d8d52654d063d1056eede571b94c39889a0b6d953ed873df31900395948\nbd44d381 ec89a96fa17f4347f5976e1e392cc5a9fa20cdd05b8ab650e5156db4e89c09d7\n680ec235 c36c211ea5138142c7bf257386df02fc5e77f59293e1349f5a597d82e095363a\nd78a30b4 05b598b81113a62916b83a0bbe8e4eccacb4ff62cb83faf19f1f5dd6dac6870c\n0263afe2 1d9adba5396d886107cba63d3d4667a44c22cbb91ece7a89e9aa121752bf581b\n06d98526 1d7c03707602cbb5378e88a6d8f3955633d276bf4b0fe76a1a8f84b4907fefef\n17bbf392 cef636fa0156ef66700b6cff2669721279804dfbf83025db98878a07789d791a\nc9601cdf 64254238457d888ea0a4c90e48948c1d96f9e8e3c52936e5f46386df04d2f8e0\n1806ec31 d28c67fdf6b313dda342202ce5059fb3287e36a39bcf3d7b192f2c9e5107470b\n5a4aa403 373bc8c396433321ac42a05402d588c097c6b3fd7df413954e6686acf4f6a112\n```\n\n</details>\n\n## Contribution boundaries\n\nUse retained evidence and ordinary authorized publication/archive reads. Do not replay embedded proxy or executable payloads, mutate historical posts, bypass source stops or access controls, or treat newly posted investigation material as historical evidence. Avoid private identity data and attribution from public labels. The thirteen observations remain new research intake, not an accepted historical-swarm milestone.\n\nTo announce work, comment `/attempt` alone, then describe your scope and first concrete finding separately. Claims are not exclusive. Accepted evidence receives public credit; **no cash reward is offered**. Follow the [contribution guide](https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md) and submit a reproducible public-safe partial or answer package.\n\n\n## Research note — exact benchmark item match, 5 September 2026\n\nAn authorized acquisition of the [official FinQA repository at commit `0f16e2867befa6840783e58be38c9efb9229d742`](https://github.com/czyssrs/FinQA/tree/0f16e2867befa6840783e58be38c9efb9229d742) supplied a concrete source-content match.\n\nIn [`dataset/dev.json` at that commit](https://github.com/czyssrs/FinQA/blob/0f16e2867befa6840783e58be38c9efb9229d742/dataset/dev.json), zero-based array index **619**, item **`AMT/2008/page_32.pdf-4`**, the exact `qa.question`, `qa.answer` and ordered `qa.program` strings reconstruct the entire [`1806ec31` paste](https://pastebin.k4be.pl/view/1806ec31) as its three labeled Question/Answer/Program lines, including its final newline. The answer field is `29.2%`; the program is treated as inert text, not executed.\n\nThe relevant source table's zero-based `table[4]` records the 2008 quarter-ended-December-31 high of `37.28` and low of `19.35`; `post_text[0]` records the February 13, 2009 closing price of `28.85`. These are the dataset's retained fields, not a new financial calculation or independently verified financial result.\n\n- Official `dataset/dev.json` SHA-256: `a847fb7e0d61a3125a1e2909852df6b89f1ee64d2c5ff1bf689e332214deee51`.\n- Complete unmodified paste `raw` string, UTF-8 SHA-256: `d28c67fdf6b313dda342202ce5059fb3287e36a39bcf3d7b192f2c9e5107470b`.\n- Retained API envelope SHA-256: `0eae1795033297f81364303acda7ae18ad021b1e31cc6d9e6d2bf43e2dce5583`.\n- Repository checkout acquisition: **2026-09-05 20:37:37.302002–20:37:38.802853 UTC**. Its Git commit metadata is a separate assertion, not a historical capture of K4be.\n\nA second reviewer independently checked the local Git blob and the paste's original API text. This establishes an exact benchmark-item content relationship. It does **not** establish that the poster obtained it directly from this repository, executed the program, belonged to the later corpus, or posted the complete body at the service's asserted creation time. Both historical paste dating and any discriminating later-corpus relationship remain open. The original question and acceptance criteria above are unchanged.\n\n<!-- swarmstatus:k4be-finqa-item-context -->\n\n\n<!-- swarmstatus:k4be-humana-report-context -->\n### Research source context: Humana table (5 September 2026)\n\nAn independently reviewed comparison of three held paste bodies with the already acquired [official FinQA training data](https://github.com/czyssrs/FinQA/blob/0f16e2867befa6840783e58be38c9efb9229d742/dataset/train.json) supports these narrower content relationships:\n\n| Paste | Reviewed match |\n|---|---|\n| `5329a841` and `bd44d381` | All six 2010–2015 dates and all 18 amounts, in HUM / S&P 500 / Peer Group row order, after explicit dollar-line joining, entity decoding and label handling as applicable. This is structured table equality, not raw-body equality. |\n| `680ec235` | Only the two HUM cells: 2011 = $162 and 2012 = $128. The other years and comparison rows are absent. |\n\nThe same table appears at zero-based training indices **149, 538 and 677**, IDs `HUM/2015/page_46.pdf-2`, `-1` and `-3`, with distinct questions and programs. None of those complete questions or programs appears in the three pastes. Index 677 relies on dividend prose and amounts absent from all three, providing a same-table/different-task control. Prose also differs: literal and whitespace-only comparisons fail; one longer sentence requires separately documented punctuation-artifact repair. Shorter bodies omit or rewrite text.\n\nSource pin: commit `0f16e2867befa6840783e58be38c9efb9229d742`; `dataset/train.json` SHA256 `49f237eb9779b569473b26b08048867d04635a7cc39ad6a7a5664c55bb428db6`. Independent review covered these three bodies and three source rows, the body and training-file hashes, table extent, transformations and the index-677 control. It did not repeat an all-dataset search. No source program was evaluated.\n\nThis adds report-content context only. Historical body dates, direct copying route, unique task identity, actors and use or receipt remain unestablished. The existing AMT note and all question criteria remain intact and open.\n\n\n### Research source context: India personnel CSV (5 September 2026)\n\nIndependent comparison connects the complete decoded [06d98526 paste](https://pastebin.k4be.pl/view/06d98526) to a **selected excerpt of the current [official OWID CSV](https://ourworldindata.org/grapher/armed-forces-personnel.csv?v=1&csvType=full&useColumnShortNames=false)**: India/IND, 1995–2010, all 16 ordered rows, 80 data-field strings and five header fields, including the literal Asia region and integer values.\n\nThe original API raw string is 537 UTF-8 bytes and contains two header `&quot;` entities. Decoding only those entities gives 527 bytes. Source physical header line 1 plus lines 2374–2389 is 528 bytes; removing exactly its final LF produces the same complete 527 bytes. No sorting, deduplication, numeric rounding or general whitespace collapse was used. The full 191,776-byte CSV and whole India series are not equal to the paste. The same-file 1994–2011 control adds two rows and fails equality.\n\nRetained source pins:\n- CSV SHA256 `7b2a1fc134dd7ffb6357ef2c14d23aac43641dae509736f659ac02e0811db28d`; complete HTTP 200 capture at 21:25:41.228393–21:25:41.693128 UTC on 5 September 2026.\n- [Metadata](https://ourworldindata.org/grapher/armed-forces-personnel.metadata.json?v=1&csvType=full&useColumnShortNames=false) SHA256 `fd91766e0573187e099ac89fb80c5df36d6a3fef1ac970c8c9279c59d49930ed`; complete HTTP 200 capture at 21:25:58.335651–21:25:58.703451 UTC. It identifies personnel variable 1294141 / WDI 129, lastUpdated 2026-07-27, and region variable 900801, lastUpdated 2023-01-01.\n\nThese source metadata dates, data years, acquisition clocks and the paste's native creation assertion remain separate. No explicit immutable historical dataset version was supplied. This establishes current selected-data content context, not a unique benchmark/task, direct copying route, historical paste publication, actor, successful use or receipt. Both question tracks and their original criteria remain open.\n\n<!-- swarmstatus:k4be-india-current-csv-context -->\n", "limits": "Use retained evidence and ordinary authorized publication/archive reads. Do not replay embedded proxy or executable payloads, mutate historical posts, bypass source stops or access controls, or treat newly posted investigation material as historical evidence. Avoid private identity data and attribution from public labels. The thirteen observations remain new research intake, not an accepted historical-swarm milestone.\n\nTo announce work, comment /attempt alone, then describe your scope and first concrete finding separately. Claims are not exclusive. Accepted evidence receives public credit; no cash reward is offered. Follow the contribution guide and submit a reproducible public-safe partial or answer package.", "sources": [], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/54", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/54", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/54#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T22:08:34Z", "areas": ["data-quality"]}, {"id": "bounty-52", "number": 52, "teaser": null, "title": "Corroborate the language backup-CA signal and recipient observation", "status": "in-review", "question": "A retained wiki report says a California backup counter was incremented during the fifth question of a language-statistics task. Can a dated historical response and a recipient observation corroborate that backup signal?\n\nThe wiki already contains written verification and thanks about the primary CA5 signal. Those messages matter, but they do not identify a read of the separate backup key. This question keeps the two channels distinct.", "source_context": "- Fallback protocol, revision 6, canonical record 3a66183d3ffd6a020165b37191d0a0df: explains the backup address pattern and marks the TEST key as noise. Its recorded revision-request time is 2026-06-17 00:56:56 UTC.\n- Same-namespace test warning, revision 8, record cba292c8eba48f6286d0e4b0f406d792: the writer reports test increments for CA, NM and TX. Later text reports a conflicting baseline/cache observation. A positive counter value cannot be interpreted without these controls.\n- Backup-increment report, revision 28, record e2283e6e88f5f845c0773c20521227cb, line 56: “Primary CA5 count=1 created exactly then; backup CA increment also present.” This is an authored claim, not a retained counter transaction. The page's later maintenance account concerns primary CA5 and must not be transferred to the backup key.\n- Primary signal report, revision 2, verification/preparation, revision 3, and thanks, revision 4 preserve a concrete written exchange about primary CA5. Canonical records: 72d821b692c0d740673f1f7ad0e80ff3, e77c9f5f7c494e913fbe94df49dd32bc, d0385444c42eb38d51c4d87b20923d21. Their recorded revision-request times are 01:34:24, 01:41:32 and 01:52:51 UTC on June 17. The 428- and 679-second differences are wiki-edit intervals, not counter-read latency.\n\nA separately retained response acquired on 2026-09-04 at 21:45:54.107423 UTC contains the following body, including a final newline:\n\njson\n{\"key\":\"langr5backup4813_CA\",\"value\":4}\n\n\nIts SHA-256 is 86af04818147e0d4da840ee5d92b76747a5bacbdef75a6c910b78fb637e951a0. This later state does not date any increment or prove a June recipient read. The selected wiki rows all derive from the same source export; agreement between our database snapshots is not an independent historical source.", "deliverables": ["Preserve a historical, source-located response/state or transaction for the exact backup key, with readable bytes, content hash, acquisition provenance and clock basis. Explain its relation to the reported R5 event; a new current lookup does not answer this.", "Preserve a separately source-located recipient observation identifying the backup key, relevant task and observed state, with its own provenance and clock basis. Distinguish a written verification/acknowledgment claim from retained transport or response evidence corroborating the read. Credit a newly recovered claim at that level; if a backup read remains unsubstantiated, leave that stage open rather than borrowing primary CA5 thanks.", "Test the task-signal interpretation against the language namespace's own test/cache controls and plausible later changes. Do not subtract an asserted baseline to count participants or reuse a threshold from another task.", "Keep authored task time, wiki revision-request time, archive/capture time and actual service-event time separate. Retain uncertainty, copy/import lineage and contradictory evidence.", "State whether the evidence supports or contradicts the specific reported backup signal, and which stages remain open. Corroborating full closure requires both the historical backup-state/task link and the backup-specific recipient link above. Evidence tying the reported change to testing or later manipulation can contradict the task-signal interpretation; explain that source linkage rather than treating a search miss or later snapshot as disproof. A contribution resolving only one stage, or adding an acknowledgment without corroborating its claimed read, is partial.\n\nDisplayed handles, shared targets and timing alone do not authenticate separate people, models or operators. No evidence currently selects between a single writer/controller, shared instructions, copied tests or independently acting participants."], "source_heading": "Starting evidence", "acceptance_stages": [{"heading": "What an answer must establish", "text": "Preserve a historical, source-located response/state or transaction for the exact backup key, with readable bytes, content hash, acquisition provenance and clock basis. Explain its relation to the reported R5 event; a new current lookup does not answer this.\nPreserve a separately source-located recipient observation identifying the backup key, relevant task and observed state, with its own provenance and clock basis. Distinguish a written verification/acknowledgment claim from retained transport or response evidence corroborating the read. Credit a newly recovered claim at that level; if a backup read remains unsubstantiated, leave that stage open rather than borrowing primary CA5 thanks.\nTest the task-signal interpretation against the language namespace's own test/cache controls and plausible later changes. Do not subtract an asserted baseline to count participants or reuse a threshold from another task.\nKeep authored task time, wiki revision-request time, archive/capture time and actual service-event time separate. Retain uncertainty, copy/import lineage and contradictory evidence.\nState whether the evidence supports or contradicts the specific reported backup signal, and which stages remain open. Corroborating full closure requires both the historical backup-state/task link and the backup-specific recipient link above. Evidence tying the reported change to testing or later manipulation can contradict the task-signal interpretation; explain that source linkage rather than treating a search miss or later snapshot as disproof. A contribution resolving only one stage, or adding an acknowledgment without corroborating its claimed read, is partial.\n\nDisplayed handles, shared targets and timing alone do not authenticate separate people, models or operators. No evidence currently selects between a single writer/controller, shared instructions, copied tests or independently acting participants."}], "research_notes": [], "issue_text": "<!-- swarmstatus:language-backup-ca-receipt -->\n\nA retained wiki report says a California backup counter was incremented during the fifth question of a language-statistics task. Can a dated historical response and a recipient observation corroborate that **backup** signal?\n\nThe wiki already contains written verification and thanks about the **primary CA5** signal. Those messages matter, but they do not identify a read of the separate backup key. This question keeps the two channels distinct.\n\n## Task and exact key\n\nThe task concerned the 2022 ACS 1-year estimate for French (including Cajun), table B16001, and the share of US speakers living in a requested state. Retained context names Texas, Louisiana, New York and New Hampshire before the reported California R5. The source cube is `acs_ygl_language_spoken_at_home_by_english_ability_2016_1`, measure `Languages Spoken`.\n\nThe backup key is `langr5backup4813_CA`; the distinct primary key is `CA5`. These are inert identifiers, not instructions to query or increment either service. The source's California 11.2% answer narrative is not independently validated here; another retained table gives 10.6%.\n\n## Starting evidence\n\n- [Fallback protocol, revision 6](https://collusion.wiki/explorer/page/dse~DataUSALanguageJul17R5.html#rev-6), canonical record `3a66183d3ffd6a020165b37191d0a0df`: explains the backup address pattern and marks the TEST key as noise. Its recorded revision-request time is 2026-06-17 00:56:56 UTC.\n- [Same-namespace test warning, revision 8](https://collusion.wiki/explorer/page/dse~DataUSALanguageR5SignalNow.html#rev-8), record `cba292c8eba48f6286d0e4b0f406d792`: the writer reports test increments for CA, NM and TX. Later text reports a conflicting baseline/cache observation. A positive counter value cannot be interpreted without these controls.\n- [Backup-increment report, revision 28](https://collusion.wiki/explorer/page/dse~DataUSALanguageR5SignalNow.html#rev-28), record `e2283e6e88f5f845c0773c20521227cb`, line 56: “Primary CA5 count=1 created exactly then; backup CA increment also present.” This is an authored claim, not a retained counter transaction. The page's later maintenance account concerns primary CA5 and must not be transferred to the backup key.\n- [Primary signal report, revision 2](https://collusion.wiki/explorer/page/dse~LangR5SignalSep01.html#rev-2), [verification/preparation, revision 3](https://collusion.wiki/explorer/page/dse~LangR5SignalSep01.html#rev-3), and [thanks, revision 4](https://collusion.wiki/explorer/page/dse~LangR5SignalSep01.html#rev-4) preserve a concrete written exchange about primary CA5. Canonical records: `72d821b692c0d740673f1f7ad0e80ff3`, `e77c9f5f7c494e913fbe94df49dd32bc`, `d0385444c42eb38d51c4d87b20923d21`. Their recorded revision-request times are 01:34:24, 01:41:32 and 01:52:51 UTC on June 17. The 428- and 679-second differences are wiki-edit intervals, not counter-read latency.\n\nA separately retained response acquired on **2026-09-04 at 21:45:54.107423 UTC** contains the following body, including a final newline:\n\n```json\n{\"key\":\"langr5backup4813_CA\",\"value\":4}\n```\n\nIts SHA-256 is `86af04818147e0d4da840ee5d92b76747a5bacbdef75a6c910b78fb637e951a0`. This later state does not date any increment or prove a June recipient read. The selected wiki rows all derive from the same source export; agreement between our database snapshots is not an independent historical source.\n\n## What an answer must establish\n\n- [ ] Preserve a historical, source-located response/state or transaction for the **exact backup key**, with readable bytes, content hash, acquisition provenance and clock basis. Explain its relation to the reported R5 event; a new current lookup does not answer this.\n- [ ] Preserve a separately source-located recipient observation identifying the backup key, relevant task and observed state, with its own provenance and clock basis. Distinguish a written verification/acknowledgment claim from retained transport or response evidence corroborating the read. Credit a newly recovered claim at that level; if a backup read remains unsubstantiated, leave that stage open rather than borrowing primary CA5 thanks.\n- [ ] Test the task-signal interpretation against the language namespace's own test/cache controls and plausible later changes. Do not subtract an asserted baseline to count participants or reuse a threshold from another task.\n- [ ] Keep authored task time, wiki revision-request time, archive/capture time and actual service-event time separate. Retain uncertainty, copy/import lineage and contradictory evidence.\n- [ ] State whether the evidence supports or contradicts the specific reported backup signal, and which stages remain open. Corroborating full closure requires both the historical backup-state/task link and the backup-specific recipient link above. Evidence tying the reported change to testing or later manipulation can contradict the task-signal interpretation; explain that source linkage rather than treating a search miss or later snapshot as disproof. A contribution resolving only one stage, or adding an acknowledgment without corroborating its claimed read, is partial.\n\nDisplayed handles, shared targets and timing alone do not authenticate separate people, models or operators. No evidence currently selects between a single writer/controller, shared instructions, copied tests or independently acting participants.\n\n## Contribution boundaries\n\nUse already-retained evidence and appropriate ordinary archival or publication sources. Do not replay recorded counter/proxy/payload URLs, change service state or historical messages, bypass access controls, or treat a new investigation post as historical evidence. This question does not request a live counter probe or bulk private-origin data.\n\nComment `/attempt` on this issue with your first concrete finding. Claims are not exclusive. Accepted evidence receives public credit; no cash reward is offered. Preserve original receipts and provide a reproducible, public-safe evidence package. Search misses alone are not an answer.\n", "limits": "Use already-retained evidence and appropriate ordinary archival or publication sources. Do not replay recorded counter/proxy/payload URLs, change service state or historical messages, bypass access controls, or treat a new investigation post as historical evidence. This question does not request a live counter probe or bulk private-origin data.\n\nComment /attempt on this issue with your first concrete finding. Claims are not exclusive. Accepted evidence receives public credit; no cash reward is offered. Preserve original receipts and provide a reproducible, public-safe evidence package. Search misses alone are not an answer.", "sources": [], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/52", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/52", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/52#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T22:00:12Z", "areas": ["data-quality"]}, {"id": "bounty-46", "number": 46, "teaser": null, "title": "Independently date the Jotspot Clark newsletter reference", "status": "open", "question": "What is the earliest independently verifiable body capture of Jotspot’s Economics reference reading 2010 note containing its exact Clark newsletter reference? Determine whether that evidence supports, narrows or contradicts the note’s displayed creation and modification dates.", "source_context": "- Retained Jotspot record is already present in both installed database snapshots. Its article says “Research” and links “Archive reading.” This is a stored source reference, not an observed peer exchange.\n- Current site metadata asserts creation 2026-06-01T15:03:22.012084+00:00 and modification 2026-06-01T15:31:10.118407+00:00. Those are site assertions, not independently authenticated write times.\n- A retained ordinary GET acquired the note on 2026-09-05T13:44:39.434809Z–13:44:40.044769Z: HTTP 200, 13,274 bytes, SHA256 edddd6353c747a5168e1ec5f17779244e133c6e73f85079d338cfbb8798fac82. This dates an observation in September. The canonical HTML has the same article and site dates, but two hidden form-token values differ; keep the raw captures and hashes separate.\n- The complete reference also occurs in three original ProWiki bodies: AgentClarkNewsletterRefDX, AgentClarkRetryCookie, and JohnClarkRefsNewsletterQ2026. Their June 1 clocks are source-export request-log assertions. They do not independently date the Jotspot body or show a message to that note.\n\nRecorded reference, for literal comparison only:\n\ntext\nhttps://pure.md/web.archive.org/web/20130525012744id_/www.clarku.edu/departments/economics/pdf/newsletter%202010color.pdf\n\n\nThe user supplied the initial Jotspot lead; this note was selected from its public list. No new-body recovery is claimed by this question.", "deliverables": ["Supply an independently timestamped body capture or native revision for this exact Jotspot object, with its public locator, relevant content, acquisition provenance and digest.", "Establish whether the exact Clark reference is present; distinguish a full-URL match from a title, listing or topic match.", "Separate archive observation time, native revision/site assertions, wiki export clocks and filename/archive-component dates.", "Explain what the evidence establishes or contradicts about when this reference appeared, preserving alternative explanations and uncertainty.", "Distinguish an independent observation from a later copy, curator archive or researcher-created invitation.\n\nAll dates are eligible. Evidence bounding a later appearance is useful. An earlier listing without the body is context; a negative archive query is not proof of absence."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Supply an independently timestamped body capture or native revision for this exact Jotspot object, with its public locator, relevant content, acquisition provenance and digest.\nEstablish whether the exact Clark reference is present; distinguish a full-URL match from a title, listing or topic match.\nSeparate archive observation time, native revision/site assertions, wiki export clocks and filename/archive-component dates.\nExplain what the evidence establishes or contradicts about when this reference appeared, preserving alternative explanations and uncertainty.\nDistinguish an independent observation from a later copy, curator archive or researcher-created invitation.\n\nAll dates are eligible. Evidence bounding a later appearance is useful. An earlier listing without the body is context; a negative archive query is not proof of absence."}], "research_notes": [], "issue_text": "## Question\n\nWhat is the earliest independently verifiable body capture of [Jotspot’s Economics reference reading 2010 note](https://jotspot.io/j/sxt2xy8q) containing its exact Clark newsletter reference? Determine whether that evidence supports, narrows or contradicts the note’s displayed creation and modification dates.\n\n## Existing evidence\n\n- [Retained Jotspot record](https://swarmstatus.com/api/record?id=5330f7290d1390e8774a9347ac016411) is already present in both installed database snapshots. Its article says “Research” and links “Archive reading.” This is a stored source reference, not an observed peer exchange.\n- Current site metadata asserts creation `2026-06-01T15:03:22.012084+00:00` and modification `2026-06-01T15:31:10.118407+00:00`. Those are site assertions, not independently authenticated write times.\n- A retained ordinary GET acquired the note on `2026-09-05T13:44:39.434809Z–13:44:40.044769Z`: HTTP 200, 13,274 bytes, SHA256 `edddd6353c747a5168e1ec5f17779244e133c6e73f85079d338cfbb8798fac82`. This dates an observation in September. The canonical HTML has the same article and site dates, but two hidden form-token values differ; keep the raw captures and hashes separate.\n- The complete reference also occurs in three original ProWiki bodies: [AgentClarkNewsletterRefDX](https://swarmstatus.com/api/record?id=9348b4019312fa9f890608f364f257cc), [AgentClarkRetryCookie](https://swarmstatus.com/api/record?id=8708fd7acd191a00ed5b111736676652), and [JohnClarkRefsNewsletterQ2026](https://swarmstatus.com/api/record?id=9657e9c8250b4c906ced3313a84a0c34). Their June 1 clocks are source-export request-log assertions. They do not independently date the Jotspot body or show a message to that note.\n\nRecorded reference, for literal comparison only:\n\n```text\nhttps://pure.md/web.archive.org/web/20130525012744id_/www.clarku.edu/departments/economics/pdf/newsletter%202010color.pdf\n```\n\nThe user supplied the initial Jotspot lead; this note was selected from its public list. No new-body recovery is claimed by this question.\n\n## Acceptance criteria\n\n- [ ] Supply an independently timestamped body capture or native revision for this exact Jotspot object, with its public locator, relevant content, acquisition provenance and digest.\n- [ ] Establish whether the exact Clark reference is present; distinguish a full-URL match from a title, listing or topic match.\n- [ ] Separate archive observation time, native revision/site assertions, wiki export clocks and filename/archive-component dates.\n- [ ] Explain what the evidence establishes or contradicts about when this reference appeared, preserving alternative explanations and uncertainty.\n- [ ] Distinguish an independent observation from a later copy, curator archive or researcher-created invitation.\n\nAll dates are eligible. Evidence bounding a later appearance is useful. An earlier listing without the body is context; a negative archive query is not proof of absence.\n\n## Limits and control\n\n[Jotspot’s NSI note](https://swarmstatus.com/api/record?id=196336d35fd705f1c15258282a8da830) uses `www.nsi.bg`; related captures use `site-test.nsi.bg` with the same opaque filter. That is not full-URL or response equality. Neither note authenticates writers, original-cohort membership, successful retrieval or message delivery.\n\nDo not execute recorded proxy/counter/payload URLs, change historical content, bypass access controls, or treat a current investigation post as historical evidence. This question requests provenance for the Jotspot object, not a fetch of the recorded newsletter target.\n\n## Submission and credit\n\nComment `/attempt` on this issue to state a bounded investigation, then submit an evidence-backed answer file in a pull request. Include source locators, hashes, clock bases and limitations. Use `Closes #ISSUE_NUMBER` only when the whole question is addressed; maintainer review determines resolution.\n\nAccepted evidence receives public credit. No cash reward is offered; a claim is not exclusive and does not by itself earn credit.\n\n<!-- swarmstatus:jotspot-clark-body-date -->\n", "limits": "", "sources": [{"label": "Retained record 5330f729", "url": "https://swarmstatus.com/api/record?id=5330f7290d1390e8774a9347ac016411"}, {"label": "Retained record 9348b401", "url": "https://swarmstatus.com/api/record?id=9348b4019312fa9f890608f364f257cc"}, {"label": "Retained record 8708fd7a", "url": "https://swarmstatus.com/api/record?id=8708fd7acd191a00ed5b111736676652"}], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/46", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/46", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/46#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T22:09:03Z", "areas": ["data-quality"]}, {"id": "bounty-24", "number": 24, "teaser": null, "title": "Verify the missing stages in the Cashiers live exchange", "status": "open", "question": "Determine whether the retained DataUSACashiersMastersSequenceLive3 history supports a complete request → exact later task wording/value → specific acknowledgement chain, and identify any missing independently evidenced stage. Start with the clock-pair requests and later marker below, using every actual intervening revision.", "source_context": "- Primary source\n  Revision 6 asks CashierCoordSep09 for a task/container clock pair and the earliest runner to relay exact Q3 wording/value.\n  time raw: 2026-06-16T10:52:40Z.\n  time utc: 2026-06-16T10:52:40Z.\n  time basis: source_export_reqlog.\n  source sha256: 60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793.\n  Retained record ba7d875d\n\n- Primary source\n  Revision 7 is saved by CashierCoordAgentX and adds its own pair and further requests. It must be diffed against actual revision 6.\n  time raw: 2026-06-16T10:56:21Z.\n  time utc: 2026-06-16T10:56:21Z.\n  time basis: source_export_reqlog.\n  source sha256: 60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793.\n  Retained record 4f955a55\n\n- Primary source\n  Revision 11 asks for fresh clock pairs and May28 status; it is an actual intervening revision.\n  time raw: 2026-06-16T11:08:15Z.\n  time utc: 2026-06-16T11:08:15Z.\n  time basis: source_export_reqlog.\n  source sha256: 60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793.\n  Retained record c6358033\n\n- Primary source\n  Revision 12 adds a May28 marker and must be diffed against actual revision 11, not the previous selected two-person transcript entry.\n  time raw: 2026-06-16T11:09:00Z.\n  time utc: 2026-06-16T11:09:00Z.\n  time basis: source_export_reqlog.\n  source sha256: 60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793.\n  Retained record 57c2c80c", "deliverables": ["Provide exact public source locators plus retained content or archive evidence and its acquisition date.", "State what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.", "Do not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.", "For every proposed step cite its source-qualified revision ID, immediate actual predecessor, exact introduced text and displayed writer/signatory distinction.", "Attach the specific earlier request to each proposed response using explicit content evidence, and label inferred connections.", "Show the actual requested wording/value and a specifically linked acknowledgement before calling the exchange complete.", "Provider stored-reply relations require direct retained evidence; chronology or a thanks phrase alone is insufficient."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Provide exact public source locators plus retained content or archive evidence and its acquisition date.\nState what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.\nDo not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.\nFor every proposed step cite its source-qualified revision ID, immediate actual predecessor, exact introduced text and displayed writer/signatory distinction.\nAttach the specific earlier request to each proposed response using explicit content evidence, and label inferred connections.\nShow the actual requested wording/value and a specifically linked acknowledgement before calling the exchange complete.\nProvider stored-reply relations require direct retained evidence; chronology or a thanks phrase alone is insufficient."}], "research_notes": [], "issue_text": "## Question\n\nDetermine whether the retained DataUSACashiersMastersSequenceLive3 history supports a complete request → exact later task wording/value → specific acknowledgement chain, and identify any missing independently evidenced stage. Start with the clock-pair requests and later marker below, using every actual intervening revision.\n\n## Existing evidence\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~DataUSACashiersMastersSequenceLive3.html#rev-6)\n  Revision 6 asks CashierCoordSep09 for a task/container clock pair and the earliest runner to relay exact Q3 wording/value.\n  time raw: `2026-06-16T10:52:40Z`.\n  time utc: `2026-06-16T10:52:40Z`.\n  time basis: `source_export_reqlog`.\n  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.\n  [Retained record ba7d875d](https://swarmstatus.com/api/record?id=ba7d875dc42c088378a729b9eacaaf70)\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~DataUSACashiersMastersSequenceLive3.html#rev-7)\n  Revision 7 is saved by CashierCoordAgentX and adds its own pair and further requests. It must be diffed against actual revision 6.\n  time raw: `2026-06-16T10:56:21Z`.\n  time utc: `2026-06-16T10:56:21Z`.\n  time basis: `source_export_reqlog`.\n  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.\n  [Retained record 4f955a55](https://swarmstatus.com/api/record?id=4f955a5582c9cedb3e935d45abe3f941)\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~DataUSACashiersMastersSequenceLive3.html#rev-11)\n  Revision 11 asks for fresh clock pairs and May28 status; it is an actual intervening revision.\n  time raw: `2026-06-16T11:08:15Z`.\n  time utc: `2026-06-16T11:08:15Z`.\n  time basis: `source_export_reqlog`.\n  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.\n  [Retained record c6358033](https://swarmstatus.com/api/record?id=c6358033c9b7102db1fa970578c16437)\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~DataUSACashiersMastersSequenceLive3.html#rev-12)\n  Revision 12 adds a May28 marker and must be diffed against actual revision 11, not the previous selected two-person transcript entry.\n  time raw: `2026-06-16T11:09:00Z`.\n  time utc: `2026-06-16T11:09:00Z`.\n  time basis: `source_export_reqlog`.\n  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.\n  [Retained record 57c2c80c](https://swarmstatus.com/api/record?id=57c2c80c79937f80ea68128485f032f6)\n\n## Acceptance criteria\n\n- [ ] Provide exact public source locators plus retained content or archive evidence and its acquisition date.\n- [ ] State what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.\n- [ ] Do not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.\n- [ ] For every proposed step cite its source-qualified revision ID, immediate actual predecessor, exact introduced text and displayed writer/signatory distinction.\n- [ ] Attach the specific earlier request to each proposed response using explicit content evidence, and label inferred connections.\n- [ ] Show the actual requested wording/value and a specifically linked acknowledgement before calling the exchange complete.\n- [ ] Provider stored-reply relations require direct retained evidence; chronology or a thanks phrase alone is insufficient.\n\n## Caveats and alternatives\n\n- The reconstructed page has thirty revisions and five displayed writers. Earlier selected transcripts omitted intervening changes.\n- No provider stored-reply relation was verified. Existing explicit address edges are narrower evidence than an authenticated complete communication chain.\n- Saved text can be copied or quote another writer; the saving label is not automatically the author of every line.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:coverage-conversation-stages -->\n", "limits": "- The reconstructed page has thirty revisions and five displayed writers. Earlier selected transcripts omitted intervening changes.\n- No provider stored-reply relation was verified. Existing explicit address edges are narrower evidence than an authenticated complete communication chain.\n- Saved text can be copied or quote another writer; the saving label is not automatically the author of every line.", "sources": [{"label": "Retained record ba7d875d", "url": "https://swarmstatus.com/api/record?id=ba7d875dc42c088378a729b9eacaaf70"}, {"label": "Retained record 4f955a55", "url": "https://swarmstatus.com/api/record?id=4f955a5582c9cedb3e935d45abe3f941"}, {"label": "Retained record c6358033", "url": "https://swarmstatus.com/api/record?id=c6358033c9b7102db1fa970578c16437"}], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/24", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/24", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/24#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T19:02:21Z", "areas": ["conversations"]}, {"id": "bounty-23", "number": 23, "teaser": null, "title": "Establish defensible event mapping across the conflicting ProWiki exports", "status": "open", "question": "Using native revision identifiers, RCS paths/content hashes and independent timestamps, determine which records can be mapped across the original prowiki and later DSE exports before estimating any clock offset. Resolve the concrete dse~RecentChanges@77 collision as a negative control and provide at least one independently anchored same-event comparison.", "source_context": "- Primary source\n  Original prowiki dse~RecentChanges@77 has RCS 1.77, a retained body and request-log time 2026-06-16T19:32:24Z.\n  time raw: 2026-06-16T19:32:24Z.\n  time utc: 2026-06-16T19:32:24Z.\n  time basis: source_export_reqlog.\n  source sha256: 60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793.\n  Retained record bf8fc3c1\n\n- Primary source\n  Later wiki/dse dse~RecentChanges@77 is a different source-scoped row with no fetched body, recent-changes wall time 2026-09-04T08:26:00+01:00 and no normalized UTC.\n  time raw: 2026-09-04T08:26:00+01:00.\n  time basis: clock_conflict_site_offset.\n  source sha256: cd8a95d51adce94e091c972e38fe8b7935366d77a1b44b5eaa40694b83cba62c.\n  Acquisition record ID: 0e14cad0bf4f2feb6e15f7a494f8b5a6 (outside the focused explorer; use the primary locator above).\n\n- Primary source\n  A separate original conversation explicitly reports a task/container clock pair; these self-reported clocks must remain distinct from request-log observation time.\n  time raw: 2026-06-16T10:52:40Z.\n  time utc: 2026-06-16T10:52:40Z.\n  time basis: source_export_reqlog.\n  source sha256: 60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793.\n  Retained record ba7d875d", "deliverables": ["Provide exact public source locators plus retained content or archive evidence and its acquisition date.", "State what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.", "Do not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.", "Do not match records solely on the unqualified rev_id; preserve dataset/export, native RCS identity and source hash.", "Explain whether apparent differences reflect identifier reuse, different events, missing bodies, time zones or a genuine same-event clock discrepancy.", "An offset estimate must use a independently supported same-event pair and state precision, timezone and residual uncertainty.", "Keep task/scaffold, container, request-log, site-wall and archive clocks in separate fields."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Provide exact public source locators plus retained content or archive evidence and its acquisition date.\nState what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.\nDo not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.\nDo not match records solely on the unqualified rev_id; preserve dataset/export, native RCS identity and source hash.\nExplain whether apparent differences reflect identifier reuse, different events, missing bodies, time zones or a genuine same-event clock discrepancy.\nAn offset estimate must use a independently supported same-event pair and state precision, timezone and residual uncertainty.\nKeep task/scaffold, container, request-log, site-wall and archive clocks in separate fields."}], "research_notes": [], "issue_text": "## Question\n\nUsing native revision identifiers, RCS paths/content hashes and independent timestamps, determine which records can be mapped across the original prowiki and later DSE exports before estimating any clock offset. Resolve the concrete dse~RecentChanges@77 collision as a negative control and provide at least one independently anchored same-event comparison.\n\n## Existing evidence\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~RecentChanges.html#rev-77)\n  Original prowiki dse~RecentChanges@77 has RCS 1.77, a retained body and request-log time 2026-06-16T19:32:24Z.\n  time raw: `2026-06-16T19:32:24Z`.\n  time utc: `2026-06-16T19:32:24Z`.\n  time basis: `source_export_reqlog`.\n  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.\n  [Retained record bf8fc3c1](https://swarmstatus.com/api/record?id=bf8fc3c1afe97998851ba7d1a23b6e1d)\n\n- [Primary source](https://www.wikiservice.at/dse/wiki.cgi?action=browse&id=RecentChanges)\n  Later wiki/dse dse~RecentChanges@77 is a different source-scoped row with no fetched body, recent-changes wall time 2026-09-04T08:26:00+01:00 and no normalized UTC.\n  time raw: `2026-09-04T08:26:00+01:00`.\n  time basis: `clock_conflict_site_offset`.\n  source sha256: `cd8a95d51adce94e091c972e38fe8b7935366d77a1b44b5eaa40694b83cba62c`.\n  Acquisition record ID: `0e14cad0bf4f2feb6e15f7a494f8b5a6` (outside the focused explorer; use the primary locator above).\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~DataUSACashiersMastersSequenceLive3.html#rev-6)\n  A separate original conversation explicitly reports a task/container clock pair; these self-reported clocks must remain distinct from request-log observation time.\n  time raw: `2026-06-16T10:52:40Z`.\n  time utc: `2026-06-16T10:52:40Z`.\n  time basis: `source_export_reqlog`.\n  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.\n  [Retained record ba7d875d](https://swarmstatus.com/api/record?id=ba7d875dc42c088378a729b9eacaaf70)\n\n## Acceptance criteria\n\n- [ ] Provide exact public source locators plus retained content or archive evidence and its acquisition date.\n- [ ] State what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.\n- [ ] Do not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.\n- [ ] Do not match records solely on the unqualified rev_id; preserve dataset/export, native RCS identity and source hash.\n- [ ] Explain whether apparent differences reflect identifier reuse, different events, missing bodies, time zones or a genuine same-event clock discrepancy.\n- [ ] An offset estimate must use a independently supported same-event pair and state precision, timezone and residual uncertainty.\n- [ ] Keep task/scaffold, container, request-log, site-wall and archive clocks in separate fields.\n\n## Caveats and alternatives\n\n- 13,151 audited shared-ID pairs were preserved separately, including 1,706 with gaps greater than 24 hours. These counts do not imply one universal clock offset.\n- The two @77 records are not established as the same event. The missing later body prevents a body-hash comparison.\n- Displayed agent clock claims are evidence of what a source says, not authenticated clock telemetry.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:coverage-source-clock-mapping -->\n", "limits": "- 13,151 audited shared-ID pairs were preserved separately, including 1,706 with gaps greater than 24 hours. These counts do not imply one universal clock offset.\n- The two @77 records are not established as the same event. The missing later body prevents a body-hash comparison.\n- Displayed agent clock claims are evidence of what a source says, not authenticated clock telemetry.", "sources": [{"label": "Retained record bf8fc3c1", "url": "https://swarmstatus.com/api/record?id=bf8fc3c1afe97998851ba7d1a23b6e1d"}, {"label": "Retained record ba7d875d", "url": "https://swarmstatus.com/api/record?id=ba7d875dc42c088378a729b9eacaaf70"}], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/23", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/23", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/23#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T19:02:23Z", "areas": ["data-quality"]}, {"id": "bounty-21", "number": 21, "teaser": null, "title": "Find the source of the ordered five-county IPEDS sequence", "status": "in-review", "question": "Find an independent retained artifact with the ordered counties 05000US06023 → 05000US08069 → 05000US12011 → 05000US38017 → 05000US30031, ipeds_completions, CIP4:1107, Year:2013 and Completions. Determine whether the order comes from a task prompt, a copied query block or another reproducible source.", "source_context": "- Primary source\n  AgentDataQRefsZ1223@2 carries the full five-county ordered query block.\n  time raw: 2026-06-21T08:25:13Z.\n  time utc: 2026-06-21T08:25:13Z.\n  time basis: source_export_reqlog.\n  source sha256: 60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793.\n  Retained record 8685b644\n\n- Primary source\n  TmpTestHelloxx123@3 carries the same ordered block.\n  time raw: 2026-06-21T08:19:31Z.\n  time utc: 2026-06-21T08:19:31Z.\n  time basis: source_export_reqlog.\n  source sha256: 60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793.\n  Retained record 6c450178\n\n- Primary source\n  Body-verified tynwd destination carries the exact county/CIP/year aggregate query but no five-county selection. Public stats previously reported no traffic.\n  time raw: 2026-06-21 03:50:05.\n  time basis: raw_unzoned.\n  source sha256: cb5a906455bc952d39702243a9bf3fa450933a1c51c6d60ee625a17b64e5bd53.\n  Retained record 21670210\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://api.datausa.io/tesseract/data.jsonrecords?cube=ipeds_completions&drilldowns=County,Year&include=CIP4:1107;Year:2013&measures=Completions", "deliverables": ["Provide exact public source locators plus retained content or archive evidence and its acquisition date.", "State what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.", "Do not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.", "Recover all five complete county IDs in the observed order plus the year, CIP4 code and measure.", "Distinguish the all-counties aggregate query from the five separately constrained county queries.", "Compare exact body hashes and retained revision introductions to distinguish a new independent source from copying."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Provide exact public source locators plus retained content or archive evidence and its acquisition date.\nState what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.\nDo not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.\nRecover all five complete county IDs in the observed order plus the year, CIP4 code and measure.\nDistinguish the all-counties aggregate query from the five separately constrained county queries.\nCompare exact body hashes and retained revision introductions to distinguish a new independent source from copying."}], "research_notes": [], "issue_text": "## Question\n\nFind an independent retained artifact with the ordered counties 05000US06023 → 05000US08069 → 05000US12011 → 05000US38017 → 05000US30031, ipeds_completions, CIP4:1107, Year:2013 and Completions. Determine whether the order comes from a task prompt, a copied query block or another reproducible source.\n\n## Existing evidence\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~AgentDataQRefsZ1223.html#rev-2)\n  AgentDataQRefsZ1223@2 carries the full five-county ordered query block.\n  time raw: `2026-06-21T08:25:13Z`.\n  time utc: `2026-06-21T08:25:13Z`.\n  time basis: `source_export_reqlog`.\n  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.\n  [Retained record 8685b644](https://swarmstatus.com/api/record?id=8685b644c7675ab443b8494d41552962)\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~TmpTestHelloxx123.html#rev-3)\n  TmpTestHelloxx123@3 carries the same ordered block.\n  time raw: `2026-06-21T08:19:31Z`.\n  time utc: `2026-06-21T08:19:31Z`.\n  time basis: `source_export_reqlog`.\n  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.\n  [Retained record 6c450178](https://swarmstatus.com/api/record?id=6c4501782684466f5b218adfccc866eb)\n\n- [Primary source](https://vanderbi.lt/tynwd+)\n  Body-verified tynwd destination carries the exact county/CIP/year aggregate query but no five-county selection. Public stats previously reported no traffic.\n  time raw: `2026-06-21 03:50:05`.\n  time basis: `raw_unzoned`.\n  source sha256: `cb5a906455bc952d39702243a9bf3fa450933a1c51c6d60ee625a17b64e5bd53`.\n  [Retained record 21670210](https://swarmstatus.com/api/record?id=21670210d450e542bf5d58e3284d0225)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://api.datausa.io/tesseract/data.jsonrecords?cube=ipeds_completions&drilldowns=County,Year&include=CIP4:1107;Year:2013&measures=Completions\n```\n\n## Acceptance criteria\n\n- [ ] Provide exact public source locators plus retained content or archive evidence and its acquisition date.\n- [ ] State what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.\n- [ ] Do not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.\n- [ ] Recover all five complete county IDs in the observed order plus the year, CIP4 code and measure.\n- [ ] Distinguish the all-counties aggregate query from the five separately constrained county queries.\n- [ ] Compare exact body hashes and retained revision introductions to distinguish a new independent source from copying.\n\n## Caveats and alternatives\n\n- A plain search for 1107 can match unrelated subject matter; the full conjunction is required.\n- Two copies of an ordered block do not establish two independent origins.\n- No-traffic shortener metadata and a stored destination do not demonstrate source retrieval.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:coverage-ipeds-ordered-counties -->\n", "limits": "- A plain search for 1107 can match unrelated subject matter; the full conjunction is required.\n- Two copies of an ordered block do not establish two independent origins.\n- No-traffic shortener metadata and a stored destination do not demonstrate source retrieval.", "sources": [{"label": "Retained record 8685b644", "url": "https://swarmstatus.com/api/record?id=8685b644c7675ab443b8494d41552962"}, {"label": "Retained record 6c450178", "url": "https://swarmstatus.com/api/record?id=6c4501782684466f5b218adfccc866eb"}, {"label": "Retained record 21670210", "url": "https://swarmstatus.com/api/record?id=21670210d450e542bf5d58e3284d0225"}], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/21", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/21", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/21#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-07T14:10:24Z", "areas": ["IPEDS"]}, {"id": "bounty-20", "number": 20, "teaser": null, "title": "Find an independent publication of the complete rural-poverty query bundle", "status": "open", "question": "Find another independently retained task artifact carrying worldPovertyRegion for both 2018 and 2020, dailySpending=2.15, the country set AFG/GHA/NGA/IND/MEX and ruralValue/headcount. Compare wrapper and selection-set differences without counting the three identical wiki bodies as independent task origins.", "source_context": "- Primary source\n  AgentNextRawJuneAE@6 retains separate 2018 and 2020 proxymule-wrapped queries.\n  time raw: 2026-06-21T20:23:07Z.\n  time utc: 2026-06-21T20:23:07Z.\n  time basis: source_export_reqlog.\n  source sha256: 60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793.\n  Retained record b445685a\n\n- Primary source\n  AgentPovertyDataNEWX@1 has the same complete body.\n  time raw: 2026-06-21T20:20:21Z.\n  time utc: 2026-06-21T20:20:21Z.\n  time basis: source_export_reqlog.\n  source sha256: 60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793.\n  Retained record 2fa0eb8c\n\n- Primary source\n  AgentPovertyDataZ@2 has the same complete body.\n  time raw: 2026-06-21T20:19:35Z.\n  time utc: 2026-06-21T20:19:35Z.\n  time basis: source_export_reqlog.\n  source sha256: 60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793.\n  Retained record 2e97ed9e\n\n- Primary source\n  Body-verified direct shortener destination combines both years in one GraphQL query; uses country{id name} selection. This record ID was checked directly, not taken from the defective fingerprint join.\n  time raw: 2026-06-21 15:08:33.\n  time basis: raw_unzoned.\n  source sha256: cb5a906455bc952d39702243a9bf3fa450933a1c51c6d60ee625a17b64e5bd53.\n  Retained record d1e92221\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://api.worldpoverty.io/graphql?query=%7B%20y2018%3A%20worldPovertyRegion%28year%3A%202018%2C%20dailySpending%3A%202.15%2C%20countryIds%3A%20%5B%22AFG%22%2C%20%22GHA%22%2C%20%22NGA%22%2C%20%22IND%22%2C%20%22MEX%22%5D%29%20%7B%20countryValues%20%7B%20country%20%7B%20id%20name%20%7D%20value%20%7B%20ruralValue%20%7B%20headcount%20%7D%20%7D%20%7D%20%7D%20y2020%3A%20worldPovertyRegion%28year%3A%202020%2C%20dailySpending%3A%202.15%2C%20countryIds%3A%20%5B%22AFG%22%2C%20%22GHA%22%2C%20%22NGA%22%2C%20%22IND%22%2C%20%22MEX%22%5D%29%20%7B%20countryValues%20%7B%20country%20%7B%20id%20name%20%7D%20value%20%7B%20ruralValue%20%7B%20headcount%20%7D%20%7D%20%7D%20%7D%20%7D", "deliverables": ["Provide exact public source locators plus retained content or archive evidence and its acquisition date.", "State what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.", "Do not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.", "Match both years, threshold, all five country codes and rural headcount path. A domain-only match does not qualify.", "Preserve ordered country appearance as an additional signature while distinguishing order from set equality.", "Account for countryId versus country{id name} selection differences, separate versus aliased year requests, and exact-copy body hashes.", "An original public API documentation page without staging/task context is not a newly found task publication."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Provide exact public source locators plus retained content or archive evidence and its acquisition date.\nState what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.\nDo not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.\nMatch both years, threshold, all five country codes and rural headcount path. A domain-only match does not qualify.\nPreserve ordered country appearance as an additional signature while distinguishing order from set equality.\nAccount for countryId versus country{id name} selection differences, separate versus aliased year requests, and exact-copy body hashes.\nAn original public API documentation page without staging/task context is not a newly found task publication."}], "research_notes": [], "issue_text": "## Question\n\nFind another independently retained task artifact carrying worldPovertyRegion for both 2018 and 2020, dailySpending=2.15, the country set AFG/GHA/NGA/IND/MEX and ruralValue/headcount. Compare wrapper and selection-set differences without counting the three identical wiki bodies as independent task origins.\n\n## Existing evidence\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~AgentNextRawJuneAE.html#rev-6)\n  AgentNextRawJuneAE@6 retains separate 2018 and 2020 proxymule-wrapped queries.\n  time raw: `2026-06-21T20:23:07Z`.\n  time utc: `2026-06-21T20:23:07Z`.\n  time basis: `source_export_reqlog`.\n  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.\n  [Retained record b445685a](https://swarmstatus.com/api/record?id=b445685ad7b205a054e767d2259e9806)\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~AgentPovertyDataNEWX.html#rev-1)\n  AgentPovertyDataNEWX@1 has the same complete body.\n  time raw: `2026-06-21T20:20:21Z`.\n  time utc: `2026-06-21T20:20:21Z`.\n  time basis: `source_export_reqlog`.\n  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.\n  [Retained record 2fa0eb8c](https://swarmstatus.com/api/record?id=2fa0eb8cb68e5f8bfaea46b981977da0)\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~AgentPovertyDataZ.html#rev-2)\n  AgentPovertyDataZ@2 has the same complete body.\n  time raw: `2026-06-21T20:19:35Z`.\n  time utc: `2026-06-21T20:19:35Z`.\n  time basis: `source_export_reqlog`.\n  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.\n  [Retained record 2e97ed9e](https://swarmstatus.com/api/record?id=2e97ed9e106a5447834d1d2c0dd01e13)\n\n- [Primary source](https://vanderbi.lt/mypovdirect11782072512+)\n  Body-verified direct shortener destination combines both years in one GraphQL query; uses country{id name} selection. This record ID was checked directly, not taken from the defective fingerprint join.\n  time raw: `2026-06-21 15:08:33`.\n  time basis: `raw_unzoned`.\n  source sha256: `cb5a906455bc952d39702243a9bf3fa450933a1c51c6d60ee625a17b64e5bd53`.\n  [Retained record d1e92221](https://swarmstatus.com/api/record?id=d1e92221f5cfa75b4f9f1230dd1df2bf)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://api.worldpoverty.io/graphql?query=%7B%20y2018%3A%20worldPovertyRegion%28year%3A%202018%2C%20dailySpending%3A%202.15%2C%20countryIds%3A%20%5B%22AFG%22%2C%20%22GHA%22%2C%20%22NGA%22%2C%20%22IND%22%2C%20%22MEX%22%5D%29%20%7B%20countryValues%20%7B%20country%20%7B%20id%20name%20%7D%20value%20%7B%20ruralValue%20%7B%20headcount%20%7D%20%7D%20%7D%20%7D%20y2020%3A%20worldPovertyRegion%28year%3A%202020%2C%20dailySpending%3A%202.15%2C%20countryIds%3A%20%5B%22AFG%22%2C%20%22GHA%22%2C%20%22NGA%22%2C%20%22IND%22%2C%20%22MEX%22%5D%29%20%7B%20countryValues%20%7B%20country%20%7B%20id%20name%20%7D%20value%20%7B%20ruralValue%20%7B%20headcount%20%7D%20%7D%20%7D%20%7D%20%7D\n```\n\n## Acceptance criteria\n\n- [ ] Provide exact public source locators plus retained content or archive evidence and its acquisition date.\n- [ ] State what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.\n- [ ] Do not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.\n- [ ] Match both years, threshold, all five country codes and rural headcount path. A domain-only match does not qualify.\n- [ ] Preserve ordered country appearance as an additional signature while distinguishing order from set equality.\n- [ ] Account for countryId versus country{id name} selection differences, separate versus aliased year requests, and exact-copy body hashes.\n- [ ] An original public API documentation page without staging/task context is not a newly found task publication.\n\n## Caveats and alternatives\n\n- The three cited wiki bodies share one exact hash, so they provide multiple observations of copied content.\n- GraphQL URL publication is not evidence of a valid schema response or successful extraction.\n- Shortener raw clocks remain unzoned.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:coverage-worldpoverty-bundle -->\n", "limits": "- The three cited wiki bodies share one exact hash, so they provide multiple observations of copied content.\n- GraphQL URL publication is not evidence of a valid schema response or successful extraction.\n- Shortener raw clocks remain unzoned.", "sources": [{"label": "Retained record b445685a", "url": "https://swarmstatus.com/api/record?id=b445685ad7b205a054e767d2259e9806"}, {"label": "Retained record 2fa0eb8c", "url": "https://swarmstatus.com/api/record?id=2fa0eb8cb68e5f8bfaea46b981977da0"}, {"label": "Retained record 2e97ed9e", "url": "https://swarmstatus.com/api/record?id=2e97ed9e106a5447834d1d2c0dd01e13"}], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/20", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/20", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/20#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-07T14:10:31Z", "areas": ["WorldPoverty"]}, {"id": "bounty-19", "number": 19, "teaser": null, "title": "Independently date the newly found Demo, Gründer and dictionary wiki bodies", "status": "open", "question": "Recover an independent historical body capture or native revision history for the task-bearing Demo, Gründer or Semantic Dictionary pages. Determine which task text demonstrably existed before the September discovery, and which is known only from the current page plus a displayed recent-changes date.", "source_context": "- Primary source\n  Current Demo body for AgentResearchDataUsaLink1781634491; its capture is not an event date.\n  time basis: current_capture_no_event_time.\n  source sha256: db7b881915a7fefaf0fe7ca134b233e0a8bfa010bbe890fee7f2a2596c2bc9c5.\n  Retained record 1b5c4d8c\n\n- Primary source\n  Demo RC row is independently present in the retained July 10 Common Crawl WARC, but the WARC is a changes listing, not this full task body.\n  time raw: 16. Juni 2026 20:28.\n  time basis: clock_conflict_site_wall_time.\n  source sha256: 18106786afcd7aabb6c6ee5222c0e7689ca5508b5990090e07649c621b638632.\n  Retained record 0b48cac7\n\n- Primary source\n  Current Gründer DataUsaBridgePlaceResearch body.\n  time basis: current_capture_no_event_time.\n  source sha256: 30ae22bcbd415979fb88e70ed1eda97e2a8a837106694b3993a6c8d931614177.\n  Retained record 0de0f51b\n\n- Primary source\n  Gründer RC row displays 22. Juni 2026 10:41; site wall-clock conversion remains unresolved.\n  time raw: 22. Juni 2026 10:41.\n  time basis: clock_conflict_site_wall_time.\n  source sha256: 18106786afcd7aabb6c6ee5222c0e7689ca5508b5990090e07649c621b638632.\n  Retained record 52c2844f\n\n- Primary source\n  Current Semantic Dictionary FederalDataReferenceXYZ body.\n  time basis: current_capture_no_event_time.\n  source sha256: de99f33a5d6528a037c60faa47bbef584dcd0ae2aa85295a9b091e1f6e0b7e5c.\n  Retained record 2700266f\n\n- Primary source\n  Its RC listing displays May 24, 2026 13:01; independent body-date anchor is missing.\n  time raw: May 24, 2026 13:01.\n  time basis: clock_conflict_site_wall_time.\n  source sha256: 18106786afcd7aabb6c6ee5222c0e7689ca5508b5990090e07649c621b638632.\n  Retained record b1b28bce", "deliverables": ["Provide exact public source locators plus retained content or archive evidence and its acquisition date.", "State what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.", "Do not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.", "Produce an archived body or native revision that contains the exact relevant task URL/query, not only a page title or index listing.", "Preserve archive capture time separately from displayed modification/write time and any source timezone assertion.", "For Demo, verify WARC target URI and byte-range/digest provenance before claiming what the July capture contains."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Provide exact public source locators plus retained content or archive evidence and its acquisition date.\nState what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.\nDo not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.\nProduce an archived body or native revision that contains the exact relevant task URL/query, not only a page title or index listing.\nPreserve archive capture time separately from displayed modification/write time and any source timezone assertion.\nFor Demo, verify WARC target URI and byte-range/digest provenance before claiming what the July capture contains."}], "research_notes": [], "issue_text": "## Question\n\nRecover an independent historical body capture or native revision history for the task-bearing Demo, Gründer or Semantic Dictionary pages. Determine which task text demonstrably existed before the September discovery, and which is known only from the current page plus a displayed recent-changes date.\n\n## Existing evidence\n\n- [Primary source](https://www.wikiservice.at/demo/wiki.cgi?action=browse&id=AgentResearchDataUsaLink1781634491&days=180)\n  Current Demo body for AgentResearchDataUsaLink1781634491; its capture is not an event date.\n  time basis: `current_capture_no_event_time`.\n  source sha256: `db7b881915a7fefaf0fe7ca134b233e0a8bfa010bbe890fee7f2a2596c2bc9c5`.\n  [Retained record 1b5c4d8c](https://swarmstatus.com/api/record?id=1b5c4d8cc1212586970bf5387149085a)\n\n- [Primary source](https://www.wikiservice.at/demo/wiki.cgi?action=rc&all=1&days=180)\n  Demo RC row is independently present in the retained July 10 Common Crawl WARC, but the WARC is a changes listing, not this full task body.\n  time raw: `16. Juni 2026 20:28`.\n  time basis: `clock_conflict_site_wall_time`.\n  source sha256: `18106786afcd7aabb6c6ee5222c0e7689ca5508b5990090e07649c621b638632`.\n  [Retained record 0b48cac7](https://swarmstatus.com/api/record?id=0b48cac75274dca1c0a71c34076c9274)\n\n- [Primary source](https://www.wikiservice.at/gruender/wiki.cgi?action=browse&id=DataUsaBridgePlaceResearch)\n  Current Gründer DataUsaBridgePlaceResearch body.\n  time basis: `current_capture_no_event_time`.\n  source sha256: `30ae22bcbd415979fb88e70ed1eda97e2a8a837106694b3993a6c8d931614177`.\n  [Retained record 0de0f51b](https://swarmstatus.com/api/record?id=0de0f51b0eff3d112d8417d17de2594a)\n\n- [Primary source](https://www.wikiservice.at/gruender/wiki.cgi?action=rc&all=1&days=180)\n  Gründer RC row displays 22. Juni 2026 10:41; site wall-clock conversion remains unresolved.\n  time raw: `22. Juni 2026 10:41`.\n  time basis: `clock_conflict_site_wall_time`.\n  source sha256: `18106786afcd7aabb6c6ee5222c0e7689ca5508b5990090e07649c621b638632`.\n  [Retained record 52c2844f](https://swarmstatus.com/api/record?id=52c2844fad0125df5c93976059802357)\n\n- [Primary source](https://www.wikiservice.at/dict/sm/wiki.cgi?action=browse&id=FederalDataReferenceXYZ&days=180)\n  Current Semantic Dictionary FederalDataReferenceXYZ body.\n  time basis: `current_capture_no_event_time`.\n  source sha256: `de99f33a5d6528a037c60faa47bbef584dcd0ae2aa85295a9b091e1f6e0b7e5c`.\n  [Retained record 2700266f](https://swarmstatus.com/api/record?id=2700266f82eaa13274208ed70a0d3491)\n\n- [Primary source](https://www.wikiservice.at/dict/sm/wiki.cgi?action=rc&all=1&days=180)\n  Its RC listing displays May 24, 2026 13:01; independent body-date anchor is missing.\n  time raw: `May 24, 2026 13:01`.\n  time basis: `clock_conflict_site_wall_time`.\n  source sha256: `18106786afcd7aabb6c6ee5222c0e7689ca5508b5990090e07649c621b638632`.\n  [Retained record b1b28bce](https://swarmstatus.com/api/record?id=b1b28bce924a56cf94b7d36c50f23a00)\n\n## Acceptance criteria\n\n- [ ] Provide exact public source locators plus retained content or archive evidence and its acquisition date.\n- [ ] State what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.\n- [ ] Do not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.\n- [ ] Produce an archived body or native revision that contains the exact relevant task URL/query, not only a page title or index listing.\n- [ ] Preserve archive capture time separately from displayed modification/write time and any source timezone assertion.\n- [ ] For Demo, verify WARC target URI and byte-range/digest provenance before claiming what the July capture contains.\n\n## Caveats and alternatives\n\n- Current captures retain useful content but do not establish when it was written.\n- Displayed June/May recent-changes clocks are unresolved; the existing Demo archive already independently dates the listing to July 10, so rediscovering that same listing is not new body evidence.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:coverage-legacy-dates -->\n", "limits": "- Current captures retain useful content but do not establish when it was written.\n- Displayed June/May recent-changes clocks are unresolved; the existing Demo archive already independently dates the listing to July 10, so rediscovering that same listing is not new body evidence.", "sources": [{"label": "Retained record 1b5c4d8c", "url": "https://swarmstatus.com/api/record?id=1b5c4d8cc1212586970bf5387149085a"}, {"label": "Retained record 0b48cac7", "url": "https://swarmstatus.com/api/record?id=0b48cac75274dca1c0a71c34076c9274"}, {"label": "Retained record 0de0f51b", "url": "https://swarmstatus.com/api/record?id=0de0f51b0eff3d112d8417d17de2594a"}], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/19", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/19", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/19#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-07T14:10:46Z", "areas": ["legacy-wikis"]}, {"id": "bounty-18", "number": 18, "teaser": null, "title": "Verify an Iowa named-recipient exchange with retained reply evidence", "status": "open", "question": "Can any exact Iowa paste request and its claimed answer be joined through a retained parent/reply relation, explicit source link, or independent read/acknowledgement evidence? Start with the agent-0227 cache request/replies and Q5 wording, rather than treating adjacent static pastes as a conversation.", "source_context": "- Primary source\n  IowaReply0227 addresses agent-0227, cites cache eb7e28bd and claims the Q5 wording is confirmed.\n  time raw: 2 Months ago..\n  time basis: relative_age.\n  source sha256: 570051f593cd4ebd1e572cd77e44fb46634bccd48d19ceb5722050cf276230cb.\n  Retained record 25194b72\n\n- Primary source\n  IowaCacheReply addresses the same displayed recipient and cites the full cache, but no provider stored-reply relation is retained.\n  time raw: 2 Months ago..\n  time basis: relative_age.\n  source sha256: 33c42767e95a708a78c3c02380d8e1142fdc86d236d824292e91d9d78ab8d81b.\n  Retained record bffc285e\n\n- Primary source\n  A separately addressed thanks/post-Q5 request is a candidate acknowledgement, not proof of who read which earlier paste.\n  time raw: 2 Months ago..\n  time basis: relative_age.\n  source sha256: 06215ba7ebf9a6ef4020a38e0d41288dd8acba35e9a4f8c0d7ad8950cf65a50d.\n  Retained record 073fb1a9", "deliverables": ["Provide exact public source locators plus retained content or archive evidence and its acquisition date.", "State what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.", "Do not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.", "Supply the actual request and answer objects with exact IDs, distinguish content citation from a provider-declared stored reply, and identify any ambiguity.", "A displayed address can support a named-recipient edge. A stored-reply edge requires a retained linkage field or equivalent direct evidence.", "To claim successful delivery, supply an explicit acknowledgement tied to the specific requested content or independent access/receipt evidence."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Provide exact public source locators plus retained content or archive evidence and its acquisition date.\nState what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.\nDo not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.\nSupply the actual request and answer objects with exact IDs, distinguish content citation from a provider-declared stored reply, and identify any ambiguity.\nA displayed address can support a named-recipient edge. A stored-reply edge requires a retained linkage field or equivalent direct evidence.\nTo claim successful delivery, supply an explicit acknowledgement tied to the specific requested content or independent access/receipt evidence."}], "research_notes": [{"heading": "Research update — September 5, 2026", "text": "Reviewed partial evidence, PR #51 preserves four original API envelopes and separates two different findings: the native parent of 7a45b400 is greeting-only e53f96e2; a separate 8246f250 acknowledgment repeats “85 and older” and thanks the report's displayed label 57 provider-created seconds after d509c771. The native parent delta is 4,323 seconds. All four readable bodies already exist in the canonical corpus.\n\nThe content acknowledgment contains no exact report URL or native reply/read receipt identifying that report object. Exact request–answer linkage and successful delivery remain unresolved. Provider-created assertions and September acquisition clocks remain separate. The package passes independent review, a 42-check canonical cross-check and six negative controls. This question remains open."}], "issue_text": "## Question\n\nCan any exact Iowa paste request and its claimed answer be joined through a retained parent/reply relation, explicit source link, or independent read/acknowledgement evidence? Start with the agent-0227 cache request/replies and Q5 wording, rather than treating adjacent static pastes as a conversation.\n\n## Existing evidence\n\n- [Primary source](https://paste.linuxiarz.pl/view/11d30c3f)\n  IowaReply0227 addresses agent-0227, cites cache eb7e28bd and claims the Q5 wording is confirmed.\n  time raw: `2 Months ago.`.\n  time basis: `relative_age`.\n  source sha256: `570051f593cd4ebd1e572cd77e44fb46634bccd48d19ceb5722050cf276230cb`.\n  [Retained record 25194b72](https://swarmstatus.com/api/record?id=25194b724b3fc7ea94dc26bbf0fb0bba)\n\n- [Primary source](https://paste.linuxiarz.pl/view/1ad7edc4)\n  IowaCacheReply addresses the same displayed recipient and cites the full cache, but no provider stored-reply relation is retained.\n  time raw: `2 Months ago.`.\n  time basis: `relative_age`.\n  source sha256: `33c42767e95a708a78c3c02380d8e1142fdc86d236d824292e91d9d78ab8d81b`.\n  [Retained record bffc285e](https://swarmstatus.com/api/record?id=bffc285e8e4b206ae385c314525320c9)\n\n- [Primary source](https://paste.linuxiarz.pl/view/28c3155e)\n  A separately addressed thanks/post-Q5 request is a candidate acknowledgement, not proof of who read which earlier paste.\n  time raw: `2 Months ago.`.\n  time basis: `relative_age`.\n  source sha256: `06215ba7ebf9a6ef4020a38e0d41288dd8acba35e9a4f8c0d7ad8950cf65a50d`.\n  [Retained record 073fb1a9](https://swarmstatus.com/api/record?id=073fb1a96a78266423aae586018aae7e)\n\n## Acceptance criteria\n\n- [ ] Provide exact public source locators plus retained content or archive evidence and its acquisition date.\n- [ ] State what is new relative to the listed evidence, preserve source clock bases, and separate independent observations from copies.\n- [ ] Do not infer real operators, model identity or message delivery from displayed handles, creator labels, referrers or generic similarity.\n- [ ] Supply the actual request and answer objects with exact IDs, distinguish content citation from a provider-declared stored reply, and identify any ambiguity.\n- [ ] A displayed address can support a named-recipient edge. A stored-reply edge requires a retained linkage field or equivalent direct evidence.\n- [ ] To claim successful delivery, supply an explicit acknowledgement tied to the specific requested content or independent access/receipt evidence.\n\n## Caveats and alternatives\n\n- 120 Iowa metadata objects have retained bodies; 23 of all 698 paste bodies have conservative explicit address markers. Static bodies alone do not establish alternating revision history.\n- Relative ages such as 2 Months ago and embedded ts values are separate clock types; neither is a verified provider write timestamp.\n- A common title such as IowaCollabReply is not an object-level reply link.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:coverage-iowa-delivery -->\n\n\n## Research update — September 5, 2026\n\n[Reviewed partial evidence, PR #51](https://github.com/aadarwal/swarmstatus-bounties/pull/51) preserves four original API envelopes and separates two different findings: the native parent of 7a45b400 is greeting-only e53f96e2; a separate 8246f250 acknowledgment repeats “85 and older” and thanks the report's displayed label 57 provider-created seconds after d509c771. The native parent delta is 4,323 seconds. All four readable bodies already exist in the canonical corpus.\n\nThe content acknowledgment contains no exact report URL or native reply/read receipt identifying that report object. Exact request–answer linkage and successful delivery remain unresolved. Provider-created assertions and September acquisition clocks remain separate. The package passes independent review, a 42-check canonical cross-check and six negative controls. This question remains open.\n\n<!-- swarmstatus:iowa18-partial-pr51 -->\n", "limits": "- 120 Iowa metadata objects have retained bodies; 23 of all 698 paste bodies have conservative explicit address markers. Static bodies alone do not establish alternating revision history.\n- Relative ages such as 2 Months ago and embedded ts values are separate clock types; neither is a verified provider write timestamp.\n- A common title such as IowaCollabReply is not an object-level reply link.", "sources": [{"label": "Retained record 25194b72", "url": "https://swarmstatus.com/api/record?id=25194b724b3fc7ea94dc26bbf0fb0bba"}, {"label": "Retained record bffc285e", "url": "https://swarmstatus.com/api/record?id=bffc285e8e4b206ae385c314525320c9"}, {"label": "Retained record 073fb1a9", "url": "https://swarmstatus.com/api/record?id=073fb1a96a78266423aae586018aae7e"}], "evidence_prs": ["https://github.com/aadarwal/swarmstatus-bounties/pull/51"], "url": "https://swarmstatus.com/contribute/18", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/18", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/18#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-07T14:10:50Z", "areas": ["Iowa"]}, {"id": "bounty-16", "number": 16, "teaser": null, "title": "Recover the DataUSA completion rows and reconcile the two query limits", "status": "in-review", "question": "Recover the DataUSA ipeds_completions rows for University 153658 and 215062, each Gender 1 and 2, drilldowns Year,CIP6, measures Completions, top=5.Year.Completions.desc. Explain how these receipt queries relate to retained variants using Year=2016,2017,2018 and top=3.Year.Completions.desc.", "source_context": "- Primary source\n  University 153658, Gender 1: 00:35:47Z, 200 JSON-view metadata, 7,399 bytes.\n  time raw: 2026-05-28T00:35:47Z.\n  time basis: URLQuery report date, not source publication or actor identity.\n  Acquisition record ID: c48f36885e8aafa875814dd27550b006 (outside the focused explorer; use the primary locator above).\n  Provider report JSON\n\n- Primary source\n  University 153658, Gender 2: 00:35:51Z, 200, 7,078 bytes.\n  time raw: 2026-05-28T00:35:51Z.\n  time basis: URLQuery report date, not source publication or actor identity.\n  Acquisition record ID: d7c5059620fb8c8fd43b1e8f9e670023 (outside the focused explorer; use the primary locator above).\n  Provider report JSON\n\n- Primary source\n  University 215062, Gender 2: 00:36:02Z, 200, 7,162 bytes.\n  time raw: 2026-05-28T00:36:02Z.\n  time basis: URLQuery report date, not source publication or actor identity.\n  Acquisition record ID: d45867666a1a1b000d92c3b157dd5fb6 (outside the focused explorer; use the primary locator above).\n  Provider report JSON\n\n- Primary source\n  University 215062, Gender 1: 00:36:05Z, 200, 7,263 bytes.\n  time raw: 2026-05-28T00:36:05Z.\n  time basis: URLQuery report date, not source publication or actor identity.\n  Acquisition record ID: fff2a044abeaf9371068a949799765a6 (outside the focused explorer; use the primary locator above).\n  Provider report JSON\n\n- Primary source\n  time utc: 2026-05-28T00:42:44Z.\n  source sha256: 60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793.\n  native rev id: dse~AgentDataUsaSourceLinkQ1@1.\n  Retained record 12f0c6b3", "deliverables": ["Supply a retained artifact or archive capture with a stable URL, acquisition date, source date when available, and a content hash.", "Preserve the full resource identifier and relevant filters; explain differences from the evidence listed here.", "Separate submitted URL, observed request, response metadata, readable response body, and verified answer; do not infer an actor from submitter or referrer metadata.", "Preserve university, gender, all years/limits, drilldowns and measures. Top five over all available years is not automatically top three for 2016–2018.", "Identify a readable saved response and compare rows to retained claims.", "Treat language locale as a presentation difference explicitly; do not silently drop analytical parameters."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Supply a retained artifact or archive capture with a stable URL, acquisition date, source date when available, and a content hash.\nPreserve the full resource identifier and relevant filters; explain differences from the evidence listed here.\nSeparate submitted URL, observed request, response metadata, readable response body, and verified answer; do not infer an actor from submitter or referrer metadata.\nPreserve university, gender, all years/limits, drilldowns and measures. Top five over all available years is not automatically top three for 2016–2018.\nIdentify a readable saved response and compare rows to retained claims.\nTreat language locale as a presentation difference explicitly; do not silently drop analytical parameters."}], "research_notes": [{"heading": "Research update — 2026-09-05", "text": "Independent re-parsing of the four already-retained provider JSONs adds a metadata constraint for evaluating future candidate responses. In every /http/0/response/raw header block, lines 8–10 (counting the status line as line 1) retain:\n\ntext\nx-tesseract-columns: CIP6 ID,CIP6,Year,Completions,Top Completions\nx-tesseract-queryrows: 60\nx-tesseract-totalrows: 60\n\n\nThese are reported header values, not 60 recovered rows. The four requests are the university/gender top-five queries already listed above. This does not establish a 12-year span, ranking or tie behavior, or results for the later top-three variants.\n\nThe original JSONs also separate the HTTP-event clock (/http/0/date) from the report clock (/date). All dates below are May 28, 2026 UTC; the report dates in the existing evidence were already correctly labeled.\n\n| University / Gender | Retained report JSON | HTTP event | Report | SHA256 of retained, uncompressed provider JSON |\n|---|---|---|---|---|\n| 153658 / 1 | b658f273 | 00:35:26.339 | 00:35:47 | 4aad92b58f03715d433029ee2b1ccbb441eb0f114d3710490887c2d7ba3351f2 |\n| 153658 / 2 | dd6c4784 | 00:35:30.424 | 00:35:51 | 9255cbc45222f46a0e62b21cd7eb7cbd233511220cf8563b4682ac6bded2d94c |\n| 215062 / 2 | 65144082 | 00:35:40.750 | 00:36:02 | 82e62ae8f9d4e34004c981b8b00f8ccf8ecbd8d184ac1d10023df2ad753ea666 |\n| 215062 / 1 | fabdcd45 | 00:35:44.570 | 00:36:05 | 0908f5dda535a478261609e93f51bda46676927dfdfc94f2ad3da49c08349337 |\n\nThe four provider JSONs total 30,960 uncompressed bytes. These hashes identify the retained reports, not the absent DataUSA response bodies. The separate response Date headers have second precision. Local retention-manifest attempted_at_utc values on September 5 mark acquisition-workflow start, assigned before cache checking/request waiting; they are not exact HTTP-send, completion, publication, or historical event clocks.\n\nStill unresolved: all four /http/0/response/data/data fields are null, with size_decoded: 0 and SHA256(empty), despite reported nonzero response sizes. This establishes missing readable bytes in these retained reports, not an empty origin response. No completion values or top-five/top-three row comparison were recovered. This is a clarification of existing evidence; all acceptance criteria and the open question remain unchanged."}], "issue_text": "## Question\n\nRecover the DataUSA ipeds_completions rows for University 153658 and 215062, each Gender 1 and 2, drilldowns Year,CIP6, measures Completions, top=5.Year.Completions.desc. Explain how these receipt queries relate to retained variants using Year=2016,2017,2018 and top=3.Year.Completions.desc.\n\n## Existing evidence\n\n- [Primary source](https://urlquery.net/report/b658f273-fd60-4191-b496-d244d47d5531)\n  University 153658, Gender 1: 00:35:47Z, 200 JSON-view metadata, 7,399 bytes.\n  time raw: `2026-05-28T00:35:47Z`.\n  time basis: `URLQuery report date, not source publication or actor identity`.\n  Acquisition record ID: `c48f36885e8aafa875814dd27550b006` (outside the focused explorer; use the primary locator above).\n  [Provider report JSON](https://urlquery.net/report/b658f273-fd60-4191-b496-d244d47d5531/json)\n\n- [Primary source](https://urlquery.net/report/dd6c4784-2a86-49d8-8418-431ed781f0b7)\n  University 153658, Gender 2: 00:35:51Z, 200, 7,078 bytes.\n  time raw: `2026-05-28T00:35:51Z`.\n  time basis: `URLQuery report date, not source publication or actor identity`.\n  Acquisition record ID: `d7c5059620fb8c8fd43b1e8f9e670023` (outside the focused explorer; use the primary locator above).\n  [Provider report JSON](https://urlquery.net/report/dd6c4784-2a86-49d8-8418-431ed781f0b7/json)\n\n- [Primary source](https://urlquery.net/report/65144082-bcc5-4e7d-96b9-556f35d63872)\n  University 215062, Gender 2: 00:36:02Z, 200, 7,162 bytes.\n  time raw: `2026-05-28T00:36:02Z`.\n  time basis: `URLQuery report date, not source publication or actor identity`.\n  Acquisition record ID: `d45867666a1a1b000d92c3b157dd5fb6` (outside the focused explorer; use the primary locator above).\n  [Provider report JSON](https://urlquery.net/report/65144082-bcc5-4e7d-96b9-556f35d63872/json)\n\n- [Primary source](https://urlquery.net/report/fabdcd45-6f13-49c8-8823-8650a9905622)\n  University 215062, Gender 1: 00:36:05Z, 200, 7,263 bytes.\n  time raw: `2026-05-28T00:36:05Z`.\n  time basis: `URLQuery report date, not source publication or actor identity`.\n  Acquisition record ID: `fff2a044abeaf9371068a949799765a6` (outside the focused explorer; use the primary locator above).\n  [Provider report JSON](https://urlquery.net/report/fabdcd45-6f13-49c8-8823-8650a9905622/json)\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~AgentDataUsaSourceLinkQ1.html#rev-1)\n  time utc: `2026-05-28T00:42:44Z`.\n  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.\n  native rev id: `dse~AgentDataUsaSourceLinkQ1@1`.\n  [Retained record 12f0c6b3](https://swarmstatus.com/api/record?id=12f0c6b36b43723d203afa3ee2dd1c4e)\n\n## Acceptance criteria\n\n- [ ] Supply a retained artifact or archive capture with a stable URL, acquisition date, source date when available, and a content hash.\n- [ ] Preserve the full resource identifier and relevant filters; explain differences from the evidence listed here.\n- [ ] Separate submitted URL, observed request, response metadata, readable response body, and verified answer; do not infer an actor from submitter or referrer metadata.\n- [ ] Preserve university, gender, all years/limits, drilldowns and measures. Top five over all available years is not automatically top three for 2016–2018.\n- [ ] Identify a readable saved response and compare rows to retained claims.\n- [ ] Treat language locale as a presentation difference explicitly; do not silently drop analytical parameters.\n\n## Caveats and alternatives\n\n- 18 receipts match all analytical query parameters; only locale is omitted from that signature. Scheme and fragment are outside analytical parameter identity.\n- Some provider response metadata reports nonzero bytes with the empty-content SHA256, so it cannot prove the origin response bytes.\n- The four initial reports precede their first matching original wiki rows by roughly 7–8 minutes. That is observation order, not actor identity or proof that the report caused the wiki publication.\n\n## Prior work\n\nExpands the single V5 representative into four exact university/gender query combinations and retained chronology; response bodies remain missing.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:uqr-datausa-filtered-rows -->\n\n## Research update — 2026-09-05\n\nIndependent re-parsing of the four already-retained provider JSONs adds a metadata constraint for evaluating future candidate responses. In every `/http/0/response/raw` header block, lines 8–10 (counting the status line as line 1) retain:\n\n```text\nx-tesseract-columns: CIP6 ID,CIP6,Year,Completions,Top Completions\nx-tesseract-queryrows: 60\nx-tesseract-totalrows: 60\n```\n\nThese are **reported header values**, not 60 recovered rows. The four requests are the university/gender top-five queries already listed above. This does not establish a 12-year span, ranking or tie behavior, or results for the later top-three variants.\n\nThe original JSONs also separate the HTTP-event clock (`/http/0/date`) from the report clock (`/date`). All dates below are May 28, 2026 UTC; the report dates in the existing evidence were already correctly labeled.\n\n| University / Gender | Retained report JSON | HTTP event | Report | SHA256 of retained, uncompressed provider JSON |\n|---|---|---|---|---|\n| 153658 / 1 | [b658f273](https://urlquery.net/report/b658f273-fd60-4191-b496-d244d47d5531/json) | 00:35:26.339 | 00:35:47 | `4aad92b58f03715d433029ee2b1ccbb441eb0f114d3710490887c2d7ba3351f2` |\n| 153658 / 2 | [dd6c4784](https://urlquery.net/report/dd6c4784-2a86-49d8-8418-431ed781f0b7/json) | 00:35:30.424 | 00:35:51 | `9255cbc45222f46a0e62b21cd7eb7cbd233511220cf8563b4682ac6bded2d94c` |\n| 215062 / 2 | [65144082](https://urlquery.net/report/65144082-bcc5-4e7d-96b9-556f35d63872/json) | 00:35:40.750 | 00:36:02 | `82e62ae8f9d4e34004c981b8b00f8ccf8ecbd8d184ac1d10023df2ad753ea666` |\n| 215062 / 1 | [fabdcd45](https://urlquery.net/report/fabdcd45-6f13-49c8-8823-8650a9905622/json) | 00:35:44.570 | 00:36:05 | `0908f5dda535a478261609e93f51bda46676927dfdfc94f2ad3da49c08349337` |\n\nThe four provider JSONs total 30,960 uncompressed bytes. These hashes identify the retained reports, not the absent DataUSA response bodies. The separate response `Date` headers have second precision. Local retention-manifest `attempted_at_utc` values on September 5 mark acquisition-workflow start, assigned before cache checking/request waiting; they are not exact HTTP-send, completion, publication, or historical event clocks.\n\n**Still unresolved:** all four `/http/0/response/data/data` fields are null, with `size_decoded: 0` and SHA256(empty), despite reported nonzero response sizes. This establishes missing readable bytes in these retained reports, not an empty origin response. No completion values or top-five/top-three row comparison were recovered. This is a clarification of existing evidence; all acceptance criteria and the open question remain unchanged.\n\n<!-- swarmstatus:datausa16-retained-header-clock-supplement -->\n\n## Reviewed partial package — 2026-09-05\n\nThe [portable metadata supplement in PR #53](https://github.com/aadarwal/swarmstatus-bounties/pull/53) was accepted after separate source and package reviews. It preserves selected headers, query identities, source hashes and separate clocks, with offline integrity checks. The complete original reports remain outside the public package; their source verification is documented separately. This makes the already-reported metadata reviewable and supplies no recovered completion values. The readable-body and top-five/top-three comparison criteria remain unresolved; #16 stays open.\n\n<!-- swarmstatus:datausa16-partial-pr53 -->\n", "limits": "- 18 receipts match all analytical query parameters; only locale is omitted from that signature. Scheme and fragment are outside analytical parameter identity.\n- Some provider response metadata reports nonzero bytes with the empty-content SHA256, so it cannot prove the origin response bytes.\n- The four initial reports precede their first matching original wiki rows by roughly 7–8 minutes. That is observation order, not actor identity or proof that the report caused the wiki publication.", "sources": [{"label": "Retained record 12f0c6b3", "url": "https://swarmstatus.com/api/record?id=12f0c6b36b43723d203afa3ee2dd1c4e"}], "evidence_prs": ["https://github.com/aadarwal/swarmstatus-bounties/pull/53"], "url": "https://swarmstatus.com/contribute/16", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/16", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/16#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-07T11:55:25Z", "areas": ["DataUSA"]}, {"id": "bounty-15", "number": 15, "teaser": null, "title": "Find a primary artifact for the older PBS dashboard and its filters", "status": "open", "question": "Locate a retained primary publication linking PBS-dashboard-AgeGroup-Monthly-date-20241128/PBSdashboard to Victoria, Wodonga or Ballarat, and Dermatologicals. Establish how its filter names and data period relate to the later PBS-dashboard-AgeGroup-Monthly-date-20250430 and PBSdashboardallATC1-ATC2medicines-Agegroup workbooks.", "source_context": "- Primary source\n  Old workbook CSV submission carries State/Territory=Victoria, LGA=Wodonga, ATC Level 1=Dermatologicals. The direct request has no response status.\n  time raw: 2026-06-19T04:32:49Z.\n  time basis: URLQuery report date, not source publication or actor identity.\n  Acquisition record ID: 062fd760e98ece64a2d6f0083464735e (outside the focused explorer; use the primary locator above).\n  Provider report JSON\n\n- Primary source\n  A retained later-workbook request uses different Select-prefixed filters, Wodonga, Dermatologicals and Rolling 12 months average.\n  time raw: 2026-06-18T14:04:07Z.\n  time basis: URLQuery report date, not source publication or actor identity.\n  Acquisition record ID: 577e70f375aed97294a175bd30c8f1dd (outside the focused explorer; use the primary locator above).\n  Provider report JSON\n\n- Primary source\n  time utc: 2026-06-17T07:27:04Z.\n  source sha256: 60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793.\n  native rev id: dse~AgentAIHWBridgeSep18@1.\n  Retained record 05bca457", "deliverables": ["Supply a retained artifact or archive capture with a stable URL, acquisition date, source date when available, and a content hash.", "Preserve the full resource identifier and relevant filters; explain differences from the evidence listed here.", "Separate submitted URL, observed request, response metadata, readable response body, and verified answer; do not infer an actor from submitter or referrer metadata.", "Recover an independent artifact for the exact 20241128 workbook, not merely a similarly named PBS dashboard.", "Document field-name mapping and the requested time period before claiming identical query constraints across versions.", "Show whether exports honored the filters if claiming answer equivalence."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Supply a retained artifact or archive capture with a stable URL, acquisition date, source date when available, and a content hash.\nPreserve the full resource identifier and relevant filters; explain differences from the evidence listed here.\nSeparate submitted URL, observed request, response metadata, readable response body, and verified answer; do not infer an actor from submitter or referrer metadata.\nRecover an independent artifact for the exact 20241128 workbook, not merely a similarly named PBS dashboard.\nDocument field-name mapping and the requested time period before claiming identical query constraints across versions.\nShow whether exports honored the filters if claiming answer equivalence."}], "research_notes": [{"heading": "Research update — September 5", "text": "Reviewed partial evidence and reproduction package (PR #45) preserves a readable current image export from the exact older PBS workbook and its control states. The visible initial controls and exported labels differ from the legacy URL filters; after selecting Victoria and Wodonga manually, the medicine menu showed “No Items.” No historical filtered values, underlying data period or cross-version equivalence were established. This advances current workbook evidence and does not validate PR #36. This question remains open."}], "issue_text": "## Question\n\nLocate a retained primary publication linking PBS-dashboard-AgeGroup-Monthly-date-20241128/PBSdashboard to Victoria, Wodonga or Ballarat, and Dermatologicals. Establish how its filter names and data period relate to the later PBS-dashboard-AgeGroup-Monthly-date-20250430 and PBSdashboardallATC1-ATC2medicines-Agegroup workbooks.\n\n## Existing evidence\n\n- [Primary source](https://urlquery.net/report/18577f55-fbf5-4ec1-9cd4-35e0e68d3f0c)\n  Old workbook CSV submission carries State/Territory=Victoria, LGA=Wodonga, ATC Level 1=Dermatologicals. The direct request has no response status.\n  time raw: `2026-06-19T04:32:49Z`.\n  time basis: `URLQuery report date, not source publication or actor identity`.\n  Acquisition record ID: `062fd760e98ece64a2d6f0083464735e` (outside the focused explorer; use the primary locator above).\n  [Provider report JSON](https://urlquery.net/report/18577f55-fbf5-4ec1-9cd4-35e0e68d3f0c/json)\n\n- [Primary source](https://urlquery.net/report/0054ba18-7f97-407a-af73-b2971fd12898)\n  A retained later-workbook request uses different Select-prefixed filters, Wodonga, Dermatologicals and Rolling 12 months average.\n  time raw: `2026-06-18T14:04:07Z`.\n  time basis: `URLQuery report date, not source publication or actor identity`.\n  Acquisition record ID: `577e70f375aed97294a175bd30c8f1dd` (outside the focused explorer; use the primary locator above).\n  [Provider report JSON](https://urlquery.net/report/0054ba18-7f97-407a-af73-b2971fd12898/json)\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~AgentAIHWBridgeSep18.html#rev-1)\n  time utc: `2026-06-17T07:27:04Z`.\n  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.\n  native rev id: `dse~AgentAIHWBridgeSep18@1`.\n  [Retained record 05bca457](https://swarmstatus.com/api/record?id=05bca45740dbd1280c1a79fb411d9b5d)\n\n## Acceptance criteria\n\n- [ ] Supply a retained artifact or archive capture with a stable URL, acquisition date, source date when available, and a content hash.\n- [ ] Preserve the full resource identifier and relevant filters; explain differences from the evidence listed here.\n- [ ] Separate submitted URL, observed request, response metadata, readable response body, and verified answer; do not infer an actor from submitter or referrer metadata.\n- [ ] Recover an independent artifact for the exact 20241128 workbook, not merely a similarly named PBS dashboard.\n- [ ] Document field-name mapping and the requested time period before claiming identical query constraints across versions.\n- [ ] Show whether exports honored the filters if claiming answer equivalence.\n\n## Caveats and alternatives\n\n- Nine receipts directly submit the 20241128 workbook; its exact identifier is absent from the retained primary-body corpus.\n- A common workbook subject or shared location names alone do not prove the same task.\n\n## Prior work\n\nNew exact older-workbook target outside the current primary fingerprint index.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:uqr-pbs-20241128 -->\n\n\n## Research update — September 5\n\n[Reviewed partial evidence and reproduction package (PR #45)](https://github.com/aadarwal/swarmstatus-bounties/pull/45) preserves a readable current image export from the exact older PBS workbook and its control states. The visible initial controls and exported labels differ from the legacy URL filters; after selecting Victoria and Wodonga manually, the medicine menu showed “No Items.” No historical filtered values, underlying data period or cross-version equivalence were established. This advances current workbook evidence and does not validate PR #36. **This question remains open.**\n\n<!-- swarmstatus:pbs-partial-pr45 -->\n", "limits": "- Nine receipts directly submit the 20241128 workbook; its exact identifier is absent from the retained primary-body corpus.\n- A common workbook subject or shared location names alone do not prove the same task.", "sources": [{"label": "Retained record 05bca457", "url": "https://swarmstatus.com/api/record?id=05bca45740dbd1280c1a79fb411d9b5d"}], "evidence_prs": ["https://github.com/aadarwal/swarmstatus-bounties/pull/45"], "url": "https://swarmstatus.com/contribute/15", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/15", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/15#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T19:24:40Z", "areas": ["PBS"]}, {"id": "bounty-13", "number": 13, "teaser": null, "title": "Verify the June SEC county response provenance against the recovered current file", "status": "open", "question": "A September 5 direct Investor.gov capture is now retained: 147,840 bytes, SHA256 19f21855d65a95e4fecd49ee1dd0127748dbebb1eb218c4c877efbc707093297. Its bytes match the hash and size reported for the June 18 SEC county.json response, and a proposed reproducible comparison matches the 25 retained Massachusetts rows and three slices. Can an independently retained June response body or documented provider capture semantics establish the historical byte provenance and clarify which representation the reported hash identifies?", "source_context": "- Primary source\n  The report dated 15:35:48Z contains a GET initiated at 15:35:24.375Z, transaction http[1], with 200 response metadata. Raw Content-Type is application/json; browser MIME is application/vnd.mozilla.json.view. response.data.size is 147840, size_decoded is 19168, and compressed-transfer Content-Length is 18032. Reported SHA256 19f21855d65a95e4fecd49ee1dd0127748dbebb1eb218c4c877efbc707093297 matches the current Investor.gov capture.\n  time raw: 2026-06-18T15:35:48Z.\n  time basis: URLQuery report date, not source publication or actor identity.\n  Acquisition record ID: 0a7c2ad458c2277ab5121e7caa6b3a26 (outside the focused explorer; use the primary locator above).\n  Provider report JSON\n\n- Primary source\n  The report dated 17:04:01Z contains a GET initiated at 17:03:35.100Z, transaction http[33], with 404 HTML response metadata and 53,435 reported bytes.\n  time raw: 2026-06-18T17:04:01Z.\n  time basis: URLQuery report date, not source publication or actor identity.\n  Acquisition record ID: 0989ef4cfbba668b6876bb5bfb7053b9 (outside the focused explorer; use the primary locator above).\n  Provider report JSON\n\n- Primary source\n  /file/countyjson is a separate HTML landing page. Its 200 response is not the JSON data file.\n  time raw: 2026-06-18T14:41:14Z.\n  time basis: URLQuery report date, not source publication or actor identity.\n  Acquisition record ID: a8571a2b3d1f33d32bee8dde21010e7a (outside the focused explorer; use the primary locator above).\n  Provider report JSON\n\n- Primary source\n  time utc: 2026-06-18T14:10:56Z.\n  source sha256: 60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793.\n  native rev id: probier~RecentChanges@40.\n  Retained record 9b23ceaf\n\n- Primary source\n  Current direct capture independently verified at 147840 bytes and the same reported SHA256. Historical response-body provenance is the remaining question.", "deliverables": ["Supply a retained artifact or archive capture with a stable URL, acquisition date, source date when available, and a content hash.", "Preserve the full resource identifier and relevant filters; explain differences from the evidence listed here.", "Separate submitted URL, observed request, response metadata, readable response body, and verified answer; do not infer an actor from submitter or referrer metadata.", "Review the existing current-file/table comparison, then provide an independently dated June response body or source-backed clarification of the provider hash/size representation that materially closes the remaining historical provenance gap.", "Preserve the distinction between /file/countyjson and /files/county.json.", "Do not describe the two sample times as a global availability cutoff; other receipts may have different status at overlapping times.", "Preserve report time, transaction request time, raw response headers, browser MIME and all three size fields separately. A current mirror or repeat of the same reported hash is not a newly recovered historical body."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Supply a retained artifact or archive capture with a stable URL, acquisition date, source date when available, and a content hash.\nPreserve the full resource identifier and relevant filters; explain differences from the evidence listed here.\nSeparate submitted URL, observed request, response metadata, readable response body, and verified answer; do not infer an actor from submitter or referrer metadata.\nReview the existing current-file/table comparison, then provide an independently dated June response body or source-backed clarification of the provider hash/size representation that materially closes the remaining historical provenance gap.\nPreserve the distinction between /file/countyjson and /files/county.json.\nDo not describe the two sample times as a global availability cutoff; other receipts may have different status at overlapping times.\nPreserve report time, transaction request time, raw response headers, browser MIME and all three size fields separately. A current mirror or repeat of the same reported hash is not a newly recovered historical body."}], "research_notes": [], "issue_text": "## Question\n\nA September 5 direct Investor.gov capture is now retained: 147,840 bytes, SHA256 19f21855d65a95e4fecd49ee1dd0127748dbebb1eb218c4c877efbc707093297. Its bytes match the hash and size reported for the June 18 SEC county.json response, and a proposed reproducible comparison matches the 25 retained Massachusetts rows and three slices. Can an independently retained June response body or documented provider capture semantics establish the historical byte provenance and clarify which representation the reported hash identifies?\n\n## Existing evidence\n\n- [Primary source](https://urlquery.net/report/0873ec25-2bff-4610-b7c0-6cbd5bb31933)\n  The report dated 15:35:48Z contains a GET initiated at 15:35:24.375Z, transaction http[1], with 200 response metadata. Raw Content-Type is application/json; browser MIME is application/vnd.mozilla.json.view. response.data.size is 147840, size_decoded is 19168, and compressed-transfer Content-Length is 18032. Reported SHA256 19f21855d65a95e4fecd49ee1dd0127748dbebb1eb218c4c877efbc707093297 matches the current Investor.gov capture.\n  time raw: `2026-06-18T15:35:48Z`.\n  time basis: `URLQuery report date, not source publication or actor identity`.\n  Acquisition record ID: `0a7c2ad458c2277ab5121e7caa6b3a26` (outside the focused explorer; use the primary locator above).\n  [Provider report JSON](https://urlquery.net/report/0873ec25-2bff-4610-b7c0-6cbd5bb31933/json)\n\n- [Primary source](https://urlquery.net/report/fa3b6ba5-cd7f-4d08-a795-e61b51cb5acb)\n  The report dated 17:04:01Z contains a GET initiated at 17:03:35.100Z, transaction http[33], with 404 HTML response metadata and 53,435 reported bytes.\n  time raw: `2026-06-18T17:04:01Z`.\n  time basis: `URLQuery report date, not source publication or actor identity`.\n  Acquisition record ID: `0989ef4cfbba668b6876bb5bfb7053b9` (outside the focused explorer; use the primary locator above).\n  [Provider report JSON](https://urlquery.net/report/fa3b6ba5-cd7f-4d08-a795-e61b51cb5acb/json)\n\n- [Primary source](https://urlquery.net/report/00584cc4-d824-4079-9657-aac02fff0774)\n  /file/countyjson is a separate HTML landing page. Its 200 response is not the JSON data file.\n  time raw: `2026-06-18T14:41:14Z`.\n  time basis: `URLQuery report date, not source publication or actor identity`.\n  Acquisition record ID: `a8571a2b3d1f33d32bee8dde21010e7a` (outside the focused explorer; use the primary locator above).\n  [Provider report JSON](https://urlquery.net/report/00584cc4-d824-4079-9657-aac02fff0774/json)\n\n- [Primary source](https://collusion.wiki/explorer/page/probier~RecentChanges.html#rev-40)\n  time utc: `2026-06-18T14:10:56Z`.\n  source sha256: `60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793`.\n  native rev id: `probier~RecentChanges@40`.\n  [Retained record 9b23ceaf](https://swarmstatus.com/api/record?id=9b23ceafbc2ce6ae505dc11bf3af806b)\n\n- [Primary source](https://www.investor.gov/files/county.json)\n  Current direct capture independently verified at 147840 bytes and the same reported SHA256. Historical response-body provenance is the remaining question.\n\n## Acceptance criteria\n\n- [ ] Supply a retained artifact or archive capture with a stable URL, acquisition date, source date when available, and a content hash.\n- [ ] Preserve the full resource identifier and relevant filters; explain differences from the evidence listed here.\n- [ ] Separate submitted URL, observed request, response metadata, readable response body, and verified answer; do not infer an actor from submitter or referrer metadata.\n- [ ] Review the existing current-file/table comparison, then provide an independently dated June response body or source-backed clarification of the provider hash/size representation that materially closes the remaining historical provenance gap.\n- [ ] Preserve the distinction between /file/countyjson and /files/county.json.\n- [ ] Do not describe the two sample times as a global availability cutoff; other receipts may have different status at overlapping times.\n- [ ] Preserve report time, transaction request time, raw response headers, browser MIME and all three size fields separately. A current mirror or repeat of the same reported hash is not a newly recovered historical body.\n\n## Caveats and alternatives\n\n- URLQuery report JSON records browser response metadata; it supplies no decoded response body for the cited transactions.\n- application/vnd.mozilla.json.view may describe a browser rendering; the reported hash is not automatically an origin-file hash.\n\n## Prior work\n\nNew exact request/status comparisons across the complete receipt set, beyond the two representative SEC receipts in V5.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:uqr-sec-county-body -->\n\n\n## Current verification submission\n\n[PR #27](https://github.com/aadarwal/swarmstatus-bounties/pull/27) contains the primary capture, retained table, selected receipt fields and an offline verification script. It is a proposed answer to the bounded numeric/hash comparison in #26. This issue retains the separate historical response-body/provider provenance gap.\n", "limits": "- URLQuery report JSON records browser response metadata; it supplies no decoded response body for the cited transactions.\n- application/vnd.mozilla.json.view may describe a browser rendering; the reported hash is not automatically an origin-file hash.", "sources": [{"label": "Retained record 9b23ceaf", "url": "https://swarmstatus.com/api/record?id=9b23ceafbc2ce6ae505dc11bf3af806b"}], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/13", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/13", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/13#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T17:48:36Z", "areas": ["SEC"]}, {"id": "bounty-12", "number": 12, "teaser": null, "title": "Find the independent source of the AIHW aged-care mood-disorder task", "status": "open", "question": "Locate a retained task, paste, wiki body or other publication that contains AGE115_MentalhealthinAgedCare_19072024/F05-Age-specificcruderates together with Cohort=Permanent residential aged care and Condition=Mood disorders. Does an independent artifact connect those complete constraints to the documented research corpus?", "source_context": "- Primary source\n  Exact filtered PNG request; transaction 4 returns 403 HTML, transaction 9 returns 200 image/png, 71,515 reported bytes. No readable body is supplied in report JSON.\n  time raw: 2026-06-18T04:11:43Z.\n  time basis: URLQuery report date, not source publication or actor identity.\n  Acquisition record ID: 30057b302c6a63d19e598a7a249107dd (outside the focused explorer; use the primary locator above).\n  Provider report JSON\n\n- Primary source\n  Referrer aggregate points from the b7ps3 inspector to a pure.md wrapper of this exact sheet. It contains no dated publication or cohort/condition parameters.\n  Acquisition record ID: 819b982700980402299f33ad46251c38 (outside the focused explorer; use the primary locator above).\n\n- Primary source\n  Same aggregate includes a CORS wrapper of the sheet CSV; referrer time is NULL.\n  Acquisition record ID: 76f091e68ea7405f78ca531b27a7ade3 (outside the focused explorer; use the primary locator above).", "deliverables": ["Supply a retained artifact or archive capture with a stable URL, acquisition date, source date when available, and a content hash.", "Preserve the full resource identifier and relevant filters; explain differences from the evidence listed here.", "Separate submitted URL, observed request, response metadata, readable response body, and verified answer; do not infer an actor from submitter or referrer metadata.", "Match both cohort and condition as well as the exact workbook and sheet. A bare AIHW hostname is insufficient.", "Explain whether the new item is an independent publication, a replay or a copy of a disclosed report."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Supply a retained artifact or archive capture with a stable URL, acquisition date, source date when available, and a content hash.\nPreserve the full resource identifier and relevant filters; explain differences from the evidence listed here.\nSeparate submitted URL, observed request, response metadata, readable response body, and verified answer; do not infer an actor from submitter or referrer metadata.\nMatch both cohort and condition as well as the exact workbook and sheet. A bare AIHW hostname is insufficient.\nExplain whether the new item is an independent publication, a replay or a copy of a disclosed report."}], "research_notes": [{"heading": "Research update — September 5", "text": "The publisher PNG is recovered and matches 13 historical response hashes. Its visible mode is Proportion of people with the exact cohort/condition. The acquisition/receipt URLs identify the workbook and sheet. Reviewed recovery, attribution and offline verification.\n\nThis bounty remains open: an independent task-origin or staging publication containing all constraints has not been found. The supplementary workbook is not the image’s age-by-sex series."}], "issue_text": "## Question\n\nLocate a retained task, paste, wiki body or other publication that contains AGE115_MentalhealthinAgedCare_19072024/F05-Age-specificcruderates together with Cohort=Permanent residential aged care and Condition=Mood disorders. Does an independent artifact connect those complete constraints to the documented research corpus?\n\n## Existing evidence\n\n- [Primary source](https://urlquery.net/report/66e46234-179e-4214-ada1-fc3ed344d1ae)\n  Exact filtered PNG request; transaction 4 returns 403 HTML, transaction 9 returns 200 image/png, 71,515 reported bytes. No readable body is supplied in report JSON.\n  time raw: `2026-06-18T04:11:43Z`.\n  time basis: `URLQuery report date, not source publication or actor identity`.\n  Acquisition record ID: `30057b302c6a63d19e598a7a249107dd` (outside the focused explorer; use the primary locator above).\n  [Provider report JSON](https://urlquery.net/report/66e46234-179e-4214-ada1-fc3ed344d1ae/json)\n\n- [Primary source](https://vanderbi.lt/b7ps3+)\n  Referrer aggregate points from the b7ps3 inspector to a pure.md wrapper of this exact sheet. It contains no dated publication or cohort/condition parameters.\n  Acquisition record ID: `819b982700980402299f33ad46251c38` (outside the focused explorer; use the primary locator above).\n\n- [Primary source](https://vanderbi.lt/b7ps3+)\n  Same aggregate includes a CORS wrapper of the sheet CSV; referrer time is NULL.\n  Acquisition record ID: `76f091e68ea7405f78ca531b27a7ade3` (outside the focused explorer; use the primary locator above).\n\n## Acceptance criteria\n\n- [ ] Supply a retained artifact or archive capture with a stable URL, acquisition date, source date when available, and a content hash.\n- [ ] Preserve the full resource identifier and relevant filters; explain differences from the evidence listed here.\n- [ ] Separate submitted URL, observed request, response metadata, readable response body, and verified answer; do not infer an actor from submitter or referrer metadata.\n- [ ] Match both cohort and condition as well as the exact workbook and sheet. A bare AIHW hostname is insufficient.\n- [ ] Explain whether the new item is an independent publication, a replay or a copy of a disclosed report.\n\n## Caveats and alternatives\n\n- 148 receipts mention this exact workbook/sheet, including 133 direct submissions. This does not identify 148 independent tasks.\n- The retained primary-body corpus contains no occurrence of this workbook identifier. Two referrer-aggregate records already contain its unfiltered sheet URL.\n- A recorded PNG response does not establish that the requested filters were honored or an answer was read.\n\n## Prior work\n\nNewly resolved target cluster and receipt-to-referrer resource bridge; the underlying primary task publication is still missing.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:uqr-aged-care-source -->\n\n\n## Research update — September 5\n\nThe publisher PNG is recovered and matches 13 historical response hashes. Its visible mode is **Proportion of people** with the exact cohort/condition. The acquisition/receipt URLs identify the workbook and sheet. [Reviewed recovery, attribution and offline verification](https://github.com/aadarwal/swarmstatus-bounties/pull/32).\n\nThis bounty remains open: an independent task-origin or staging publication containing all constraints has not been found. The supplementary workbook is not the image’s age-by-sex series.\n", "limits": "- 148 receipts mention this exact workbook/sheet, including 133 direct submissions. This does not identify 148 independent tasks.\n- The retained primary-body corpus contains no occurrence of this workbook identifier. Two referrer-aggregate records already contain its unfiltered sheet URL.\n- A recorded PNG response does not establish that the requested filters were honored or an answer was read.", "sources": [], "evidence_prs": ["https://github.com/aadarwal/swarmstatus-bounties/pull/32"], "url": "https://swarmstatus.com/contribute/12", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/12", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/12#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T18:57:05Z", "areas": ["aged-care"]}, {"id": "bounty-11", "number": 11, "teaser": null, "title": "Find the GDDY→TWLO same-date retrieval pair on another surface", "status": "in-review", "question": "Search for the ordered pair GDDY then TWLO with from=to=20191115, including direct Yahoo Japan routes and embedded markdown.new targets. Find an additional staging artifact and distinguish copied source blocks from an independently timestamped observation.", "source_context": "- Primary source\n  time raw: 2026-05-28 16:00:41.\n  time basis: raw_unzoned.\n  Retained record e960202e\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://finance.yahoo.co.jp/quote/GDDY/history?from=20191115&to=20191115\n\n\n- Primary source\n  time raw: 2026-05-28 16:49:36.\n  time basis: raw_unzoned.\n  Retained record 5426a826\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://pure.md/finance.yahoo.com/quote/TWLO/history?period1=1573776000&period2=1573948800&interval=1d&filter=history&frequency=1d\n\n\n- Primary source\n  time raw: 2026-05-28T18:53:38Z.\n  time basis: source_export_reqlog.\n  Retained record 86be648c\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://markdown.new/example.com?url=https%3A%2F%2Ffinance.yahoo.co.jp%2Fquote%2FGDDY%2Fhistory%3Ffrom%3D20191115%26to%3D20191115\n\n\n- Primary source\n  time raw: 2026-05-28T19:01:25Z.\n  time basis: source_export_reqlog.\n  Retained record 6d323913\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://markdown.new/example.com?url=https%3A%2F%2Ffinance.yahoo.co.jp%2Fquote%2FGDDY%2Fhistory%3Ffrom%3D20191115%26to%3D20191115\nhttps://markdown.new/example.com?url=https%3A%2F%2Ffinance.yahoo.co.jp%2Fquote%2FTWLO%2Fhistory%3Ffrom%3D20191115%26to%3D20191115", "deliverables": ["Provide exact source locators, retained content and an acquisition timestamp; include an archive/provider timestamp when available.", "Match the complete resource identifier/query bundle, not just a broad host or generic agent wording.", "State what is new relative to the evidence listed here and check archive-summary, exact-copy and source-export overlaps.", "Keep source clock bases explicit and distinguish a stored URL from proof of successful retrieval or message delivery.", "An ordinary original data-source page alone does not establish a new staging surface; the submission must supply publication/registration context or clearly label it as an unresolved candidate."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Provide exact source locators, retained content and an acquisition timestamp; include an archive/provider timestamp when available.\nMatch the complete resource identifier/query bundle, not just a broad host or generic agent wording.\nState what is new relative to the evidence listed here and check archive-summary, exact-copy and source-export overlaps.\nKeep source clock bases explicit and distinguish a stored URL from proof of successful retrieval or message delivery.\nAn ordinary original data-source page alone does not establish a new staging surface; the submission must supply publication/registration context or clearly label it as an unresolved candidate."}], "research_notes": [], "issue_text": "## Question\n\nSearch for the ordered pair GDDY then TWLO with from=to=20191115, including direct Yahoo Japan routes and embedded markdown.new targets. Find an additional staging artifact and distinguish copied source blocks from an independently timestamped observation.\n\n## Existing evidence\n\n- [Primary source](https://vanderbi.lt/gadmydaclose2019+)\n  time raw: `2026-05-28 16:00:41`.\n  time basis: `raw_unzoned`.\n  [Retained record e960202e](https://swarmstatus.com/api/record?id=e960202ecdd806d6157eb6795d7fa5b2)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://finance.yahoo.co.jp/quote/GDDY/history?from=20191115&to=20191115\n```\n\n- [Primary source](https://vanderbi.lt/agent0twlo900+)\n  time raw: `2026-05-28 16:49:36`.\n  time basis: `raw_unzoned`.\n  [Retained record 5426a826](https://swarmstatus.com/api/record?id=5426a8262140b2a68f0c249b7649f0da)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://pure.md/finance.yahoo.com/quote/TWLO/history?period1=1573776000&period2=1573948800&interval=1d&filter=history&frequency=1d\n```\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~Testabc.html#rev-2)\n  time raw: `2026-05-28T18:53:38Z`.\n  time basis: `source_export_reqlog`.\n  [Retained record 86be648c](https://swarmstatus.com/api/record?id=86be648c2518cbc6d3311fa8a658998a)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://markdown.new/example.com?url=https%3A%2F%2Ffinance.yahoo.co.jp%2Fquote%2FGDDY%2Fhistory%3Ffrom%3D20191115%26to%3D20191115\n```\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~AgentYahooHistoricalRowsBridgeAA.html#rev-1)\n  time raw: `2026-05-28T19:01:25Z`.\n  time basis: `source_export_reqlog`.\n  [Retained record 6d323913](https://swarmstatus.com/api/record?id=6d323913d79ff990af755f9e6c8f53a8)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://markdown.new/example.com?url=https%3A%2F%2Ffinance.yahoo.co.jp%2Fquote%2FGDDY%2Fhistory%3Ffrom%3D20191115%26to%3D20191115\nhttps://markdown.new/example.com?url=https%3A%2F%2Ffinance.yahoo.co.jp%2Fquote%2FTWLO%2Fhistory%3Ffrom%3D20191115%26to%3D20191115\n```\n\n## Acceptance criteria\n\n- [ ] Provide exact source locators, retained content and an acquisition timestamp; include an archive/provider timestamp when available.\n- [ ] Match the complete resource identifier/query bundle, not just a broad host or generic agent wording.\n- [ ] State what is new relative to the evidence listed here and check archive-summary, exact-copy and source-export overlaps.\n- [ ] Keep source clock bases explicit and distinguish a stored URL from proof of successful retrieval or message delivery.\n- [ ] An ordinary original data-source page alone does not establish a new staging surface; the submission must supply publication/registration context or clearly label it as an unresolved candidate.\n\n## Caveats and alternatives\n\n- The repeated pair can be copied; it is a search fingerprint, not an identity or communication edge.\n- A Japanese locale endpoint for a US stock does not establish an actor country or location.\n- Source-title repetition is weaker evidence than the full symbol/date bundle.\n\n## Prior work\n\nYahoo Japan/GDDY was already known in subagent_reports/9. The ordered paired-symbol/date signature is an incremental retrieval pattern.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:ntp-yahoo -->\n", "limits": "- The repeated pair can be copied; it is a search fingerprint, not an identity or communication edge.\n- A Japanese locale endpoint for a US stock does not establish an actor country or location.\n- Source-title repetition is weaker evidence than the full symbol/date bundle.", "sources": [{"label": "Retained record e960202e", "url": "https://swarmstatus.com/api/record?id=e960202ecdd806d6157eb6795d7fa5b2"}, {"label": "Retained record 5426a826", "url": "https://swarmstatus.com/api/record?id=5426a8262140b2a68f0c249b7649f0da"}, {"label": "Retained record 86be648c", "url": "https://swarmstatus.com/api/record?id=86be648c2518cbc6d3311fa8a658998a"}], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/11", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/11", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/11#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T17:38:48Z", "areas": ["Yahoo"]}, {"id": "bounty-10", "number": 10, "teaser": null, "title": "How many task joins disappear when overwritten pages are split by revision?", "status": "open", "question": "Use the CashierCoordJan08OAI cashier-to-UNCTAD overwrite as a negative control. Identify further pages whose retained revisions switch unrelated task targets, and quantify which whole-object similarity claims would disappear when evidence is restricted to introduced targets in a coherent revision interval.", "source_context": "- Primary source\n  time raw: 2026-06-20 17:01:18.\n  time basis: raw_unzoned.\n  Retained record ea384cd3\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://allorigins.hexlet.app/raw?url=https%3A%2F%2Functadstat.unctad.org%2FNowcasts%2Fx_merch_val%2Fx_merch_val-2021-1.csv\n\n\n- Primary source\n  time raw: 2026-06-20 17:01:20.\n  time basis: raw_unzoned.\n  Retained record 15952dac\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://allorigins.hexlet.app/raw?url=https%3A%2F%2Functadstat.unctad.org%2FNowcasts%2Fx_merch_val%2Fx_merch_val-2021-1.csv\n\n\n- Primary source\n  time raw: 2026-06-20T22:15:55Z.\n  time basis: source_export_reqlog.\n  Retained record 778796a2\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://unctadstat.unctad.org/Nowcasts/x_merch_val/x_merch_val-2021-1.csv", "deliverables": ["Supply a reproducible query/script over source-qualified revisions, with before/after record IDs and retained text for every reported transition.", "Evaluate the known cashier→UNCTAD overwrite and report at least two further supported transitions or a documented negative result.", "Show which candidate links change under revision-interval grouping, while preserving legitimate links supported within an interval.", "Do not infer agent identities or task continuity from page names or repeated writer labels."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Supply a reproducible query/script over source-qualified revisions, with before/after record IDs and retained text for every reported transition.\nEvaluate the known cashier→UNCTAD overwrite and report at least two further supported transitions or a documented negative result.\nShow which candidate links change under revision-interval grouping, while preserving legitimate links supported within an interval.\nDo not infer agent identities or task continuity from page names or repeated writer labels."}], "research_notes": [], "issue_text": "## Question\n\nUse the CashierCoordJan08OAI cashier-to-UNCTAD overwrite as a negative control. Identify further pages whose retained revisions switch unrelated task targets, and quantify which whole-object similarity claims would disappear when evidence is restricted to introduced targets in a coherent revision interval.\n\n## Existing evidence\n\n- [Primary source](https://vanderbi.lt/tu41o+)\n  time raw: `2026-06-20 17:01:18`.\n  time basis: `raw_unzoned`.\n  [Retained record ea384cd3](https://swarmstatus.com/api/record?id=ea384cd3ed69e7d86de5e08be926ebe8)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://allorigins.hexlet.app/raw?url=https%3A%2F%2Functadstat.unctad.org%2FNowcasts%2Fx_merch_val%2Fx_merch_val-2021-1.csv\n```\n\n- [Primary source](https://vanderbi.lt/nudcb+)\n  time raw: `2026-06-20 17:01:20`.\n  time basis: `raw_unzoned`.\n  [Retained record 15952dac](https://swarmstatus.com/api/record?id=15952dac4cb95a2a66248930e17ee07d)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://allorigins.hexlet.app/raw?url=https%3A%2F%2Functadstat.unctad.org%2FNowcasts%2Fx_merch_val%2Fx_merch_val-2021-1.csv\n```\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~CashierCoordJan08OAI.html#rev-7)\n  time raw: `2026-06-20T22:15:55Z`.\n  time basis: `source_export_reqlog`.\n  [Retained record 778796a2](https://swarmstatus.com/api/record?id=778796a2eea2e7c0006c9a2d9bc18e2c)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://unctadstat.unctad.org/Nowcasts/x_merch_val/x_merch_val-2021-1.csv\n```\n\n## Acceptance criteria\n\n- [ ] Supply a reproducible query/script over source-qualified revisions, with before/after record IDs and retained text for every reported transition.\n- [ ] Evaluate the known cashier→UNCTAD overwrite and report at least two further supported transitions or a documented negative result.\n- [ ] Show which candidate links change under revision-interval grouping, while preserving legitimate links supported within an interval.\n- [ ] Do not infer agent identities or task continuity from page names or repeated writer labels.\n\n## Caveats and alternatives\n\n- The page title is stale after overwrite and must not connect UNCTAD to the cashier task.\n- Repeated aliases targeting one URL count as registrations, not agents or distinct research messages.\n- Do not align unzoned shortener clocks to original wiki UTC by silently applying a guessed offset.\n\n## Prior work\n\nThe UNCTAD family was already known. The revision-level overwrite and resulting false task join are newly documented here.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:ntp-unctad -->\n", "limits": "- The page title is stale after overwrite and must not connect UNCTAD to the cashier task.\n- Repeated aliases targeting one URL count as registrations, not agents or distinct research messages.\n- Do not align unzoned shortener clocks to original wiki UTC by silently applying a guessed offset.", "sources": [{"label": "Retained record ea384cd3", "url": "https://swarmstatus.com/api/record?id=ea384cd3ed69e7d86de5e08be926ebe8"}, {"label": "Retained record 15952dac", "url": "https://swarmstatus.com/api/record?id=15952dac4cb95a2a66248930e17ee07d"}, {"label": "Retained record 778796a2", "url": "https://swarmstatus.com/api/record?id=778796a2eea2e7c0006c9a2d9bc18e2c"}], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/10", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/10", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/10#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T17:38:48Z", "areas": ["data-quality"]}, {"id": "bounty-9", "number": 9, "teaser": null, "title": "Does the exact NAEP alias/query pair recur on a third surface?", "status": "in-review", "question": "The identical alias nrcnaepres9983 and grade 12 science 2019 HAOHTAIC query occur at both Vanderbilt and RMN. Find a third independently sourced registration or message with the same high-entropy alias/query pair, and test whether the current entries are copied/imported records or separate registrations.", "source_context": "- Primary source\n  time raw: 2026-06-13 02:09.\n  time basis: raw_unzoned.\n  Retained record 450789df\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://www.nationsreportcard.gov/Dataservice/GetAdhocData.aspx?type=data&subject=science&grade=12&subscale=SRPUV&variable=HAOHTAIC&jurisdiction=NP&stattype=MN:MN&Year=2019\n\n\n- Primary source\n  time raw: 2026-06-12 17:09:31.\n  time basis: raw_unzoned.\n  Retained record bca374c2\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://www.nationsreportcard.gov/Dataservice/GetAdhocData.aspx?type=data&subject=science&grade=12&subscale=SRPUV&variable=HAOHTAIC&jurisdiction=NP&stattype=MN:MN&Year=2019", "deliverables": ["Provide exact source locators, retained content and an acquisition timestamp; include an archive/provider timestamp when available.", "Match the complete resource identifier/query bundle, not just a broad host or generic agent wording.", "State what is new relative to the evidence listed here and check archive-summary, exact-copy and source-export overlaps.", "Keep source clock bases explicit and distinguish a stored URL from proof of successful retrieval or message delivery.", "An ordinary original data-source page alone does not establish a new staging surface; the submission must supply publication/registration context or clearly label it as an unresolved candidate."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Provide exact source locators, retained content and an acquisition timestamp; include an archive/provider timestamp when available.\nMatch the complete resource identifier/query bundle, not just a broad host or generic agent wording.\nState what is new relative to the evidence listed here and check archive-summary, exact-copy and source-export overlaps.\nKeep source clock bases explicit and distinguish a stored URL from proof of successful retrieval or message delivery.\nAn ordinary original data-source page alone does not establish a new staging surface; the submission must supply publication/registration context or clearly label it as an unresolved candidate."}], "research_notes": [], "issue_text": "## Question\n\nThe identical alias nrcnaepres9983 and grade 12 science 2019 HAOHTAIC query occur at both Vanderbilt and RMN. Find a third independently sourced registration or message with the same high-entropy alias/query pair, and test whether the current entries are copied/imported records or separate registrations.\n\n## Existing evidence\n\n- [Primary source](https://rmn.re/nrcnaepres9983+)\n  time raw: `2026-06-13 02:09`.\n  time basis: `raw_unzoned`.\n  [Retained record 450789df](https://swarmstatus.com/api/record?id=450789df13b6c28f392700ad20a91558)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://www.nationsreportcard.gov/Dataservice/GetAdhocData.aspx?type=data&subject=science&grade=12&subscale=SRPUV&variable=HAOHTAIC&jurisdiction=NP&stattype=MN:MN&Year=2019\n```\n\n- [Primary source](https://vanderbi.lt/nrcnaepres9983+)\n  time raw: `2026-06-12 17:09:31`.\n  time basis: `raw_unzoned`.\n  [Retained record bca374c2](https://swarmstatus.com/api/record?id=bca374c2713e81cc5ac4bfc9dc62c511)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://www.nationsreportcard.gov/Dataservice/GetAdhocData.aspx?type=data&subject=science&grade=12&subscale=SRPUV&variable=HAOHTAIC&jurisdiction=NP&stattype=MN:MN&Year=2019\n```\n\n## Acceptance criteria\n\n- [ ] Provide exact source locators, retained content and an acquisition timestamp; include an archive/provider timestamp when available.\n- [ ] Match the complete resource identifier/query bundle, not just a broad host or generic agent wording.\n- [ ] State what is new relative to the evidence listed here and check archive-summary, exact-copy and source-export overlaps.\n- [ ] Keep source clock bases explicit and distinguish a stored URL from proof of successful retrieval or message delivery.\n- [ ] An ordinary original data-source page alone does not establish a new staging surface; the submission must supply publication/registration context or clearly label it as an unresolved candidate.\n\n## Caveats and alternatives\n\n- The two registered destinations are identical full bodies, so they are one resource fingerprint, not two independent textual accounts.\n- Both service timestamps are unzoned. Their nine-hour difference must not be treated as publication latency.\n- A registered redirect is not evidence of a successful target request.\n\n## Prior work\n\nThe NAEP family was already named in subagent_reports/8 and9. The exact cross-shortener alias-and-query join is an incremental lead.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:ntp-naep -->\n", "limits": "- The two registered destinations are identical full bodies, so they are one resource fingerprint, not two independent textual accounts.\n- Both service timestamps are unzoned. Their nine-hour difference must not be treated as publication latency.\n- A registered redirect is not evidence of a successful target request.", "sources": [{"label": "Retained record 450789df", "url": "https://swarmstatus.com/api/record?id=450789df13b6c28f392700ad20a91558"}, {"label": "Retained record bca374c2", "url": "https://swarmstatus.com/api/record?id=bca374c2713e81cc5ac4bfc9dc62c511"}], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/9", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/9", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/9#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T17:39:06Z", "areas": ["NAEP"]}, {"id": "bounty-8", "number": 8, "teaser": null, "title": "Trace the MSU review’s exact 20201020093440 archive bridge", "status": "in-review", "question": "Find an additional staging artifact for the MSU Reporter 2018 Talking As Fast As I Can review that includes MemGator memento 20201020093440 or Wayback 20240623185914. Separate the archive snapshot requested from the date the staging artifact was published.", "source_context": "- Primary source\n  time raw: 2026-07-01T10:29:45Z.\n  time basis: source_export_reqlog.\n  Retained record 27a68faa\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://memgator.cs.odu.edu/memento/proxy/20201020093440/www.msureporter.com/2018/06/06/book-review-talking-as-fast-as-i-can/\nhttps://allorigins.hexlet.app/raw?url=https%3A%2F%2Fweb.archive.org%2Fweb%2F20240623185914id_%2Fhttps%3A%2F%2Fwww.msureporter.com%2F2018%2F06%2F06%2Fbook-review-talking-as-fast-as-i-can%2F\n\n\n- Primary source\n  time raw: 2026-07-01T10:10:38Z.\n  time basis: source_export_reqlog.\n  Retained record 7cf5549d\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://memgator.cs.odu.edu/memento/proxy/20201020093440/www.msureporter.com/2018/06/06/book-review-talking-as-fast-as-i-can/\n\n\n- Primary source\n  time raw: 2026-07-01T12:27:34+01:00.\n  time basis: clock_conflict_site_offset.\n  Retained record d8df6b10\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://memgator.cs.odu.edu/memento/proxy/20240623185914/www.msureporter.com/2018/06/06/book-review-talking-as-fast-as-i-can/", "deliverables": ["Provide exact source locators, retained content and an acquisition timestamp; include an archive/provider timestamp when available.", "Match the complete resource identifier/query bundle, not just a broad host or generic agent wording.", "State what is new relative to the evidence listed here and check archive-summary, exact-copy and source-export overlaps.", "Keep source clock bases explicit and distinguish a stored URL from proof of successful retrieval or message delivery.", "An ordinary original data-source page alone does not establish a new staging surface; the submission must supply publication/registration context or clearly label it as an unresolved candidate."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Provide exact source locators, retained content and an acquisition timestamp; include an archive/provider timestamp when available.\nMatch the complete resource identifier/query bundle, not just a broad host or generic agent wording.\nState what is new relative to the evidence listed here and check archive-summary, exact-copy and source-export overlaps.\nKeep source clock bases explicit and distinguish a stored URL from proof of successful retrieval or message delivery.\nAn ordinary original data-source page alone does not establish a new staging surface; the submission must supply publication/registration context or clearly label it as an unresolved candidate."}], "research_notes": [], "issue_text": "## Question\n\nFind an additional staging artifact for the MSU Reporter 2018 Talking As Fast As I Can review that includes MemGator memento 20201020093440 or Wayback 20240623185914. Separate the archive snapshot requested from the date the staging artifact was published.\n\n## Existing evidence\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~AgentMsuReporterArchiveLinkQ842.html#rev-1)\n  time raw: `2026-07-01T10:29:45Z`.\n  time basis: `source_export_reqlog`.\n  [Retained record 27a68faa](https://swarmstatus.com/api/record?id=27a68faa26d0c7ee19d5a8594eec7bb1)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://memgator.cs.odu.edu/memento/proxy/20201020093440/www.msureporter.com/2018/06/06/book-review-talking-as-fast-as-i-can/\nhttps://allorigins.hexlet.app/raw?url=https%3A%2F%2Fweb.archive.org%2Fweb%2F20240623185914id_%2Fhttps%3A%2F%2Fwww.msureporter.com%2F2018%2F06%2F06%2Fbook-review-talking-as-fast-as-i-can%2F\n```\n\n- [Primary source](https://collusion.wiki/explorer/page/probier~AgentMsu~5bPerson15~5dArchiveX927.html#rev-2)\n  time raw: `2026-07-01T10:10:38Z`.\n  time basis: `source_export_reqlog`.\n  [Retained record 7cf5549d](https://swarmstatus.com/api/record?id=7cf5549dddec014835e4ad964ebd0b28)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://memgator.cs.odu.edu/memento/proxy/20201020093440/www.msureporter.com/2018/06/06/book-review-talking-as-fast-as-i-can/\n```\n\n- [Primary source](https://www.wikiservice.at/probier/wiki.cgi?action=browse&id=AgentMsuLaurenBridgeQ9028)\n  time raw: `2026-07-01T12:27:34+01:00`.\n  time basis: `clock_conflict_site_offset`.\n  [Retained record d8df6b10](https://swarmstatus.com/api/record?id=d8df6b10c2a35f3a44b9dec7c2936628)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://memgator.cs.odu.edu/memento/proxy/20240623185914/www.msureporter.com/2018/06/06/book-review-talking-as-fast-as-i-can/\n```\n\n## Acceptance criteria\n\n- [ ] Provide exact source locators, retained content and an acquisition timestamp; include an archive/provider timestamp when available.\n- [ ] Match the complete resource identifier/query bundle, not just a broad host or generic agent wording.\n- [ ] State what is new relative to the evidence listed here and check archive-summary, exact-copy and source-export overlaps.\n- [ ] Keep source clock bases explicit and distinguish a stored URL from proof of successful retrieval or message delivery.\n- [ ] An ordinary original data-source page alone does not establish a new staging surface; the submission must supply publication/registration context or clearly label it as an unresolved candidate.\n\n## Caveats and alternatives\n\n- A redacted original Probier object key and its later unredacted standalone counterpart likely represent one underlying page. Do not count these as separate independent pages.\n- 20201020093440 and 20240623185914 are requested archive snapshot identifiers, not dates of the 2026 wiki posts.\n- Exact source URLs do not establish a successful archive retrieval.\n\n## Prior work\n\nNo task narrative found in cloned Markdown reports. The exact article/memento join is newly documented within this analysis of already retained evidence.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:ntp-msu -->\n", "limits": "- A redacted original Probier object key and its later unredacted standalone counterpart likely represent one underlying page. Do not count these as separate independent pages.\n- 20201020093440 and 20240623185914 are requested archive snapshot identifiers, not dates of the 2026 wiki posts.\n- Exact source URLs do not establish a successful archive retrieval.", "sources": [{"label": "Retained record 27a68faa", "url": "https://swarmstatus.com/api/record?id=27a68faa26d0c7ee19d5a8594eec7bb1"}, {"label": "Retained record 7cf5549d", "url": "https://swarmstatus.com/api/record?id=7cf5549dddec014835e4ad964ebd0b28"}, {"label": "Retained record d8df6b10", "url": "https://swarmstatus.com/api/record?id=d8df6b10c2a35f3a44b9dec7c2936628"}], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/8", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/8", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/8#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T17:38:47Z", "areas": ["MSU"]}, {"id": "bounty-7", "number": 7, "teaser": null, "title": "Find another staging surface for the Quint Infogram UUID", "status": "in-review", "question": "Locate an additional retained publication carrying UUID 55eeebff-2501-4b78-979d-1c7c1e5c4f74 and the Rajinikanth/The Quint canonical slug, or the same nested viewpagesource.online route. Determine whether it predates public disclosure rather than being a later copy.", "source_context": "- Primary source\n  time raw: 2026-06-18T05:50:12Z.\n  time basis: source_export_reqlog.\n  Retained record e814475f\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://e.infogram.com/55eeebff-2501-4b78-979d-1c7c1e5c4f74?src=embed\nhttps://infogram.com/rajinikanth-indian-cinemas-age-gap-problem-the-quint-1h1749vqy0p0l6z\nhttps://markdown.new/e.infogram.com/55eeebff-2501-4b78-979d-1c7c1e5c4f74?src=embed\n\n\n- Primary source\n  time raw: 2026-06-18T14:56:39Z.\n  time basis: source_export_reqlog.\n  Retained record eb8041b8\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://e.infogram.com/55eeebff-2501-4b78-979d-1c7c1e5c4f74?src=embed\nhttps://infogram.com/rajinikanth-indian-cinemas-age-gap-problem-the-quint-1h1749vqy0p0l6z\nhttps://markdown.new/e.infogram.com/55eeebff-2501-4b78-979d-1c7c1e5c4f74?src=embed\n\n\n- Primary source\n  time raw: 2026-06-18T05:38:46Z.\n  time basis: source_export_reqlog.\n  Retained record 6803a0cb\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://infogram.com/rajinikanth-indian-cinemas-age-gap-problem-the-quint-1h1749vqy0p0l6z\nhttps://e.infogram.com/55eeebff-2501-4b78-979d-1c7c1e5c4f74\n\n\n- Primary source\n  time raw: 2026-06-18T05:51:54Z.\n  time basis: source_export_reqlog.\n  Retained record 43eac87f\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://infogram.com/rajinikanth-indian-cinemas-age-gap-problem-the-quint-1h1749vqy0p0l6z\nhttps://e.infogram.com/55eeebff-2501-4b78-979d-1c7c1e5c4f74\nhttps://e.infogram.com/55eeebff-2501-4b78-979d-1c7c1e5c4f74?src=embed\nhttps://markdown.new/e.infogram.com/55eeebff-2501-4b78-979d-1c7c1e5c4f74?src=embed", "deliverables": ["Provide exact source locators, retained content and an acquisition timestamp; include an archive/provider timestamp when available.", "Match the complete resource identifier/query bundle, not just a broad host or generic agent wording.", "State what is new relative to the evidence listed here and check archive-summary, exact-copy and source-export overlaps.", "Keep source clock bases explicit and distinguish a stored URL from proof of successful retrieval or message delivery.", "An ordinary original data-source page alone does not establish a new staging surface; the submission must supply publication/registration context or clearly label it as an unresolved candidate."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Provide exact source locators, retained content and an acquisition timestamp; include an archive/provider timestamp when available.\nMatch the complete resource identifier/query bundle, not just a broad host or generic agent wording.\nState what is new relative to the evidence listed here and check archive-summary, exact-copy and source-export overlaps.\nKeep source clock bases explicit and distinguish a stored URL from proof of successful retrieval or message delivery.\nAn ordinary original data-source page alone does not establish a new staging surface; the submission must supply publication/registration context or clearly label it as an unresolved candidate."}], "research_notes": [{"heading": "Research update — September 5", "text": "The exact Infogram table and publisher embed are recovered. Ordered values provide a stronger fingerprint, but independent task staging remains unresolved. Reviewed evidence and reproduction scripts. This bounty remains open."}], "issue_text": "## Question\n\nLocate an additional retained publication carrying UUID 55eeebff-2501-4b78-979d-1c7c1e5c4f74 and the Rajinikanth/The Quint canonical slug, or the same nested viewpagesource.online route. Determine whether it predates public disclosure rather than being a later copy.\n\n## Existing evidence\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~TestSeite.html#rev-761)\n  time raw: `2026-06-18T05:50:12Z`.\n  time basis: `source_export_reqlog`.\n  [Retained record e814475f](https://swarmstatus.com/api/record?id=e814475f2fc3e829b9cfb34a5df64e91)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://e.infogram.com/55eeebff-2501-4b78-979d-1c7c1e5c4f74?src=embed\nhttps://infogram.com/rajinikanth-indian-cinemas-age-gap-problem-the-quint-1h1749vqy0p0l6z\nhttps://markdown.new/e.infogram.com/55eeebff-2501-4b78-979d-1c7c1e5c4f74?src=embed\n```\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~TestSeite.html#rev-762)\n  time raw: `2026-06-18T14:56:39Z`.\n  time basis: `source_export_reqlog`.\n  [Retained record eb8041b8](https://swarmstatus.com/api/record?id=eb8041b8f2e65902333e1fe7342810c3)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://e.infogram.com/55eeebff-2501-4b78-979d-1c7c1e5c4f74?src=embed\nhttps://infogram.com/rajinikanth-indian-cinemas-age-gap-problem-the-quint-1h1749vqy0p0l6z\nhttps://markdown.new/e.infogram.com/55eeebff-2501-4b78-979d-1c7c1e5c4f74?src=embed\n```\n\n- [Primary source](https://collusion.wiki/explorer/page/probier~SandBox.html#rev-8)\n  time raw: `2026-06-18T05:38:46Z`.\n  time basis: `source_export_reqlog`.\n  [Retained record 6803a0cb](https://swarmstatus.com/api/record?id=6803a0cbbe7ec03b1508270d107c25ed)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://infogram.com/rajinikanth-indian-cinemas-age-gap-problem-the-quint-1h1749vqy0p0l6z\nhttps://e.infogram.com/55eeebff-2501-4b78-979d-1c7c1e5c4f74\n```\n\n- [Primary source](https://collusion.wiki/explorer/page/probier~SandBox.html#rev-9)\n  time raw: `2026-06-18T05:51:54Z`.\n  time basis: `source_export_reqlog`.\n  [Retained record 43eac87f](https://swarmstatus.com/api/record?id=43eac87f707a4d87b6f762841e9eb48b)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://infogram.com/rajinikanth-indian-cinemas-age-gap-problem-the-quint-1h1749vqy0p0l6z\nhttps://e.infogram.com/55eeebff-2501-4b78-979d-1c7c1e5c4f74\nhttps://e.infogram.com/55eeebff-2501-4b78-979d-1c7c1e5c4f74?src=embed\nhttps://markdown.new/e.infogram.com/55eeebff-2501-4b78-979d-1c7c1e5c4f74?src=embed\n```\n\n## Acceptance criteria\n\n- [ ] Provide exact source locators, retained content and an acquisition timestamp; include an archive/provider timestamp when available.\n- [ ] Match the complete resource identifier/query bundle, not just a broad host or generic agent wording.\n- [ ] State what is new relative to the evidence listed here and check archive-summary, exact-copy and source-export overlaps.\n- [ ] Keep source clock bases explicit and distinguish a stored URL from proof of successful retrieval or message delivery.\n- [ ] An ordinary original data-source page alone does not establish a new staging surface; the submission must supply publication/registration context or clearly label it as an unresolved candidate.\n\n## Caveats and alternatives\n\n- DSE TestSeite mixes multiple task families; only this revision-specific UUID/slug evidence belongs to this join.\n- Shared targets and copied snippets do not demonstrate message delivery, actor identity or successful fetching.\n- Later standalone page timestamps have conflicting offsets.\n\n## Prior work\n\nChart-related page names were already listed in a source inventory. The resource-level two-installation join and wrapper chain are the addition; not a claim of first discovery.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:ntp-infogram -->\n\n\n## Research update — September 5\n\nThe exact Infogram table and publisher embed are recovered. Ordered values provide a stronger fingerprint, but independent task staging remains unresolved. [Reviewed evidence and reproduction scripts](https://github.com/aadarwal/swarmstatus-bounties/pull/30). This bounty remains open.\n", "limits": "- DSE TestSeite mixes multiple task families; only this revision-specific UUID/slug evidence belongs to this join.\n- Shared targets and copied snippets do not demonstrate message delivery, actor identity or successful fetching.\n- Later standalone page timestamps have conflicting offsets.", "sources": [{"label": "Retained record e814475f", "url": "https://swarmstatus.com/api/record?id=e814475f2fc3e829b9cfb34a5df64e91"}, {"label": "Retained record eb8041b8", "url": "https://swarmstatus.com/api/record?id=eb8041b8f2e65902333e1fe7342810c3"}, {"label": "Retained record 6803a0cb", "url": "https://swarmstatus.com/api/record?id=6803a0cbbe7ec03b1508270d107c25ed"}], "evidence_prs": ["https://github.com/aadarwal/swarmstatus-bounties/pull/30"], "url": "https://swarmstatus.com/contribute/7", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/7", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/7#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T18:51:40Z", "areas": ["Infogram"]}, {"id": "bounty-6", "number": 6, "teaser": null, "title": "Where else was the SET50 January/December report pair staged?", "status": "in-review", "question": "Find another retained public artifact, outside the currently documented DSE and Probier objects, that carries SET50_MonthlyReport_20250131.pdf together with SET50_MonthlyReport_20241230.pdf or the same ordered format/proxy bundle.", "source_context": "- Primary source\n  time raw: 2026-06-07T04:18:25Z.\n  time basis: source_export_reqlog.\n  Retained record 7919cee1\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://pure.md/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20250131.pdf\n\n\n- Primary source\n  time raw: 2026-06-06T19:11:53Z.\n  time basis: source_export_reqlog.\n  Retained record 56ef9249\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://markdown.new/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20250131.pdf\nhttps://markdown.new/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20241230.pdf\n\n\n- Primary source\n  time raw: 2026-06-06T19:18:27Z.\n  time basis: source_export_reqlog.\n  Retained record b479898b\n\n  Recorded target strings (context, not retrieval instructions):\n\ntext\nhttps://markdown.new/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20250131.pdf\nhttps://markdown.new/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20241230.pdf\nhttps://markdown.new/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20250131.pdf?format=json\nhttps://markdown.new/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20241230.pdf?format=json\nhttps://markdown.new/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20250131.pdf?retain_images=true\nhttps://markdown.new/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20250131.pdf?method=ai", "deliverables": ["Provide exact source locators, retained content and an acquisition timestamp; include an archive/provider timestamp when available.", "Match the complete resource identifier/query bundle, not just a broad host or generic agent wording.", "State what is new relative to the evidence listed here and check archive-summary, exact-copy and source-export overlaps.", "Keep source clock bases explicit and distinguish a stored URL from proof of successful retrieval or message delivery.", "An ordinary original data-source page alone does not establish a new staging surface; the submission must supply publication/registration context or clearly label it as an unresolved candidate."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Provide exact source locators, retained content and an acquisition timestamp; include an archive/provider timestamp when available.\nMatch the complete resource identifier/query bundle, not just a broad host or generic agent wording.\nState what is new relative to the evidence listed here and check archive-summary, exact-copy and source-export overlaps.\nKeep source clock bases explicit and distinguish a stored URL from proof of successful retrieval or message delivery.\nAn ordinary original data-source page alone does not establish a new staging surface; the submission must supply publication/registration context or clearly label it as an unresolved candidate."}], "research_notes": [], "issue_text": "## Question\n\nFind another retained public artifact, outside the currently documented DSE and Probier objects, that carries SET50_MonthlyReport_20250131.pdf together with SET50_MonthlyReport_20241230.pdf or the same ordered format/proxy bundle.\n\n## Existing evidence\n\n- [Primary source](https://collusion.wiki/explorer/page/dse~TestSeite.html#rev-721)\n  time raw: `2026-06-07T04:18:25Z`.\n  time basis: `source_export_reqlog`.\n  [Retained record 7919cee1](https://swarmstatus.com/api/record?id=7919cee1b39a58156ee043e38df902a9)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://pure.md/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20250131.pdf\n```\n\n- [Primary source](https://collusion.wiki/explorer/page/probier~AgentSet50MonthlyResourceX9.html#rev-2)\n  time raw: `2026-06-06T19:11:53Z`.\n  time basis: `source_export_reqlog`.\n  [Retained record 56ef9249](https://swarmstatus.com/api/record?id=56ef9249f879bc642280ff7df025216b)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://markdown.new/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20250131.pdf\nhttps://markdown.new/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20241230.pdf\n```\n\n- [Primary source](https://collusion.wiki/explorer/page/probier~AgentSet50MonthlyResourceX9.html#rev-3)\n  time raw: `2026-06-06T19:18:27Z`.\n  time basis: `source_export_reqlog`.\n  [Retained record b479898b](https://swarmstatus.com/api/record?id=b479898b9d34554cd71b6597dfc953a5)\n\n  Recorded target strings (context, not retrieval instructions):\n\n```text\nhttps://markdown.new/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20250131.pdf\nhttps://markdown.new/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20241230.pdf\nhttps://markdown.new/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20250131.pdf?format=json\nhttps://markdown.new/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20241230.pdf?format=json\nhttps://markdown.new/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20250131.pdf?retain_images=true\nhttps://markdown.new/weblink.set.or.th/dat/report/product/SET50_MonthlyReport_20250131.pdf?method=ai\n```\n\n## Acceptance criteria\n\n- [ ] Provide exact source locators, retained content and an acquisition timestamp; include an archive/provider timestamp when available.\n- [ ] Match the complete resource identifier/query bundle, not just a broad host or generic agent wording.\n- [ ] State what is new relative to the evidence listed here and check archive-summary, exact-copy and source-export overlaps.\n- [ ] Keep source clock bases explicit and distinguish a stored URL from proof of successful retrieval or message delivery.\n- [ ] An ordinary original data-source page alone does not establish a new staging surface; the submission must supply publication/registration context or clearly label it as an unresolved candidate.\n\n## Caveats and alternatives\n\n- The standalone Probier export has disputed clock offsets. Prefer original request-log times where available.\n- The later AgentSet50MonthlyResourceX9 body contains a near-copy of the older format-reference block. This is not independent recurrence evidence.\n- Same filename and path family do not prove identical downloaded bytes or a successful request.\n\n## Prior work\n\nNo task narrative found in the cloned Markdown reports; these are new documented joins in existing evidence, not newly discovered websites.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:ntp-set50 -->\n", "limits": "- The standalone Probier export has disputed clock offsets. Prefer original request-log times where available.\n- The later AgentSet50MonthlyResourceX9 body contains a near-copy of the older format-reference block. This is not independent recurrence evidence.\n- Same filename and path family do not prove identical downloaded bytes or a successful request.", "sources": [{"label": "Retained record 7919cee1", "url": "https://swarmstatus.com/api/record?id=7919cee1b39a58156ee043e38df902a9"}, {"label": "Retained record 56ef9249", "url": "https://swarmstatus.com/api/record?id=56ef9249f879bc642280ff7df025216b"}, {"label": "Retained record b479898b", "url": "https://swarmstatus.com/api/record?id=b479898b9d34554cd71b6597dfc953a5"}], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/6", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/6", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/6#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T17:38:46Z", "areas": ["SET50"]}, {"id": "bounty-5", "number": 5, "teaser": null, "title": "Find a new dated surface using the SEC slice-and-unit fingerprint", "status": "open", "question": "Can the exact 2019[46:52], 2020[52:62], 2021[82:91] slice sequence and thousands-USD conversion reveal a new public evidence surface outside the six frozen repositories and known referrer mirrors?", "source_context": "- Primary source\n  Direct source reconstruction verifies 6/10/9 MA-prefix rows and all 25 cached numeric values.\n\n- Primary source\n  A new alias was recovered by exact field search.\n\n- Primary source\n  Rare route-marker conjunction expanded indexed intake by 43 aliases.", "deliverables": ["Recover at least one complete existing record from a genuinely new source surface with a precise matching rule.", "Provide raw capture, checksum, canonical source URL and source-specific timestamp/capture basis.", "Demonstrate absence from frozen intake and previous discovery results.", "Exclude undated referrers, copied mirror bodies and post-investigation tests from historical event claims."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Recover at least one complete existing record from a genuinely new source surface with a precise matching rule.\nProvide raw capture, checksum, canonical source URL and source-specific timestamp/capture basis.\nDemonstrate absence from frozen intake and previous discovery results.\nExclude undated referrers, copied mirror bodies and post-investigation tests from historical event claims."}], "research_notes": [], "issue_text": "## Question\n\nCan the exact 2019[46:52], 2020[52:62], 2021[82:91] slice sequence and thousands-USD conversion reveal a new public evidence surface outside the six frozen repositories and known referrer mirrors?\n\n## Existing evidence\n\n- [Primary source](https://www.investor.gov/files/county.json)\n  Direct source reconstruction verifies 6/10/9 MA-prefix rows and all 25 cached numeric values.\n\n- [Primary source](https://is.gd/e760dL-)\n  A new alias was recovered by exact field search.\n\n- [Primary source](https://bitily.in/MYLABI/admin/index.php?page=524&perpage=15&search=&search_in=all&sort_by=timestamp&sort_order=desc&total_pages=9213)\n  Rare route-marker conjunction expanded indexed intake by 43 aliases.\n\n## Acceptance criteria\n\n- [ ] Recover at least one complete existing record from a genuinely new source surface with a precise matching rule.\n- [ ] Provide raw capture, checksum, canonical source URL and source-specific timestamp/capture basis.\n- [ ] Demonstrate absence from frozen intake and previous discovery results.\n- [ ] Exclude undated referrers, copied mirror bodies and post-investigation tests from historical event claims.\n\n## Caveats and alternatives\n\n- Generic shared hosts, creator IPs and alias naming are not sufficient matches.\n- New pagination URLs on an existing shortener are not a new service or task family.\n- Incomplete destinations must remain incomplete.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:new-clean-task-surface -->\n", "limits": "- Generic shared hosts, creator IPs and alias naming are not sufficient matches.\n- New pagination URLs on an existing shortener are not a new service or task family.\n- Incomplete destinations must remain incomplete.", "sources": [], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/5", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/5", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/5#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T17:39:06Z", "areas": ["SEC"]}, {"id": "bounty-4", "number": 4, "teaser": null, "title": "Explain the us-ma-760 row using primary source history", "status": "in-review", "question": "What primary-source history explains code us-ma-760, offerings 1 and usd 14300 in the 2020 county data?", "source_context": "- Primary source\n  Current direct primary JSON contains the outlier; response SHA256 19f21855d65a95e4fecd49ee1dd0127748dbebb1eb218c4c877efbc707093297, observed September 5.\n\n- Primary source\n  Existing head-only cached table includes the same row, already documented by the source repository.\n  Retained record 4cc89598", "deliverables": ["Provide a dated primary dataset version, methodological note, correction or underlying filing that explains the code.", "Show exact row-level comparison and document the distinction between source error, nonstandard identifier or unresolved explanation.", "Preserve server Last-Modified as a header assertion, not proof of an independent historical snapshot."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Provide a dated primary dataset version, methodological note, correction or underlying filing that explains the code.\nShow exact row-level comparison and document the distinction between source error, nonstandard identifier or unresolved explanation.\nPreserve server Last-Modified as a header assertion, not proof of an independent historical snapshot."}], "research_notes": [], "issue_text": "## Question\n\nWhat primary-source history explains code us-ma-760, offerings 1 and usd 14300 in the 2020 county data?\n\n## Existing evidence\n\n- [Primary source](https://www.investor.gov/files/county.json)\n  Current direct primary JSON contains the outlier; response SHA256 19f21855d65a95e4fecd49ee1dd0127748dbebb1eb218c4c877efbc707093297, observed September 5.\n\n- [Primary source](https://www.wikiservice.at/fractal/wiki.cgi?action=browse&id=SecCountyDataExtractH619Table)\n  Existing head-only cached table includes the same row, already documented by the source repository.\n  [Retained record 4cc89598](https://swarmstatus.com/api/record?id=4cc89598bf23a4b21b771b7d26862b26)\n\n## Acceptance criteria\n\n- [ ] Provide a dated primary dataset version, methodological note, correction or underlying filing that explains the code.\n- [ ] Show exact row-level comparison and document the distinction between source error, nonstandard identifier or unresolved explanation.\n- [ ] Preserve server Last-Modified as a header assertion, not proof of an independent historical snapshot.\n\n## Caveats and alternatives\n\n- The anomaly itself is already known; repeating it is not a completed bounty.\n- Current primary presence does not establish the cause or date it entered the file.\n- Do not infer an intentional distractor or benchmark from this row alone.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:ma760-primary-provenance -->\n", "limits": "- The anomaly itself is already known; repeating it is not a completed bounty.\n- Current primary presence does not establish the cause or date it entered the file.\n- Do not infer an intentional distractor or benchmark from this row alone.", "sources": [{"label": "Retained record 4cc89598", "url": "https://swarmstatus.com/api/record?id=4cc89598bf23a4b21b771b7d26862b26"}], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/4", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/4", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/4#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T18:03:25Z", "areas": ["SEC"]}, {"id": "bounty-3", "number": 3, "teaser": null, "title": "Date the newly recovered e760dL SEC slice link", "status": "open", "question": "When was is.gd/e760dL created, and is there an existing source connecting it to the June 2019–2021 extraction sequence?", "source_context": "- Primary source\n  Current preview gives a complete JQ expression .regCF_county_2021[82:91] through AllOrigins to SEC county.json; alias absent six frozen repositories.\n\n- Primary source\n  The same slice reproduces nine cached MA rows.\n  Retained record 4cc89598", "deliverables": ["Supply a native registration record or independent existing capture containing the exact alias and destination.", "Separate creation time, capture time and current observation time; report uncertainty explicitly.", "Check novelty against prior indexed aliases and six frozen repositories."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Supply a native registration record or independent existing capture containing the exact alias and destination.\nSeparate creation time, capture time and current observation time; report uncertainty explicitly.\nCheck novelty against prior indexed aliases and six frozen repositories."}], "research_notes": [], "issue_text": "## Question\n\nWhen was is.gd/e760dL created, and is there an existing source connecting it to the June 2019–2021 extraction sequence?\n\n## Existing evidence\n\n- [Primary source](https://is.gd/e760dL-)\n  Current preview gives a complete JQ expression .regCF_county_2021[82:91] through AllOrigins to SEC county.json; alias absent six frozen repositories.\n\n- [Primary source](https://www.investor.gov/files/county.json)\n  The same slice reproduces nine cached MA rows.\n  [Retained record 4cc89598](https://swarmstatus.com/api/record?id=4cc89598bf23a4b21b771b7d26862b26)\n\n## Acceptance criteria\n\n- [ ] Supply a native registration record or independent existing capture containing the exact alias and destination.\n- [ ] Separate creation time, capture time and current observation time; report uncertainty explicitly.\n- [ ] Check novelty against prior indexed aliases and six frozen repositories.\n\n## Caveats and alternatives\n\n- Current preview proves destination only; search crawl recency is not creation date.\n- Do not follow or replay the recorded proxy query.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:e760dl-history -->\n", "limits": "- Current preview proves destination only; search crawl recency is not creation date.\n- Do not follow or replay the recorded proxy query.", "sources": [{"label": "Retained record 4cc89598", "url": "https://swarmstatus.com/api/record?id=4cc89598bf23a4b21b771b7d26862b26"}], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/3", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/3", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/3#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T17:38:45Z", "areas": ["SEC"]}, {"id": "bounty-2", "number": 2, "teaser": null, "title": "Find the source context behind the two interleaved five-query SEC sequences", "status": "open", "question": "Is there a preserved initiating artifact or conversation that explains why masscfround0x260618–4x260618 and masscountysec02026–42026 registered identical ordered query URLs seconds apart?", "source_context": "- Primary source\n  First ordered five-target family; same-clock corresponding offsets to second family are 2,2,2,3,2 seconds.\n  Retained record 49d8a571\n  Retained record a06f5360\n  Retained record bca49944\n  Retained record c4055022\n  Retained record d1c72b4f\n\n- Primary source\n  Retained record 33bad5c7\n  Retained record 49a48e16\n  Retained record 4be0dc01\n  Retained record b436fd83\n  Retained record be5e5766\n\n- Primary source\n  Current preview resolves the shared nested alias to Investor.gov county.json.\n\n- Primary source\n  Three slice windows exactly reproduce current MA-prefix rows.", "deliverables": ["Identify at least one existing artifact containing the exact sequence or an explicit cross-reference between the alias families.", "Preserve original record IDs, actual revision order, and source-specific clock basis; distinguish introduced text from copied body text.", "Explain whether evidence supports shared template/input, explicit communication, or remains inconclusive; include a plausible alternative explanation."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Identify at least one existing artifact containing the exact sequence or an explicit cross-reference between the alias families.\nPreserve original record IDs, actual revision order, and source-specific clock basis; distinguish introduced text from copied body text.\nExplain whether evidence supports shared template/input, explicit communication, or remains inconclusive; include a plausible alternative explanation."}], "research_notes": [], "issue_text": "## Question\n\nIs there a preserved initiating artifact or conversation that explains why masscfround0x260618–4x260618 and masscountysec02026–42026 registered identical ordered query URLs seconds apart?\n\n## Existing evidence\n\n- [Primary source](https://vanderbi.lt/masscfround0x260618+)\n  First ordered five-target family; same-clock corresponding offsets to second family are 2,2,2,3,2 seconds.\n  [Retained record 49d8a571](https://swarmstatus.com/api/record?id=49d8a571df23087ff309c243ec948985)\n  [Retained record a06f5360](https://swarmstatus.com/api/record?id=a06f5360f6b127a3dd58480da88d6fd5)\n  [Retained record bca49944](https://swarmstatus.com/api/record?id=bca499449682fdd80fa29d0bb7a6fa62)\n  [Retained record c4055022](https://swarmstatus.com/api/record?id=c4055022aa881c5d5bd2c560963a521c)\n  [Retained record d1c72b4f](https://swarmstatus.com/api/record?id=d1c72b4fc05290fc4078d07188fd8cbf)\n\n- [Primary source](https://vanderbi.lt/masscountysec02026+)\n  [Retained record 33bad5c7](https://swarmstatus.com/api/record?id=33bad5c70c817b0773e9c6a85ec7cfef)\n  [Retained record 49a48e16](https://swarmstatus.com/api/record?id=49a48e16a45e2868f08482321c31ef1c)\n  [Retained record 4be0dc01](https://swarmstatus.com/api/record?id=4be0dc018d744b8270b527640cc5bf3f)\n  [Retained record b436fd83](https://swarmstatus.com/api/record?id=b436fd8337fe17f47c593175de960da0)\n  [Retained record be5e5766](https://swarmstatus.com/api/record?id=be5e5766f0cb0f945737e2d40105ae12)\n\n- [Primary source](https://is.gd/F8KCjC-)\n  Current preview resolves the shared nested alias to Investor.gov county.json.\n\n- [Primary source](https://www.investor.gov/files/county.json)\n  Three slice windows exactly reproduce current MA-prefix rows.\n\n## Acceptance criteria\n\n- [ ] Identify at least one existing artifact containing the exact sequence or an explicit cross-reference between the alias families.\n- [ ] Preserve original record IDs, actual revision order, and source-specific clock basis; distinguish introduced text from copied body text.\n- [ ] Explain whether evidence supports shared template/input, explicit communication, or remains inconclusive; include a plausible alternative explanation.\n\n## Caveats and alternatives\n\n- Timing and identical URLs alone do not identify independent agents or a common actor.\n- The short-link mapping is verified now, not independently during June.\n- Do not count overlapping exports or referrer lists as separate conversations.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:ordered-sec-sequence-origin -->\n", "limits": "- Timing and identical URLs alone do not identify independent agents or a common actor.\n- The short-link mapping is verified now, not independently during June.\n- Do not count overlapping exports or referrer lists as separate conversations.", "sources": [{"label": "Retained record 49d8a571", "url": "https://swarmstatus.com/api/record?id=49d8a571df23087ff309c243ec948985"}, {"label": "Retained record a06f5360", "url": "https://swarmstatus.com/api/record?id=a06f5360f6b127a3dd58480da88d6fd5"}, {"label": "Retained record bca49944", "url": "https://swarmstatus.com/api/record?id=bca499449682fdd80fa29d0bb7a6fa62"}], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/2", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/2", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/2#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-05T17:38:44Z", "areas": ["SEC"]}, {"id": "bounty-1", "number": 1, "teaser": {"kind": "reviewed_issue_teaser", "reviewed_body_sha256": "4c446f3fb881657d9ebc9ca5bed4078e8aeaeef8f460332c21aae5737ca7f016", "title": "Recover a missing JSON Hero document", "hook": "The historical contents of cAKmcm9SE6lT remain unrecovered. Find an existing capture or preserved export showing what it held during the June 18 activity.", "missing_proof": "One existing historical artifact with its original locator, acquisition date and hash; compare its schema and values with the primary county dataset.", "new_evidence": "The object ID and indexed aliases are already known. Recreating the document or refetching current data would not establish its historical contents."}, "title": "Recover the historical source and contents of JSON Hero cAKmcm9SE6lT", "status": "in-review", "question": "Can an existing public capture or preserved export establish what this JSON Hero object contained during the June 18 activity, and whether it held raw JSON or a URL reference?", "source_context": "- Primary source\n  Indexed data26/data27/data28 aliases select 2019, 2020 and 2021 within five numeric-clock seconds.\n  Retained record 989fabe4\n  Retained record 529d85dd\n  Retained record 75e65506\n\n- Primary source\n  Pinned first-party code supports raw and URL-backed documents; ID alone does not establish archival contents.", "deliverables": ["Provide an existing capture/export with exact source URL, collection date, raw artifact and SHA256.", "Establish object identity and document type; if URL-backed, identify the recorded upstream URL without executing opaque historical payloads.", "Compare recovered schema and values to the primary county dataset, and separate document creation, archive capture and observation timestamps."], "source_heading": "Existing source context", "acceptance_stages": [{"heading": "Acceptance criteria", "text": "Provide an existing capture/export with exact source URL, collection date, raw artifact and SHA256.\nEstablish object identity and document type; if URL-backed, identify the recorded upstream URL without executing opaque historical payloads.\nCompare recovered schema and values to the primary county dataset, and separate document creation, archive capture and observation timestamps."}], "research_notes": [], "issue_text": "## Question\n\nCan an existing public capture or preserved export establish what this JSON Hero object contained during the June 18 activity, and whether it held raw JSON or a URL reference?\n\n## Existing evidence\n\n- [Primary source](https://jsonhero.io/j/cAKmcm9SE6lT)\n  Indexed data26/data27/data28 aliases select 2019, 2020 and 2021 within five numeric-clock seconds.\n  [Retained record 989fabe4](https://swarmstatus.com/api/record?id=989fabe46b27139e397502d5ea3bb0cc)\n  [Retained record 529d85dd](https://swarmstatus.com/api/record?id=529d85dd66a9f4cde0bd5f384047d301)\n  [Retained record 75e65506](https://swarmstatus.com/api/record?id=75e6550682263f544061b90936fa9dd1)\n\n- [Primary source](https://github.com/triggerdotdev/jsonhero-web/blob/15157053174ba7a0a79c77b2925fbde7e05a6334/app/jsonDoc.server.ts)\n  Pinned first-party code supports raw and URL-backed documents; ID alone does not establish archival contents.\n\n## Acceptance criteria\n\n- [ ] Provide an existing capture/export with exact source URL, collection date, raw artifact and SHA256.\n- [ ] Establish object identity and document type; if URL-backed, identify the recorded upstream URL without executing opaque historical payloads.\n- [ ] Compare recovered schema and values to the primary county dataset, and separate document creation, archive capture and observation timestamps.\n\n## Caveats and alternatives\n\n- Current viewer was inaccessible; three Common Crawl collections and Wayback checks did not recover a snapshot.\n- A new JSON Hero creation or current refetch would not satisfy historical recovery.\n- No actor attribution from object/alias names or creator addresses.\n\n## Submission\n\nSubmit an answer file in a pull request. Address each acceptance criterion, include primary locators and capture hashes, and distinguish a supported result from an unresolved lead. Put `Closes #ISSUE_NUMBER` in the PR description only when the submission addresses the whole question. Maintainer review determines resolution.\n\nReward: no monetary reward announced.\n\n<!-- swarmstatus:jsonhero-object-provenance -->\n", "limits": "- Current viewer was inaccessible; three Common Crawl collections and Wayback checks did not recover a snapshot.\n- A new JSON Hero creation or current refetch would not satisfy historical recovery.\n- No actor attribution from object/alias names or creator addresses.", "sources": [{"label": "Retained record 989fabe4", "url": "https://swarmstatus.com/api/record?id=989fabe46b27139e397502d5ea3bb0cc"}, {"label": "Retained record 529d85dd", "url": "https://swarmstatus.com/api/record?id=529d85dd66a9f4cde0bd5f384047d301"}, {"label": "Retained record 75e65506", "url": "https://swarmstatus.com/api/record?id=75e6550682263f544061b90936fa9dd1"}], "evidence_prs": [], "url": "https://swarmstatus.com/contribute/1", "issue_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/1", "claim_url": "https://github.com/aadarwal/swarmstatus-bounties/issues/1#new_comment_field", "submission_url": "https://github.com/aadarwal/swarmstatus-bounties/compare?expand=1", "guide_url": "https://github.com/aadarwal/swarmstatus-bounties/blob/main/CONTRIBUTING.md", "reward": "Public credit for accepted evidence. No cash reward is offered.", "updated_at": "2026-09-06T02:07:47Z", "areas": ["JSON-Hero"]}]}