Germany, Robert Mullins, Arduin Findeis, Timo Kaufmann, Munich Munich
6 of 10 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; 3 failures of our instrument; 4 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/2406.06560.json · badge: /api/ran/2406.06560.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 |
|---|---|---|
| rdnfn/icai | canonical (classifier label) classifier basis: classifier_2025 |
6 ran · 4 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| AlpacaEvalAnnotatorConfig | Ran ran on a synthesized input · constructed an object; no result was computed |
rdnfn/icai/src/inverse_cai/algorithm/proposal.py code served (permissive licence) · get_code("fad9c323896389d9") 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, AlpacaEvalAnnotatorConfig: 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.
|
| AnnotatorConfig | Ran ran on a synthesized input · constructed an object; no result was computed |
rdnfn/icai/src/inverse_cai/algorithm/proposal.py code served (permissive licence) · get_code("3c4ba0e3b3c33583") 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, AnnotatorConfig: 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.
|
| FunctionAnnotatorConfig | Ran ran on a synthesized input · constructed an object; no result was computed |
rdnfn/icai/src/inverse_cai/algorithm/proposal.py code served (permissive licence) · get_code("59a4167a57113c68") 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, FunctionAnnotatorConfig: 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.
|
| clean_principle_str | Ran ran; our contract draft was wrong, not the code |
rdnfn/icai/src/inverse_cai/algorithm/proposal.py code served (permissive licence) · get_code("cf0ddec0199e9097") 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 str. 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.
|
| get_preferred_text | Ran ran; our contract draft was wrong, not the code |
rdnfn/icai/src/inverse_cai/algorithm/proposal.py code served (permissive licence) · get_code("56041d176337cc61") 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 str. 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.
|
| get_rejected_text | Ran ran; our contract draft was wrong, not the code |
rdnfn/icai/src/inverse_cai/algorithm/proposal.py code served (permissive licence) · get_code("d1252752dc993a17") 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 str. 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.
|
| ExpConfig | Not yet run unverified (harvested, no recorded run) |
rdnfn/icai/src/inverse_cai/algorithm/proposal.py code served (permissive licence) · get_code("2417283750496843") How it ranno invocation recorded. |
| PromptConfig | Not yet run unverified (harvested, no recorded run) |
rdnfn/icai/src/inverse_cai/algorithm/proposal.py code served (permissive licence) · get_code("d93fe6772a75b268") How it ranno invocation recorded. |
| generate_principles_from_feedback | Not yet run unverified (harvested, no recorded run) |
rdnfn/icai/src/inverse_cai/algorithm/proposal.py code served (permissive licence) · get_code("7aeeac243f7d0d42") How it ranno invocation recorded. |
| generate_principles_from_single_ranking | Not yet run unverified (harvested, no recorded run) |
rdnfn/icai/src/inverse_cai/algorithm/proposal.py code served (permissive licence) · get_code("7e33551b08a8b93b") How it ranno invocation recorded. |
Of 10 samples lifted from this paper's linked repositories, 10 carry a function identity and 0 do not. Of the 10 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 10 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.
Feedback data is widely used for fine-tuning and evaluating state-of-the-art AI models. Pairwise text preferences, where human or AI annotators select the "better" of two options, are particularly common. Such preferences are used to train (reward) models or to rank models with aggregate statistics. For many applications it is desirable to understand annotator preferences in addition to modelling them -not least because extensive prior work has shown various unintended biases in preference datasets. Yet, preference datasets remain challenging to interpret. Neither black-box reward models nor statistics can answer why one text is preferred over another. Manual interpretation of the numerous (long) response pairs is usually equally infeasible. In this paper, we introduce the Inverse Constitutional AI (ICAI) problem, formulating the interpretation of pairwise text preference data as a compression task. In constitutional AI, a set of principles (a constitution) is used to provide feedback and fine-tune AI models. ICAI inverts this process: given a feedback dataset, we aim to extract a constitution that best enables a large language model (LLM) to reconstruct the original annotations. We propose a corresponding ICAI algorithm and validate its generated constitutions quantitatively based on annotation reconstruction accuracy on several datasets: (a) synthetic feedback data with known principles; (b) AlpacaEval cross-annotated human feedback data; (c) crowdsourced Chatbot Arena data; and (d) PRISM data from diverse demographic groups. As an example application, we further demonstrate the detection of biases in human feedback data. As a short and interpretable representation of the original dataset, generated constitutions have many potential use cases: they may help identify undesirable annotator biases, better understand model performance, scale feedback to unseen data, or assist with adapting AI models to individual user or group preferences. We release the source code for our algorithm and experiments at https://github.com/rdnfn/icai.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2406.06560")
get_code_for_paper("2406.06560")
have("2406.06560")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2406.06560.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2406.06560)
Connect an agent — have() is free.