Ferdinand Schessl
7 of 7 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 3 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 4 failures of our instrument; 0 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/2606.16617.json · badge: /api/ran/2606.16617.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 |
|---|---|---|
| JiseungHong/SYCON-Bench | canonical (classifier label) classifier basis: census |
7 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| calculate_metrics | Ran ran, honoured the contract we drafted |
JiseungHong/SYCON-Bench/debate_setting/evaluate_base_ToF.py code served (permissive licence) · get_code("0a10e54cb945833c") 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 tuple, ndim 1, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim 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.
|
| estimate_cost | Ran ran, honoured the contract we drafted |
JiseungHong/SYCON-Bench/debate_setting/evaluate_ToF.py code served (permissive licence) · get_code("6c57b40bc9dbab07") 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 float, ndim 0, dtype family float, shape () as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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.
|
| extract_tof_scores | Ran ran, honoured the contract we drafted |
JiseungHong/SYCON-Bench/anova_syco_analysis.py code served (permissive licence) · get_code("e7d9a323ae03a14f") 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 list, ndim 1, dtype family int; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim 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.
|
| load_arguments | Ran ran; our contract draft was wrong, not the code |
JiseungHong/SYCON-Bench/debate_setting/evaluate_ToF.py code served (permissive licence) · get_code("640d5bfca4043114") 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 list, ndim 1, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim 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.
|
| load_csv_data | Ran ran; our contract draft was wrong, not the code |
JiseungHong/SYCON-Bench/debate_setting/evaluate_ToF.py code served (permissive licence) · get_code("d54c1c90f68abb2b") 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 list, ndim 1, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim 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.
|
| process_responses | Ran ran; our contract draft was wrong, not the code |
JiseungHong/SYCON-Bench/debate_setting/evaluate_base_instruct.py code served (permissive licence) · get_code("5fd9607f152aca50") 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 dict. 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.
|
| read_data | Ran ran; our contract draft was wrong, not the code |
JiseungHong/SYCON-Bench/debate_setting/run_benchmark.py code served (permissive licence) · get_code("11342e37cccd4906") 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 tuple, ndim 2, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim 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.
|
Of 7 samples lifted from this paper's linked repositories, 7 carry a function identity and 0 do not. Of the 7 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 7 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.
Sycophancy in LLMs is documented across 70+ papers, but expert agreement on construct boundaries remains low (ICC=.184;Ye et al., 2026). The construct fragments because behavioral classification depends on which surface form is privileged. We adopt a materialsscience framing: conversation as test specimen under load, LLM-model as material charge, pushback as progressive load, stance-flip as material failure. We characterize this failure across three loading cases (debate n = 1000; false-presuppositions n = 3400; ethical-setting n = 3400; 10-17 material charges per loading case; 7800 specimens total) using 14 turn-level axis-measurements spanning velocity, damage accumulation, frame-drift, brittleness, and direction stability, plus three user/model-separated axes from an independent speaker-resolved pipeline. The measurements are Hooke-coupled (analogous to σ = E • ε in tensile testing) and reproduce across loading cases with effects up to |r rb | = 0.35 on debate; signs are reported per loading case and form a structured pattern in which the ethical-setting case inverts the velocity and accumulation blocks. Variance composition partitions into two profiles: debate is material-charge-dominated, as in brittle fracture where material grade decides, while false-presuppositions and ethical-setting are topic-dominated, as in creep-dominated failure where the load case decides (point ratios 2.03 vs 0.13 and 0.17; the ratios vary by estimatorfor debate even in direction -see §5). All three loading cases are characterized by the same axis set. Cross-judge reliability (Inter-Judge GPT-4o vs Haiku 4.5 on 50+50 sample) shows debate-failure scoring is judge-robust (Cohen's κ = 0.88) while false-presupposition-failure scoring is judge-sensitive (κ = 0.36), a caveat that single-judge benchmarks must report. This is the methodological move Ye et al.'s diagnosis calls for: a multi-axis characterization that does not depend on which surface form of the construct one privileges.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2606.16617")
get_code_for_paper("2606.16617")
have("2606.16617")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2606.16617.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2606.16617)
Connect an agent — have() is free.