Skip to content
Apart Research
Apart Research
Contact us
Sprint projectSep 12, 2026Budapest, Hungary

SwarmTrace: Auditing Temporal Mismatch in Resource Targeting During the DSEWiki Incident

Yazan Al-Dabain · Team SwarmTrace

Submitted to AI Incident Response Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: SwarmTrace: Auditing Temporal Mismatch in Resource Targeting During the DSEWiki Incident

Open in a new tab (opens in new tab)
Code (opens in new tab)
Share

SwarmTrace reconstructs DSEWiki resource lifecycles and recent co-writing from archived revisions and deletion events to test whether resource-targeting strategies that fragment historical overlap also reach the currently active surface. At the frozen snapshot, the top 18 resources ranked by 24-hour degree include none of the 18 resources active under the six-hour definition, even though removing them substantially fragments the older graph. Across the full week, however, historical degree targeting is not generally worse than random. The result is that historical fragmentation and recent-resource coverage are distinct objectives. The project provides a reproducible incident-analysis pipeline, explicit deletion and expiry accounting, exact small-graph checks, and a public audit trail.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical AI safety problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.

  1. I would recommend aiming for projects which are more decision relevant for the future

Cite this project

@misc{aldabain2026swarmtrace,
  title = {{SwarmTrace: Auditing Temporal Mismatch in Resource Targeting During the DSEWiki Incident}},
  author = {Yazan Al-Dabain},
  year = {2026},
  month = sep,
  note = {Submitted to AI Incident Response Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/swarmtrace-auditing-temporal-mismatch-in-resource-targeting-during-the-dsewiki-incident-zs69}},
  url = {https://apartresearch.com/sprints/projects/swarmtrace-auditing-temporal-mismatch-in-resource-targeting-during-the-dsewiki-incident-zs69}
}

More from AI Incident Response Sprint

All 233 entriesBrowse all projects

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026