The on-wiki version of this edition of the newsletter can be found here: https://www.wikifunctions.org/wiki/Wikifunctions:Status_updates/2026-04-25 ---- The Foundation’s search for the perfect language
An academic paper critically discussing the Abstract Wikipedia project by University of Melbourne senior lecturer Michael Falk https://michaelfalk.io/ has been published in Springer Nature AI & Society https://link.springer.com/article/10.1007/s00146-026-02899-w: *Wikilambda the ultimate - The Wikimedia Foundation’s search for the perfect language*.
The title of the paper riffs on a wonderful book https://en.wikipedia.org/wiki/La%20Ricerca%20della%20Lingua%20Perfetta%20nella%20Cultura%20Europea by Umberto Eco https://en.wikipedia.org/wiki/Umberto%20Eco, a book I recommend everyone to read when they are interested in the goal of Abstract Wikipedia, as the book describes the many brilliant minds that have aimed for similar goals, and their failures to achieve them. I thought I discussed the book in this newsletter before, but it seems I am mistaken; I will do so in the near future.
Michael Falk discusses a number of interesting points about Abstract Wikipedia:
- An overview of the architecture and ambition of the project - The 2023 evaluation of the project by the Google.org fellows https://meta.wikimedia.org/wiki/Abstract%20Wikipedia/Updates/2023-02-08 - A literary criticism of the code of the WikiLambda orchestrator
I recommend reading the article if you are interested. Whereas I would disagree with some of the characterizations, I also find a lot to agree with. I want to avoid going through it point by point, but if there’s anything you find particularly interesting, please raise it and I’d be happy to discuss that point further. I do want to cite a few sentences from the conclusions:
*The Abstract Wikipedia/Wikifunctions project has a profoundly moral aim: to give human beings control over information in the Age of GenAI. If the problem were simply to populate minority-language Wikipedias with articles, it would be simpler just to get a Large Language Model (LLM) to translate English Wikipedia into those languages. But Wikilambda presents a stark alternative to LLMs such as Gemini, Llama or ChatGPT. LLMs rely on vast concealed datasets. Wikifunctions draws its data openly from public Wikimedia databases. LLMs generate text using opaque algorithms that even their designers struggle to control. Wikilambda makes every part of every algorithm available to anyone. In short, Wikilambda is contestable. If you ask an LLM to generate an article on a topic, the only way to contest its algorithm is to click 👍 or 👎 (Crawford and Gillespie 2016). If you are unhappy with an article generated by Abstract Wikipedia, you will be able to: change the “abstract” content in Wikidata; change the algorithms that construct or render the article in Wikifunctions; or sever the connection between the article and Abstract Wikipedia, and edit the article the old-fashioned way in Wikipedia. The role of Wikilambda in all this is to make algorithms “defeasible” (Blanton et al. 2022). Every part of every algorithm is there, and can be contested on the platform itself, even if that contestation may be culturally and politically constrained (Tkacz 2015; Ford 2022). Wikilambda is an attempt to design what Alan Blackwell (2024) calls a “moral code”: it combines More Open Representation, Access to Learning, and Creating Opportunities for Digital Expression. If nothing else, Wikilambda is a thundering critique of corporate AI hype.*
Falk, M. Wikilambda the ultimate: the Wikimedia foundation’s search for the perfect language. AI & Soc (2026). doi.org/10.1007/s00146-026-02899-w News in Types: ‘Tis the seasons
This week we implemented the proposal https://www.wikifunctions.org/wiki/Wikifunctions:Type_proposals/Season by Dv103 https://www.wikifunctions.org/wiki/User:Dv103 to create a type for the four temperate seasons, Spring, Summer, Fall or Autumn, and Winter. The new type is now available: temperate season (Z33827) https://www.wikifunctions.org/wiki/Z33827
Thanks to Dv103 for the proposal, and the community for discussing and supporting it! We are looking forward to seeing the functions using the new type.
We invite you all to create new and discuss the existing type proposals so we can keep on creating new types. Thanks to all the community members contributing to the discussion and writing proposals, making it possible to extend the Wikifunctions to new domains! Fresh Functions weekly: 61 new Functions
This week we had 61 new functions. Here is an incomplete list of functions with implementations and passing tests to get a taste of what functions have been created. Thanks everybody for contributing!
- monolingual text from lang and str in zh-hant/s (Z33391) https://www.wikifunctions.org/wiki/Z33391 - fallback languages codes with fallbacks (Z33399) https://www.wikifunctions.org/wiki/Z33399 - Unlabelled (Z33405) https://www.wikifunctions.org/wiki/Z33405 - best lexeme from list with label (Z33415) https://www.wikifunctions.org/wiki/Z33415 - subject is instance of, default (Z33420) https://www.wikifunctions.org/wiki/Z33420 - item is instance of something (Z33431) https://www.wikifunctions.org/wiki/Z33431 - verb to agent noun (Z33439) https://www.wikifunctions.org/wiki/Z33439 - Tagalog verb to agent noun (Z33440) https://www.wikifunctions.org/wiki/Z33440 - Filter but fallback if empty (Z33453) https://www.wikifunctions.org/wiki/Z33453 - Monolingual text as HTML with language span (Z33457) https://www.wikifunctions.org/wiki/Z33457 - State location using entity and class, en, 4 args (Z33459) https://www.wikifunctions.org/wiki/Z33459 - wrap text as HTML element (Z33470) https://www.wikifunctions.org/wiki/Z33470 - magnitude of complex128 (Z33499) https://www.wikifunctions.org/wiki/Z33499 - same complex128 within tolerance (Z33506) https://www.wikifunctions.org/wiki/Z33506 - remove tones from pinyin (Z33509) https://www.wikifunctions.org/wiki/Z33509 - reference note of pitch standard (Z33570) https://www.wikifunctions.org/wiki/Z33570 - qualifier value of item property claim (Z33573) https://www.wikifunctions.org/wiki/Z33573 - qualifier value of Wikidata statement (Z33579) https://www.wikifunctions.org/wiki/Z33579 - exponent minus log (Z33593) https://www.wikifunctions.org/wiki/Z33593 - argument of Complex number (Z33610) https://www.wikifunctions.org/wiki/Z33610 - is negative (float64) (Z33615) https://www.wikifunctions.org/wiki/Z33615 - cells for enwikt Japanese verb conj. table row (Z33644) https://www.wikifunctions.org/wiki/Z33644 - intersperse delimiter throughout list (Z33646) https://www.wikifunctions.org/wiki/Z33646 - float as plain decimal to decimal places (Z33672) https://www.wikifunctions.org/wiki/Z33672 - complex conjugate (complex128s) (Z33679) https://www.wikifunctions.org/wiki/Z33679 - frequency of MIDI note number (Z33682) https://www.wikifunctions.org/wiki/Z33682 - subject is instance of (html) (Z33687) https://www.wikifunctions.org/wiki/Z33687 - subsection title from Wikidata label (Z33690) https://www.wikifunctions.org/wiki/Z33690 - subsection title (H3) (Z33691) https://www.wikifunctions.org/wiki/Z33691 - single char pinyin with tone numbers to tone marks (Z33696) https://www.wikifunctions.org/wiki/Z33696 - multiply Complex numbers (float64) (Z33700) https://www.wikifunctions.org/wiki/Z33700 - divide Complex numbers (float64) (Z33708) https://www.wikifunctions.org/wiki/Z33708 - square magnitude of Complex number (float64) (Z33713) https://www.wikifunctions.org/wiki/Z33713 - pad end of list (Z33720) https://www.wikifunctions.org/wiki/Z33720 - enwikt Module:Hrkt-translit tr (Z33727) https://www.wikifunctions.org/wiki/Z33727 - Word order (SOV, SVO...) of WD language Item (Z33731) https://www.wikifunctions.org/wiki/Z33731 - Word order (SOV, SVO...) of Natural language (Z33738) https://www.wikifunctions.org/wiki/Z33738 - Basque article-less instantiating sentence (Z33753) https://www.wikifunctions.org/wiki/Z33753 - Unlabelled (Z33768) https://www.wikifunctions.org/wiki/Z33768 - word for predicate (Z33775) https://www.wikifunctions.org/wiki/Z33775
A complete list of all functions sorted by when they were created https://www.wikifunctions.org/wiki/Special:ListObjectsByType?type=Z8&orderby=latest is available.
Denny and Team,
First, congratualtions on getting this coverage. Second, I want to say that I deeply respect the moral foundation behind Abstract Wikipedia and Wikifunctions. The idea of making knowledge generation contestable, transparent, and free from opaque model behavior is not just technically interesting, it’s necessary in today’s AI world.
The distinction you’re drawing between LLMs and Wikilambda is real and important. Open data, inspectable logic, and the ability to intervene at every layer of the system represent a meaningful alternative to black-box generation. Where there is still a critical gap is not in principle, but in accessibility of participation.
Wikifunctions makes every part of the system contestable, but in practice, that contestability is mediated through programming abstractions. To meaningfully engage, a contributor must understand functions, execution logic, and composability at a level that resembles software development. This creates a barrier where the right to contest exists, but the ability to exercise that right is unevenly distributed.
In other words, the system is open, but not yet broadly usable. When I proposed the aiidea Graph as an alternative years ago, it was a different approach to the same moral objective: Instead of requiring users to modify algorithms, it allows them to operate directly on ideas (sentences), objects, and their relationships, which are the natural units of human knowledge. It’s reuse of faithful recordation of information in graph form.
Rather than exposing contestability through code, aiidea exposes it through:
Direct inspection of source-backed statements Transparent linkage between ideas and underlying data The ability to challenge, replace, or extend knowledge at the sentence level (something we all know, not just some skilled users) Deterministic responses constructed from traceable subgraphs rather than generated text This preserves the core moral properties:
Transparency Contestability Auditability But shifts the interaction surface from programming to reasoning. Where Wikilambda makes algorithms defeasible, aiidea makes knowledge itself defeasible, without requiring users to understand or modify the machinery that produces it. This is a subtle but important distinction. One system opens the engine; the other lets people steer the vehicle without needing to be engineers.
I believe both approaches are aligned in intent, but optimized for different layers of participation. My concern, and the reason for reaching out, is that if contestability depends on developer-level fluency, we risk recreating a new kind of gatekeeping, even within an open system.
I would welcome the opportunity to continue this conversation. I think there is real potential for alignment in building systems that are not just open in principle, but broadly usable in practice.
Doug
Douglas Clark www.aiidea.biz 707.210.4771
This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
On Apr 25, 2026, at 2:22 AM, Denny Vrandečić via Abstract-Wikipedia abstract-wikipedia@lists.wikimedia.org wrote:
The Abstract Wikipedia/Wikifunctions project has a profoundly moral aim: to give human beings control over information in the Age of GenAI. If the problem were simply to populate minority-language Wikipedias with articles, it would be simpler just to get a Large Language Model (LLM) to translate English Wikipedia into those languages. But Wikilambda presents a stark alternative to LLMs such as Gemini, Llama or ChatGPT. LLMs rely on vast concealed datasets. Wikifunctions draws its data openly from public Wikimedia databases. LLMs generate text using opaque algorithms that even their designers struggle to control. Wikilambda makes every part of every algorithm available to anyone. In short, Wikilambda is contestable. If you ask an LLM to generate an article on a topic, the only way to contest its algorithm is to click 👍 or 👎 (Crawford and Gillespie 2016). If you are unhappy with an article generated by Abstract Wikipedia, you will be able to: change the “abstract” content in Wikidata; change the algorithms that construct or render the article in Wikifunctions; or sever the connection between the article and Abstract Wikipedia, and edit the article the old-fashioned way in Wikipedia. The role of Wikilambda in all this is to make algorithms “defeasible” (Blanton et al. 2022). Every part of every algorithm is there, and can be contested on the platform itself, even if that contestation may be culturally and politically constrained (Tkacz 2015; Ford 2022). Wikilambda is an attempt to design what Alan Blackwell (2024) calls a “moral code”: it combines More Open Representation, Access to Learning, and Creating Opportunities for Digital Expression. If nothing else, Wikilambda is a thundering critique of corporate AI hype.
Hello Douglas, and thank you for your proposal and your answer!
In your proposal, how is the knowledge translated to text, so that it can be integrated into Wikipedia?
Cheers, Denny
On Mon, Apr 27, 2026 at 6:35 PM Douglas Clark clarkdd@gmail.com wrote:
Denny and Team,
First, congratualtions on getting this coverage. Second, I want to say that I deeply respect the moral foundation behind Abstract Wikipedia and Wikifunctions. The idea of making knowledge generation contestable, transparent, and free from opaque model behavior is not just technically interesting, it’s necessary in today’s AI world.
The distinction you’re drawing between LLMs and Wikilambda is real and important. Open data, inspectable logic, and the ability to intervene at every layer of the system represent a meaningful alternative to black-box generation. Where there is still a critical gap is not in *principle*, but in *accessibility of participation*.
Wikifunctions makes every part of the system contestable, but in practice, that contestability is mediated through programming abstractions. To meaningfully engage, a contributor must understand functions, execution logic, and composability at a level that resembles software development. This creates a barrier where the *right to contest* exists, but the *ability to exercise that right* is unevenly distributed.
In other words, the system is open, but not yet broadly *usable*. When I proposed the aiidea Graph as an alternative years ago, it was a different approach to the same moral objective: Instead of requiring users to modify algorithms, it allows them to operate directly on *ideas (sentences), objects, and their relationships*, which are the natural units of human knowledge. It’s reuse of faithful recordation of information in graph form.
Rather than exposing contestability through code, aiidea exposes it through:
- Direct inspection of source-backed statements
- Transparent linkage between ideas and underlying data
- The ability to challenge, replace, or extend knowledge at the
sentence level (something we all know, not just some skilled users)
- Deterministic responses constructed from traceable subgraphs rather
than generated text
This preserves the core moral properties:
- Transparency
- Contestability
- Auditability
But shifts the interaction surface from *programming* to *reasoning*. Where Wikilambda makes algorithms defeasible, aiidea makes *knowledge itself defeasible*, without requiring users to understand or modify the machinery that produces it. This is a subtle but important distinction. One system opens the engine; the other lets people steer the vehicle without needing to be engineers.
I believe both approaches are aligned in intent, but optimized for different layers of participation. My concern, and the reason for reaching out, is that if contestability depends on developer-level fluency, we risk recreating a new kind of gatekeeping, even within an open system.
I would welcome the opportunity to continue this conversation. I think there is real potential for alignment in building systems that are not just open in principle, but broadly usable in practice.
Doug Douglas Clark www.aiidea.biz 707.210.4771
This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
On Apr 25, 2026, at 2:22 AM, Denny Vrandečić via Abstract-Wikipedia < abstract-wikipedia@lists.wikimedia.org> wrote:
*The Abstract Wikipedia/Wikifunctions project has a profoundly moral aim: to give human beings control over information in the Age of GenAI. If the problem were simply to populate minority-language Wikipedias with articles, it would be simpler just to get a Large Language Model (LLM) to translate English Wikipedia into those languages. But Wikilambda presents a stark alternative to LLMs such as Gemini, Llama or ChatGPT. LLMs rely on vast concealed datasets. Wikifunctions draws its data openly from public Wikimedia databases. LLMs generate text using opaque algorithms that even their designers struggle to control. Wikilambda makes every part of every algorithm available to anyone. In short, Wikilambda is contestable. If you ask an LLM to generate an article on a topic, the only way to contest its algorithm is to click 👍 or 👎 (Crawford and Gillespie 2016). If you are unhappy with an article generated by Abstract Wikipedia, you will be able to: change the “abstract” content in Wikidata; change the algorithms that construct or render the article in Wikifunctions; or sever the connection between the article and Abstract Wikipedia, and edit the article the old-fashioned way in Wikipedia. The role of Wikilambda in all this is to make algorithms “defeasible” (Blanton et al. 2022). Every part of every algorithm is there, and can be contested on the platform itself, even if that contestation may be culturally and politically constrained (Tkacz 2015; Ford 2022). Wikilambda is an attempt to design what Alan Blackwell (2024) calls a “moral code”: it combines More Open Representation, Access to Learning, and Creating Opportunities for Digital Expression. If nothing else, Wikilambda is a thundering critique of corporate AI hype.*
Denny,
Great exchanging with you again. We ingested all 161 million sentences of Wikipedia for our proof of concept - a context knowledge graph. I am pretty confident you asked this specific question so you can DQ this immediately, and yes, we do use an embedding model to resolve meaning, initially. However, we use a fully explainable and transparent method to move from the high dimensions of the embedding space to a 3D space we call Pixelization of Semantic Anisotropy (PSA). We use guide stars sentences to align the semantics of the 3D space, losing none of the semantic or contextual information needed for the graph in the compression from 4096 to 3D. We have submitted a paper to the ACL on our findings of meaning alignment decay by distance in the PSA field. We can even exchange coordinates to another aiidea Graph to express meaning. By ingesting sentences, the end result is a fully human readable, explainable, traceable to provenance graph of ideas. Every step and all math can be checked by a human. The original embedding model is multi-lingual and multi-modal, thus our sentence nodes (and paraphrase nodes) are the basic units of meaning tracked in the graph, regardless of language or conveyance mode.. However, we also extract the objects from the sentences and using an ensemble of approaches (all transparent and explainable to anyone that listened in grammar and algebra class) to link the objects to an ontology. While we ship with the BFO/CCO ontology as a seed, we are ontology agnostic, and can use any ontology, including WikiData. Lastly, we use ontological frontier pressure to model where the ontology is under stress (does not have coverage for the incoming objects) as an adjacent possible probe to flag the need for human intervention, or in your case, possibly new article(s).
I would argue that the aiidea Graph is more easily understood by non-programmers than Abstract. We have already demonstrated that it can work at Wikipedia scale. I’ve attached some images to help in your understanding. I am not in any way denegrating Abstract. I just think that your rigidity in a strictly function based approach is limiting. There are always N ways to get from A to B. Now that you are mostly in production, your uptake numbers will tell you if you stay in mostly technical users, or you branch out into the wider community. Your goal is about trust and transparency and so too mine. I just don’t think that AI is automatically bad. I do think that it is just the natural emergence of information under increasing pressure to reduce local entropy. Its a tool.
Doug
Douglas Clark www.aiidea.biz 707.210.4771
This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.


