Papers › On the Measure of Intelligence

On the Measure of Intelligence

5 Nov 2019arXiv:1911.01547archive 2025-07-28

François Chollet

To make deliberate progress towards more intelligent and more human-like artificial systems, we need to be following an appropriate feedback signal: we need to be able to define and evaluate intelligence in a way that enables comparisons between two systems, as well as comparisons with humans. Over the past hundred years, there has been an abundance of attempts to define and measure intelligence, across both the fields of psychology and AI. We summarize and critically assess these definitions and evaluation approaches, while making apparent the two historical conceptions of intelligence that have implicitly guided them. We note that in practice, the contemporary AI community still gravitates towards benchmarking intelligence by comparing the skill exhibited by AIs and humans at specific tasks such as board games and video games. We argue that solely measuring skill at any given task falls short of measuring intelligence, because skill is heavily modulated by prior knowledge and experience: unlimited priors or unlimited training data allow experimenters to "buy" arbitrary levels of skills for a system, in a way that masks the system's own generalization power. We then articulate a new formal definition of intelligence based on Algorithmic Information Theory, describing intelligence as skill-acquisition efficiency and highlighting the concepts of scope, generalization difficulty, priors, and experience. Using this definition, we propose a set of guidelines for what a general AI benchmark should look like. Finally, we present a benchmark closely following these guidelines, the Abstraction and Reasoning Corpus (ARC), built upon an explicit set of priors designed to be as close as possible to innate human priors. We argue that ARC can be used to measure a human-like form of general fluid intelligence and that it enables fair general intelligence comparisons between AI systems and humans.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

The archive's official repository (fchollet/ARC) was not harvested; the 11 samples below come from 2 community repositories.

Syntology 11 code samples harvested from 2 repositories linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 11 samples from 2 repositories, 10 ran (10 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

fchollet/ARC officialmentioned in papermentioned on GitHubApache-2.0Syntology: not harvested report
alejandrodemiquel/arc mentioned on GitHubApache-2.0Syntology: not harvested report
arcprize/arc-agi-2 mentioned on GitHubApache-2.0Syntology: not harvested report
artyompal/kaggle-abstract-reasoning mentioned on GitHubApache-2.0Syntology: 3 samples, 2 ran (0 instrument-failed) · 1 unverified report
fchollet/arc-agi mentioned on GitHubApache-2.0Syntology: not harvested report
ilialarchenko/abstract_reasoning mentioned on GitHubApache-2.0Syntology: 8 samples, 8 ran (0 instrument-failed) · 0 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

11 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

10ran
1unverified

Licence: 0 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its 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.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at 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 cleared, but the stored copy of the same code that Syntology serves is not. 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 label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

artyompal/kaggle-abstract-reasoning community (archive-listed) 3 samples, 2 ran (0 instrument-failed) · 1 unverified
encode_file python-dsl-code/bake_kernel.py ran Apache-2.0 (permissive) · 01b3f8dafbba00b7 · report fixture: signature path:str/0/str · returned str · level recorded 2026-09-24
vcat_imgs python-dsl-code/genetics.py ran Apache-2.0 (permissive) · e5703b19f49bceeb · report fixture: signature imgs:list/1/Image, border:int/0/int · returned Image · level recorded 2026-09-24
parse_output in 21 papers unit_tests.py unverified Apache-2.0 (permissive) · ca5e60c977324c1e · report
ilialarchenko/abstract_reasoning community (archive-listed) 8 samples, 8 ran (0 instrument-failed) · 0 unverified
combine_submission_files src/submission_utils.py ran Apache-2.0 (permissive) · 5705f797d6c8ed13 · report fixture: signature list_of_dfs:list/1/DataFrame, sample_submission_path:str/0/str · returned DataFrame · level recorded 2026-09-24
combine_two_lists src/functions.py ran Apache-2.0 (permissive) · 2598408104f35ac7 · report fixture: signature list1:list/1/Tensor, list2:list/1/Tensor · returned list · level recorded 2026-09-24
find_color_boundaries src/preprocessing.py ran Apache-2.0 (permissive) · cb5b66e357456a69 · report fixture: signature array:ndarray/2/int, color:int/0/int · returned tuple · level recorded 2026-09-24
find_grid src/preprocessing.py ran Apache-2.0 (permissive) · ab44366ceba04378 · report fixture: signature image:ndarray/2/int, frame:bool/0/bool, possible_colors:NoneType/0/? · returned tuple · level recorded 2026-09-24
generate_submission src/submission_utils.py ran Apache-2.0 (permissive) · 54178cc12c59390e · report fixture: signature predictions_list:list/1/dict, sample_submission_path:str/0/str · returned DataFrame · level recorded 2026-09-24
get_color_max src/preprocessing.py ran Apache-2.0 (permissive) · 9b2b1b6f42de3ffe · report fixture: signature image:ndarray/2/int, color:int/0/int · returned tuple · level recorded 2026-09-24
matrix2answer src/utils.py ran Apache-2.0 (permissive) · 62a7b00a87aebb3b · report fixture: signature array:ndarray/2/int · returned str · level recorded 2026-09-24
swap_two_colors src/functions.py ran Apache-2.0 (permissive) · b8bf0064ef2c92ca · report fixture: signature image:ndarray/2/int · returned tuple · level recorded 2026-09-24

Tasks

ARCBenchmarking

Datasets

Introduced by this paper, per the archive.

ARC (The Abstraction and Reasoning Corpus)

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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