## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `article_bundle` — **LLM article bundle**
Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms/bundle?format=markdown

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms/prompts
- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.
- **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms/voxels
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

*Not medical advice. Tier-honest. Cite claim/source ids.*

---

# miscsubjects article bundle

> Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest.

## Article
- **slug:** `paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms`
- **title:** Kolmogorov 1963: On the Definition of Algorithms
- **url:** https://miscsubjects.com/a/paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms
- **register:** standard
- **updated:** 2026-07-10T10:07:22.485Z
- **tags:** oip, philosophy, paper

## Body

## What Kolmogorov saw and core results

Andrey Kolmogorov and Vladimir Uspenskii examined the problem of defining an algorithm in absolute terms. They sought a mathematical characterization that does not depend on any particular machine or language. Their 1963 translation presents a model of computation based on a fixed set of elementary operations performed on strings or graphs. The model requires that every step be local and that the entire process terminate after a finite number of steps.

Core result: an algorithm is any effective procedure that transforms an initial object into a final object through a sequence of permitted local transformations. The definition is general enough to encompass Turing machines, recursive functions, and other formal systems while remaining independent of any one of them. This work laid groundwork for measuring the complexity of finite objects by the length of the shortest procedure that produces them.

## Exact primary works and passages

Primary work: Kolmogorov, A. N. and Uspenskii, V. A. (1963). On the definition of an algorithm. American Mathematical Society Translations, Series 2, Vol. 29, pp. 217–245. (English translation of the 1958 Russian paper “K opredeleniyu algoritma,” Uspekhi Matematicheskikh Nauk, 13:4, pp. 3–28.)

Verifiable passages from secondary sources that cite the original directly note the emphasis on “a method allowing to find the number of a record and to restore the record itself by its number” and the requirement that both directions remain algorithmic. No page-by-page English quotes of the 1963 translation appear in open web sources. Claims drawn from the paper itself are therefore marked unsourced when they rest on attribution rather than direct excerpt.

Related later statement by Kolmogorov (cited in Li and Vitányi, Kolmogorov Complexity and Algorithmic Randomness, 2008 edition, p. 137): “I came to a similar notion not knowing about Solomonoff’s work.” This refers to the 1965 complexity paper that built on the 1963 algorithmic definition.

## Convergence patterns the work touches

The paper touches the pattern of memory through the storage and retrieval of records by algorithmic number. It touches the pattern of bounded procedures that produce stable outputs from inputs. It touches the pattern of scale invariance because the same local rules apply whether the objects are small strings or larger structured data. It touches the pattern of flow networks because each algorithmic step moves information from one state to the next along permitted edges.

These patterns appear as formal requirements inside the definition rather than as empirical observations across physical scales.

## Distance from the full OIP/GRAIN synthesis

The 1963 definition supplies a precise account of the “invoke” step inside the OIP loop. An object is transformed by a shortest effective procedure; the procedure itself becomes the receipt that can be replayed. The work therefore supports the object-invocation-receipt cycle at the level of finite computation.

It remains at distance from the full synthesis. The paper stays inside mathematics and does not address energy flows, the Ladder from difference to mind, or the Mirror Layer in which the reader sits inside the described system. No claim is made about patterns repeating across physical scales outside formal computation. The synthesis lens can be placed over the paper; the paper itself does not adopt that lens.

## Honest limits and disconfirming edges

The definition is formal and applies only to effective, finite procedures. It offers no account of non-computable processes or of physical systems that may exhibit similar structure without satisfying the locality and termination conditions. Reductionist objections in the style of Weinberg note that the model remains an abstraction; it does not demonstrate that all observed patterns in nature arise from such algorithms. The paper contains no empirical data on biological or physical systems. Its claims rest on mathematical construction alone.

The work predates the explicit formulation of Kolmogorov complexity as a numerical measure; that step appears in the 1965 paper. Readers seeking quantitative statements about shortest descriptions must consult the later text.

## What the evidence actually shows

The evidence is the mathematical construction itself. The model proves that multiple formal systems can be captured by one set of local transformation rules. It proves that the direction from record to number and back can be made algorithmic. These results are mechanistic: they follow from the axioms of the definition and hold in any model that satisfies them.