On Apr 28, 2026, at 11:30 AM, Denny Vrandečić dvrandecic@wikimedia.org wrote:
Hello Douglas, and thank you for your proposal and your answer!
In your proposal, how is the knowledge translated to text, so that it can be integrated into Wikipedia?
Cheers, Denny
On Mon, Apr 27, 2026 at 6:35 PM Douglas Clark <clarkdd@gmail.com mailto:clarkdd@gmail.com> wrote:
Denny and Team,
First, congratualtions on getting this coverage. Second, I want to say that I deeply respect the moral foundation behind Abstract Wikipedia and Wikifunctions. The idea of making knowledge generation contestable, transparent, and free from opaque model behavior is not just technically interesting, it’s necessary in today’s AI world.
The distinction you’re drawing between LLMs and Wikilambda is real and important. Open data, inspectable logic, and the ability to intervene at every layer of the system represent a meaningful alternative to black-box generation. Where there is still a critical gap is not in principle, but in accessibility of participation.
Wikifunctions makes every part of the system contestable, but in practice, that contestability is mediated through programming abstractions. To meaningfully engage, a contributor must understand functions, execution logic, and composability at a level that resembles software development. This creates a barrier where the right to contest exists, but the ability to exercise that right is unevenly distributed.
In other words, the system is open, but not yet broadly usable. When I proposed the aiidea Graph as an alternative years ago, it was a different approach to the same moral objective: Instead of requiring users to modify algorithms, it allows them to operate directly on ideas (sentences), objects, and their relationships, which are the natural units of human knowledge. It’s reuse of faithful recordation of information in graph form.
Rather than exposing contestability through code, aiidea exposes it through:
Direct inspection of source-backed statements Transparent linkage between ideas and underlying data The ability to challenge, replace, or extend knowledge at the sentence level (something we all know, not just some skilled users) Deterministic responses constructed from traceable subgraphs rather than generated text This preserves the core moral properties:
Transparency Contestability Auditability But shifts the interaction surface from programming to reasoning. Where Wikilambda makes algorithms defeasible, aiidea makes knowledge itself defeasible, without requiring users to understand or modify the machinery that produces it. This is a subtle but important distinction. One system opens the engine; the other lets people steer the vehicle without needing to be engineers.
I believe both approaches are aligned in intent, but optimized for different layers of participation. My concern, and the reason for reaching out, is that if contestability depends on developer-level fluency, we risk recreating a new kind of gatekeeping, even within an open system.
I would welcome the opportunity to continue this conversation. I think there is real potential for alignment in building systems that are not just open in principle, but broadly usable in practice.
Doug
Douglas Clark www.aiidea.biz http://www.aiidea.biz/ 707.210.4771
This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
On Apr 25, 2026, at 2:22 AM, Denny Vrandečić via Abstract-Wikipedia <abstract-wikipedia@lists.wikimedia.org mailto:abstract-wikipedia@lists.wikimedia.org> wrote:
The Abstract Wikipedia/Wikifunctions project has a profoundly moral aim: to give human beings control over information in the Age of GenAI. If the problem were simply to populate minority-language Wikipedias with articles, it would be simpler just to get a Large Language Model (LLM) to translate English Wikipedia into those languages. But Wikilambda presents a stark alternative to LLMs such as Gemini, Llama or ChatGPT. LLMs rely on vast concealed datasets. Wikifunctions draws its data openly from public Wikimedia databases. LLMs generate text using opaque algorithms that even their designers struggle to control. Wikilambda makes every part of every algorithm available to anyone. In short, Wikilambda is contestable. If you ask an LLM to generate an article on a topic, the only way to contest its algorithm is to click 👍 or 👎 (Crawford and Gillespie 2016). If you are unhappy with an article generated by Abstract Wikipedia, you will be able to: change the “abstract” content in Wikidata; change the algorithms that construct or render the article in Wikifunctions; or sever the connection between the article and Abstract Wikipedia, and edit the article the old-fashioned way in Wikipedia. The role of Wikilambda in all this is to make algorithms “defeasible” (Blanton et al. 2022). Every part of every algorithm is there, and can be contested on the platform itself, even if that contestation may be culturally and politically constrained (Tkacz 2015; Ford 2022). Wikilambda is an attempt to design what Alan Blackwell (2024) calls a “moral code”: it combines More Open Representation, Access to Learning, and Creating Opportunities for Digital Expression. If nothing else, Wikilambda is a thundering critique of corporate AI hype.
Il 25/04/26 09:22, Denny Vrandečić via Abstract-Wikipedia ha scritto:
The title of the paper riffs on a wonderful book <https://en.wikipedia.org/wiki/ La%20Ricerca%20della%20Lingua%20Perfetta%20nella%20Cultura%20Europea> by Umberto Ecohttps://en.wikipedia.org/wiki/Umberto%20Eco, a book I recommend everyone to read when they are interested in the goal of Abstract Wikipedia, as the book describes the many brilliant minds that have aimed for similar goals, and their failures to achieve them. I thought I discussed the book in this newsletter before, but it seems I am mistaken; I will do so in the near future.
Noted! Thanks for the suggestion.
Very interesting newsletter.
Best, Federico
abstract-wikipedia@lists.wikimedia.org