Kui Ren, Hui Xue, Zhixuan Chu, Licheng Pan, Jiexi Liu, Yunsheng Lu, Haozhe Feng, Jialing Tao
3 of 5 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (3 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 3 have no contract verdict; 0 failures of our instrument; 2 no recorded run), measured 2026-11-22; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.
"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2602.04893.json · badge: /api/ran/2602.04893.svg
Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.
| Repository | Role | Ran |
|---|---|---|
| Master-PLC/Causal-Analyst | community Papers with Code archive |
3 ran · 2 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| CausalAnalystOutputWithPast | Ran ran on a synthesized input · constructed an object; no result was computed |
Master-PLC/Causal-Analyst/src/llamafactory/custom/qwen2causal/modeling_qwen2custom.py code served (permissive licence) · get_code("3a1da1d05f23b202") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned an instance of its own class, CausalAnalystOutputWithPast: the run constructed the object and did not call it, so no result was computed. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| DAGGNN_MLPDecoder | Ran ran on a synthesized input · constructed an object; no result was computed |
Master-PLC/Causal-Analyst/src/llamafactory/custom/qwen2causal/modeling_qwen2custom.py code served (permissive licence) · get_code("5f86e84a8bd6d2d5") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned an instance of its own class, DAGGNN_MLPDecoder: the run constructed the object and did not call it, so no result was computed. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| DAGGNN_MLPEncoder | Ran ran on a synthesized input · constructed an object; no result was computed |
Master-PLC/Causal-Analyst/src/llamafactory/custom/qwen2causal/modeling_qwen2custom.py code served (permissive licence) · get_code("7e423932593696a9") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned an instance of its own class, DAGGNN_MLPEncoder: the run constructed the object and did not call it, so no result was computed. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| DAGGNN | Not yet run unverified (harvested, no recorded run) |
Master-PLC/Causal-Analyst/src/llamafactory/custom/qwen2causal/modeling_qwen2custom.py code served (permissive licence) · get_code("aee6beb843bd077e") How it ranno invocation recorded. |
| Qwen2Custom | Not yet run unverified (harvested, no recorded run) |
Master-PLC/Causal-Analyst/src/llamafactory/custom/qwen2causal/modeling_qwen2custom.py code served (permissive licence) · get_code("beb993005a8f2ad3") How it ranno invocation recorded. |
Of 5 samples lifted from this paper's linked repositories, 5 carry a function identity and 0 do not. Of the 5 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 5 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).
Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.
Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
Uncovering the mechanisms behind "jailbreaks" in large language models (LLMs) is crucial for enhancing their safety and reliability, yet these mechanisms remain poorly understood. Existing studies predominantly analyze jailbreak prompts by probing latent representations, often overlooking the causal relationships between interpretable prompt features and jailbreak occurrences. In this work, we propose Causal Analyst, a framework that integrates LLMs into data-driven causal discovery to identify the direct causes of jailbreaks and leverage them for both attack and defense. We introduce a comprehensive dataset comprising 35k jailbreak attempts across seven LLMs, systematically constructed from 100 attack templates and 50 harmful queries, annotated with 37 meticulously designed human-readable prompt features. By jointly training LLM-based prompt encoding and GNN-based causal graph learning, we reconstruct causal pathways linking prompt features to jailbreak responses. Our analysis reveals that specific features, such as "Positive Character" and "Number of Task Steps", act as direct causal drivers of jailbreaks. We demonstrate the practical utility of these insights through two applications: ❶ a Jailbreaking Enhancer that targets identified causal features to significantly boost attack success rates on public benchmarks, and ❷ a Guardrail Advisor that utilizes the learned causal graph to extract true malicious intent from obfuscated queries. Extensive experiments, including baseline comparisons and causal structure validation, confirm the robustness of our causal analysis and its superiority over non-causal approaches. Our results suggest that analyzing jailbreak features from a causal perspective is an effective and interpretable approach for improving LLM reliability. Our code is available at https://github.com/Master-PLC/Causal-Analyst. Warning: Some contents may include disturbing contents.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2602.04893")
get_code_for_paper("2602.04893")
have("2602.04893")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2602.04893.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2602.04893)
Connect an agent — have() is free.