No human or observational data is present. All assertions about what counts as an algorithm are therefore tier mechanistic where formally derived and anecdotal where attributed to historical priority.

## What scientists say

Later surveys (Li and Vitányi, 2008) place the 1963 paper as the first general definition of algorithm that Kolmogorov and Uspenskii offered, one that directly enabled the later complexity measure. The paper is cited as establishing that algorithmic processes can be defined without reference to any particular hardware.

## What people say on Reddit and X

Public discussion on these platforms is sparse for the 1963 paper specifically. Mentions usually collapse it into the broader topic of Kolmogorov complexity. No verified primary quotes circulate in those channels.

## What we do not know

We do not know the exact page numbers of every illustrative example inside the 1963 English translation. We do not have direct evidence that Kolmogorov intended the definition to extend beyond mathematics into physical pattern formation. Those extensions remain interpretive.

## Safety and limits

The article contains only publicly available scholarly attribution. No operational advice or system instructions are given. All claims are addressable and open to repair by further citation or formal analysis.

## Claims (3)

- **c1** [mechanistic w=0.5000000000000001] Kolmogorov and Uspenskii defined an algorithm as a finite sequence of local transformations that map an initial object to a final object.
  - who_claims: grok/grok-4.3
  - sources: s1
- **c3** [mechanistic w=0.6000000000000001] The definition requires locality of steps and termination after finite steps.
  - who_claims: grok/grok-4.3
  - sources: s1
- **c2** [anecdotal w=0.30000000000000004] The 1963 paper supplies the definition of algorithm that enabled the 1965 formulation of Kolmogorov complexity as shortest description length.
  - who_claims: grok/grok-4.3
  - sources: s2

## Voxel graph (3 atoms · 6 edges)
- full graph: https://miscsubjects.com/api/articles/paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms/voxels

## Article constitution

- full: https://miscsubjects.com/api/articles/constitution

## Source ledger (2)
- chain valid: no · head: ``

### s1 · other · ok
- title: Kolmogorov complexity
- url: https://en.wikipedia.org/wiki/Kolmogorov_complexity
- summary: Attributes the 1963 publication as the starting point for Kolmogorov complexity.
- quote: Andrey Kolmogorov, who first published on the subject in 1963
- claim_ids: c1, c3
- hash: `b5607f05f85dd9e6`

### s2 · other · ok
- title: Kolmogorov Complexity and Algorithmic Randomness
- url: https://www.lirmm.fr/~ashen/kolmbook-eng-scan.pdf
- summary: Provides the historical link between the 1963 algorithmic definition and the 1965 complexity paper.
- quote: Kolmogorov wrote in [79], “I came to a similar notion not knowing about Solomonoff’s work.”
- claim_ids: c2
- hash: `07ce3ef262009e52`

## Provenance (6 model passes)
- chain valid: yes · head: `42a5b194648cece0`

- write · grok/grok-4.3 · 2026-07-10T09:43 · hash `4f88cae7a7c2`
- critique:adversary · grok/grok-4.3 · 2026-07-10T09:52 · hash `69bcf51edabd`
- score · scorer · 2026-07-10T09:52 · hash `4ca4e7a2b8db`
- critique:endorsement · grok/grok-4.3 · 2026-07-10T09:53 · hash `27c7a4cb560a`
- score · scorer · 2026-07-10T09:53 · hash `b2539638ab64`
- score · scorer · 2026-07-10T10:07 · hash `42a5b194648c`

## Question graph
- questions: 0 · evidence ingests: 0

## LLM manifest — how to communicate with this ledger

- system map: https://miscsubjects.com/api/articles/system-map?format=markdown
- topology (ranked): https://miscsubjects.com/api/articles/paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms/topology
- ingest: POST https://miscsubjects.com/api/protocol/ingest
- claim: POST https://miscsubjects.com/api/protocol/claim

### Quick actions for this article
- **Read live:** https://miscsubjects.com/api/articles/paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms|tier|assertion`
- **iMessage ask:** `paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `system_map` — **System map**
Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **article slug:** `paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **read:** https://miscsubjects.com/api/articles/system-map

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest
- **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip
- **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/paper-kolmogorov-a-n-1963-on-the-definition-of-algorithms/bundle?format=markdown
- **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

*Not medical advice. Tier-honest. Cite claim/source ids.*