5 of 8 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; 0 honoured the contract we drafted, 0 violated it and 5 have no contract verdict; 0 failures of our instrument; 3 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; 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/2211.11540.json · badge: /api/ran/2211.11540.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 |
|---|---|---|
| alan-turing-institute/sdg-auditing | canonical (classifier label) classifier basis not recorded on the link |
5 ran · 3 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| get_count_matrix | Ran ran on a synthesized input |
alan-turing-institute/sdg-auditing/raw_ipf.py code served (permissive licence) · get_code("01a319dbf93f7023") 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 ndarray, ndim 3, dtype family int, shape (3, 2, 3) 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.
|
| load_data | Ran ran on a synthesized input |
alan-turing-institute/sdg-auditing/utils.py code served (permissive licence) · get_code("d1236cc35fd91c25") 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 DataFrame. 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.
|
| refactor_linear_combination | Ran ran on a synthesized input |
alan-turing-institute/sdg-auditing/auditing.py code served (permissive licence) · get_code("d9490bcb443413fb") 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 AddedFunctions. 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.
|
| sinkhorn_tensor | Ran ran on a synthesized input |
alan-turing-institute/sdg-auditing/raw_ipf.py code served (permissive licence) · get_code("6ff912bc65da4b55") 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 ndarray, ndim 3, dtype family float, shape (2, 3, 4) 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.
|
| split_linear_combination | Ran ran on a synthesized input |
alan-turing-institute/sdg-auditing/auditing.py code served (permissive licence) · get_code("89709a5623910d2f") 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 defaultdict. 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_margin_grids | Not yet run unverified (harvested, no recorded run) |
alan-turing-institute/sdg-auditing/raw_ipf.py code served (permissive licence) · get_code("3c635564d232e68a") How it ranno invocation recorded. |
| gram_schmidt | Not yet run unverified (harvested, no recorded run) |
alan-turing-institute/sdg-auditing/auditing.py code served (permissive licence) · get_code("7a848eb237060cf7") How it ranno invocation recorded. |
| load_synthetic_datasets | Not yet run unverified (harvested, no recorded run) |
alan-turing-institute/sdg-auditing/utils.py code served (permissive licence) · get_code("edc970a0714a753f") How it ranno invocation recorded. |
Of 8 samples lifted from this paper's linked repositories, 8 carry a function identity and 0 do not. Of the 8 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 8 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.
Synthetic data has gained significant momentum thanks to sophisticated machine learning tools that enable the synthesis of high-dimensional datasets. However, many generation techniques do not give the data controller control over what statistical patterns are captured, leading to concerns over privacy protection. While synthetic records are not linked to a particular real-world individual, they can reveal information about users indirectly which may be unacceptable for data owners. There is thus a need to empirically verify the privacy of synthetic data -- a particularly challenging task in high-dimensional data. In this paper we present a general framework for synthetic data generation that gives data controllers full control over which statistical properties the synthetic data ought to preserve, what exact information loss is acceptable, and how to quantify it. The benefits of the approach are that (1) one can generate synthetic data that results in high utility for a given task, while (2) empirically validating that only statistics considered safe by the data curator are used to generate the data. We thus show the potential for synthetic data to be an effective means of releasing confidential data safely, while retaining useful information for analysts.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2211.11540")
get_code_for_paper("2211.11540")
have("2211.11540")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2211.11540.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2211.11540)
Connect an agent — have() is free.