Home › Code › wilson_ci

wilson_ci

Syntologyentry name in harvested code

Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record.

wilson_ci appears in the code Syntology harvested for 8 papers, as 9 distinct code bodies found in 9 places (a place is one code body under one paper). Of the 8 papers, 8 with a sample that ran: 8 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument. 5 of the code bodies carry a behaviour fingerprint.

What this page is not. Routines are grouped here by the exact string of their function or class name. Nothing asserts that two samples named wilson_ci do the same thing, share code, or are comparable; the name is a string, not an identity. Behaviour outputs (what a fingerprinted sample returned on the shared battery) are not in this export and are not shown here; get_code(code_sha256="…") returns this sample's fingerprint on the shared battery, with the battery's shuffled null and lift; not shown on this site (how to connect). "Ran" means executed on a synthesized fixture, not that the code is correct or reproduces a paper.

Samples Syntology

The 9 distinct code bodies named wilson_ci: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 7 honoured, 2 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. One tile per status, in the site's fixed vocabulary, each code body counted once:

7ran · honoured contract
2ran · violated contract
0ran · our draft was wrong
0ran; the contract check could not run
0ran
0unverified
5fingerprinted

Licence is a property of each copy, so it is counted per place: 5 of the 9 places are pointer only (Syntology does not serve that copy's text). This site shows no code text for any sample; every row below links to the file in its repository where the record names one.

“Ran” means the sample executed on a synthesized input; it does not mean the output is correct. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “the contract check could not run” (RAISES, DEP_MISSING or TIMEOUT; hover a row's label for which) are failures of Syntology's instrument, not of the code, and those samples did run. The ran count above is every status except unverified, the same rule as each paper page; “with no instrument failure” is honoured, violated and ran with no contract checked. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Papers

8 papers shown of 8, newest first; 9 places in the table. A paper with no recorded date is placed by the month its arXiv id encodes, shown in the Date column as YYYY-MM (from id). One row per place: a paper whose repository defines the name more than once appears more than once, and the same code body held for several papers appears once under each, with the same status. Titles and dates are the archive's archive 2025-07-28 for papers in the archive, and the graph's for 8 papers added by Syntology. Status and fingerprint are Syntology's record of each code body; licence is recorded for each place. The File cell ends with the code body's code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

PaperDateFileStatus SyntologyLicence
Mind Viruses: Self-Propagating Ideas in Multi-Agent LLM Systems added by Syntology 2026-08 (from id) frotaur/mindvirus-viruschain/paper_figures/action_infection/extract_stats.py 69ef525f0e66024e ran · honoured contract fingerprinted MIT (permissive)
Implicit Geographic Inference in LLM Medical Triage: Language-Driven Disparities in Emergency Recommendations added by Syntology 2026-06 (from id) wongqihan/ai-behavioral-experiments/gender-age-triage/run_experiment.py daf150f5e4e5b28b ran · honoured contract MIT (permissive)
Domain Adaptation and Reasoning Frameworks in Language Models: A Controlled Experiment with Historical Cosmology added by Syntology 2026-05 (from id) fdeberna/chat-ptolemaic/evaluation/summarize_qwen_judgments.py 226793ee23a4ce7b ran · honoured contract fingerprinted no licence file found · pointer only
Domain-level metacognitive monitoring in frontier LLMs: A 33-model atlas added by Syntology 2026-05 (from id) synthiumjp/validity-scaling-llm/screen/validity_screen.py 5dcd318f224ef614 ran · honoured contract fingerprinted MIT (permissive)
From Prompt Risk to Response Risk: Paired Analysis of Safety Behavior of Large Language Models added by Syntology 2026-04 (from id) microsoft/PairedSafety/analysis/statistical_uncertainty/compute_ci.py c99829ab032929a1 ran · honoured contract fingerprinted MIT (permissive)
Unified Deployment-Aware Evaluation of Open Reasoning Language Models added by Syntology 2026-04 (from id) mkboch/UDAE/evaluation/metrics.py e60660601bd75ac4 ran · honoured contract fingerprinted no licence file found · pointer only
Emergent decentralized regulation in a purely synthetic society added by Syntology 2026-04 (from id) manikm-114/OpenClaw_V2/codes/di_robustness_variant.py e39261b3e6d117dc ran · violated contract no licence file found · pointer only
Emergent decentralized regulation in a purely synthetic society added by Syntology 2026-04 (from id) manikm-114/OpenClaw_V2/codes/figure19_risk_vs_policing.py cb43824ccc336246 ran · violated contract no licence file found · pointer only
LIE TO ME: HOW FAITHFUL IS CHAIN-OF-THOUGHT REASONING IN OPEN-WEIGHT REASONING MODELS? added by Syntology 2026-03 (from id) ricyoung/cot-faithfulness-open-models/measuring-faithfulness/check_quality.py 7ff6ba901e38b975 ran · honoured contract licence not identified · pointer only

This site shows no code text; each File cell links to the file on GitHub at the repository's current default branch, which may have changed since the harvest. "Pointer only" means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is under a permissive licence, but the stored copy of the same code that Syntology serves is not cleared for its text. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence cell for the reason. Per-sample records for a paper are on its paper page under "Code Syntology ran".

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections