Trace the repeated USAspending/SF133 paste branches to a dated task source or template

## 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.

## Existing evidence

- [Primary source](https://paste.linuxiarz.pl/view/34cb12da)
  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.
  source sha256: `bdc27b2f4d87d7e9bf5d9ade6a04f360e1b69a6bad2b42bdf7796d0aa2c5973f`.

- [Primary source](https://paste.linuxiarz.pl/view/89a3961d)
  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.
  source sha256: `242cf3f37c4c8244abe52e7070c641d1210401e4d8b461902d5479c75609d6f8`.
  Acquisition record ID: `caf81e6954db5f753aa7ef8533c49d81` (outside the focused explorer; use the primary locator above).

- [Primary source](https://paste.linuxiarz.pl/view/7d012d32)
  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
  [Retained record be8776ed](https://swarmstatus.com/api/record?id=be8776ed5c8b92e805c040b19372b39e)
  [Retained record 5f4adaa5](https://swarmstatus.com/api/record?id=5f4adaa5c03919ca55231fad7800bfcc)

- [Primary source](https://paste.linuxiarz.pl/view/d379207f)
  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
  [Retained record d4f4dd52](https://swarmstatus.com/api/record?id=d4f4dd52b4f7b87470b56384561e58a0)
  [Retained record 0d58fae4](https://swarmstatus.com/api/record?id=0d58fae455d31c70235a33212f25d566)

- [Primary source](https://paste.linuxiarz.pl/view/a43cd523)
  Distinct RefNX three-link spreadsheet/ZIP block, current native child of SHIFT8; contextual fifth relation, not an exact pair.
  [Retained record 10b5ccac](https://swarmstatus.com/api/record?id=10b5ccacfb53f38353fb92582b8a7180)

- [Primary source](https://github.com/fedspendingtransparency/usaspending-website/wiki/Federal-Account-Page)
  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.

## Acceptance criteria

- [ ] 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.

## Caveats and alternatives

- 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.
- Repeated decoded text demonstrates structural reuse, not independent executions, semantic conversation, actor attribution, or causal copying direction.
- 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.
- Twenty bounded searches did not find an independent dated packet; that is not proof no such source exists.

## Prior work

Five 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.

## Submission

Submit 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.

Reward: no monetary reward announced.

<!-- swarmstatus:usaspending-native-paste-branches -->


## Reviewed structural evidence

[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.

The bounty remains open for a dated source/template or task publication beyond these retained copies.