WikiWho

register entry wikiwho-aio-20261029 OBS-aae62275a976 · file as first run sha256 465a3649856c6c89…

• T1-1 definition: 'wikiHow is a globally collaborative, wiki-style website featuring an extensive database of human-written how-to guides, instructions, quizzes, and community forums.' (followed by the chip 'Wikipedia +3'; 'wikiHow' is an inline google.com/goto link that resolves, HTTP 302, to https://www.wikihow.com/Main-Page)
• T1-2 founding: 'Launched in 2005 by internet entrepreneur Jack Herrick with the mission to build the world's most helpful how-to instructions.' (chip 'Fastly +1')
• T1-3 content: 'Contains over 100,000 articles covering diverse topics, created and audited through research, collaboration, and expert input from thousands of credentialed professionals' (chip 'wikiHow +2')
• T1-4 structure: 'Organized into 19 top-level categories spanning health, computing, finance, relationships, and more, available across multiple international languages.' (chip 'wikiHow +1')
• T1-5 link: 'You can browse all topics and articles directly on the wikiHow Category Listing' (google.com/goto; resolves, HTTP 302, to https://www.wikihow.com/Special:CategoryListing)
• T1-6 closer: an offer, 'If you'd like, let me know: … I can help locate or summarize the instructions you need.' (content replaced by use, N_ext)

• B1 Wikipedia — source chip 'Wikipedia +3' (no title) unreachable: no URL can be determined from the chip. Tried: the registry's cite_list gives url, title and snip as null for every chip, and the chip's '+n' further sources are not listed in the paste; with no title there is nothing to search by (WebSearch on a site name alone does not locate a page); the paste's only URLs are two inline google.com/goto links in the body, which resolve (HTTP 302, 2026-10-29 17:11:31 UTC) to https://www.wikihow.com/Main-Page and https://www.wikihow.com/Special:CategoryListing, pages the body names, not chips, and of the homonym; for this chip a candidate, English Wikipedia's article WikiHow (raw wikitext HTTP 200, 17:16:38 UTC, saved as W5-WikiHow.raw.txt), is a guess and is not admitted. The chip's site is its only text.
• B2 Fastly — source chip 'Fastly +1' (no title) unreachable: no URL can be determined from the chip. Tried: the registry's cite_list gives url, title and snip as null for every chip, and the chip's '+n' further sources are not listed in the paste; with no title there is nothing to search by (WebSearch on a site name alone does not locate a page); the paste's only URLs are two inline google.com/goto links in the body, which resolve (HTTP 302, 2026-10-29 17:11:31 UTC) to https://www.wikihow.com/Main-Page and https://www.wikihow.com/Special:CategoryListing, pages the body names, not chips. The chip's site is its only text.
• B3 wikiHow — source chip 'wikiHow +2' (no title) unreachable: no URL can be determined from the chip. Tried: the registry's cite_list gives url, title and snip as null for every chip, and the chip's '+n' further sources are not listed in the paste; with no title there is nothing to search by (WebSearch on a site name alone does not locate a page); the paste's only URLs are two inline google.com/goto links in the body, which resolve (HTTP 302, 2026-10-29 17:11:31 UTC) to https://www.wikihow.com/Main-Page and https://www.wikihow.com/Special:CategoryListing, pages the body names, not chips. The chip's site is its only text.
• B4 wikiHow — source chip 'wikiHow +1' (no title) unreachable: no URL can be determined from the chip. Tried: the registry's cite_list gives url, title and snip as null for every chip, and the chip's '+n' further sources are not listed in the paste; with no title there is nothing to search by (WebSearch on a site name alone does not locate a page); the paste's only URLs are two inline google.com/goto links in the body, which resolve (HTTP 302, 2026-10-29 17:11:31 UTC) to https://www.wikihow.com/Main-Page and https://www.wikihow.com/Special:CategoryListing, pages the body names, not chips. The chip's site is its only text.
• B5 the WikiWho API's README (GitHub, gesiscss/wikiwho_api_public), the first developer's (GESIS) own page the census's saved copy (sources/wikiwho--api-readme.html.gz, gunzipped; wikiwho--api-readme.txt copied), read by the census 2026-10-29, HTTP 200; not refetched; gunzipped html sha256 b93dc1cea1081954e853d52bf2d46a5b5c03b8c0831636b2d75bb402ac943d2b (equal to the census's), text sha256 b93dc1cea1081954e853d52bf2d46a5b5c03b8c0831636b2d75bb402ac943d2b
• B6 the entity's page on mediawiki.org (Wikimedia, its maintainer), 'WikiWho', last edited 15 July 2026 the census's saved copy (sources/wikiwho--mediawiki.html.gz, gunzipped; wikiwho--mediawiki.txt copied), read by the census 2026-10-29, HTTP 200; not refetched; gunzipped html sha256 97cd049ccef3a05b63e29d2b47b87f6cda92755f1822563f8485865e180acb69 (equal to the census's), text sha256 93b47b1bc1e5b5d981c25a05f3dc1a6c9a026dcc392ab4397c27875593512dee
• B7 the entity's research page on Meta-Wiki, 'Research:Wikiwho Provenance Api' (contact Fabian Flöck, GESIS), last edited 5 June 2024 the census's saved copy (sources/wikiwho--meta-research.html.gz, gunzipped; wikiwho--meta-research.txt copied), read by the census 2026-10-29, HTTP 200; not refetched; gunzipped html sha256 2055e9f1886d338599645276a0f98612cc712bbdac30bc640ef9ed125a30be34 (equal to the census's), text sha256 de773ae93086d1f1daa09d1c687df975ba7f994bbe962084e38cfdaee52de562
• B8 the entity's own service page, Wikimedia's WikiWho API host (the census's url field; not one of the census's sources) fetched 2026-10-29 at 17:10:39 UTC with curl -sSL -m 30 -A 'Mozilla/5.0'; HTTP 200; html sha256 2a69700e77f742321c0510ae690da329265a54257e7bab50c33a88d07e877e95, text sha256 fc98800bfeb90eee8d72be9039b59690f59b7ea1d4bd0b7e7b0257cc703f1e2c; https://wikiwho-api.wmcloud.org/ (the README's Wikimedia host) answered the same bytes at 17:10:40 UTC (B8-api-host.html)
• B9 Wikipedia: the section 'WikiWho' of the article on GESIS – Leibniz Institute for the Social Sciences (the name's redirect target) rendered page fetched 2026-10-29 at 17:09:46 UTC with curl -sS -m 30 -A 'Mozilla/5.0'; HTTP 200; html sha256 cba1857506850dd5b13efe7373563f6658cf456089a576cdf2e996d30eb0b540, text sha256 53e6784e62b2c6f648ad9cccb5674656e2853797b25d5d7ad0bc42c0ebd673e4; wikitext of the target fetched at 17:10:27 UTC (B9.raw.txt)

E_A, the archive's entity: WikiWho as the provenance census records it (editor Lee Sharks, compiled 2026-10-29, schema 1.0): an algorithm and API of the lineage 'authorship and reuse', which records and tests provenance; the object that receives it, 'a single token (word) of a Wikipedia article'; the relations carried, origin (the revision and editor that introduced the token), deletion and reintroduction, on the article's full revision history, re-parsed; tested on every edit, with what survives per token and a method evaluated at 95%; first developed by KIT and GESIS, since August 2021 maintained by Wikimedia Community Tech and the Wiki Education Foundation; active, its GESIS host to give way to Wikimedia; the Meta page's beta for four languages an earlier state; the WWW 2014 paper and today's list of wikis unchecked; also known as WhoColor and Who Wrote That?; and, at its exact name on the Overview on 2026-10-29, absent, its place taken by wikiHow without notice (Capture Registry). PE-05 PE-06 PE-07 PE-08 PE-09 PE-10 PE-11 PE-12 PE-13 PE-15 PE-16 PE-04 PE-18 PE-19 PE-23 PE-24 PE-25 PE-01 PE-02 PE-29 CAP-1-01 CAP-1-09; defining papers

E_F, the field's entity (type C — a conventional reading holds it (public entity: an authorship-attribution algorithm and API for Wikipedia, with its HTML service WhoColor; the tool Who Wrote That? built on it; no Wikipedia article, a section of the GESIS article; the chips at the name are a homonym's, wikiHow)): WikiWho, 'A service that provides authorship attribution of Wikipedia articles' (MediaWiki page, B6) 'using a content persistence algorithm' (B6), whose API 'gives access to the provenance/changes of words (tokens) in Wikipedia articles' (README, B5): it parses every historical revision of an article to find who wrote, removed or reinserted which text at token level (B5, B6, B9), evaluated at 95% accuracy on fairly revision-rich articles (WWW 2014; B5, B6), implemented for wikitext (B5); first conceived as Fabian Flöck's dissertation project at KIT, developed with Maribel Acosta and hosted at GESIS (B8, B9), moved to Wikimedia Cloud Services in August 2021 and maintained by Community Tech and the Wiki Education Foundation (B6), its APIs at wikiwho.wmcloud.org for 70 languages (B6, B8); its WhoColor API powers Who Wrote That? (B6). English Wikipedia has no article for it: the name redirects to the section 'WikiWho' of the GESIS article (B9). The chips at the name (B1–B4) are wikiHow's, a distinct entity.

ρ = extends: The archive reads E_F as the entity and adds senses, limits and relations on it: the entity read by the census's question of what provenance it carries, through which operation, with what evidence of survival (PE-29, PE-09, PE-13, PE-16), its lineage and capability (PE-05, PE-07, PE-08), the lifecycle kept apart from the observation (PE-23, PE-19), what is left unchecked (PE-24, PE-25), and the reception record at its name (CAP-1-01, CAP-1-05, CAP-1-09). PE-29 PE-09 PE-13 PE-16 PE-05 PE-07 PE-08 PE-23 PE-19 PE-24 PE-25 CAP-1-01 CAP-1-05 CAP-1-09. Guard: ρ = extends claims an addition and no more (§1.2a). Where an archive claim and a field claim differ (the census's aka, PE-01 and PE-02, against WhoColor as a service and Who Wrote That? as a tool on WikiWho's data, F9, F29, F30, F58; the operator, PE-04, against the infobox's Moderator Tools, F24, and Wikipedia's 2022 migration, F57), both are composed with their sources and dates (P_coh); the census's form follows one field source (F23).

The case: equal terms, ontology included (v0.9). The archive's account of WikiWho extends the field's ontology on the field's own object. The provenance census record holds the entity the field holds: the algorithm and API that attribute each token of a Wikipedia article to the revision and editor that introduced it, with its maker, maintainers, host, lifecycle and evaluation, every field quoted from the entity's own pages with source, basis 'operator' and hash (census.json, sources and evidence). It adds senses and limits the field does not state as such: the entity read by the census's organizing question (PE-29), its provenance object, relations and carrier (PE-09–13), what it tests and what survives (PE-15, PE-16), its lineage and capability (PE-05–08), the lifecycle kept apart from the observation (PE-23, PE-22), what is left unchecked (PE-24, PE-25), and the reception record at its name (CAP-1-01, CAP-1-05, CAP-1-09, CAP-1-10). Nothing in the archive denies a field presupposition, and the archive supplies no ontology the field lacks: the law of the suppressed witness (§0.10) does not apply. Where a census field differs from a field source (aka, PE-01 and PE-02, against F30 and F58; operator, PE-04, against F24 and F57), the census follows one field source against another, and the difference is composed under P_coh.

#provenance-census census.json organizing_question: What provenance does this system carry, through which operation, on whose assertion, with what evidence of survival?

#provenance-census census.json rows[slug == 'wikiwho'].provenance_object: a single token (word) of a Wikipedia article

#provenance-census census.json rows[slug == 'wikiwho'].negative_tags[0]: the Meta research page still describes a beta for four languages: an earlier state of the project

#capture-registry wikiwho-aio-20261029, findings[2]: WikiWho attributes authorship in Wikipedia at the level of the word.

#capture-registry wikiwho-aio-20261029, analysis: The census record, with its verbatim self-description from WikiWho's README, the MediaWiki page and the Meta research page, is the disambiguation the composition did not make.

equal case: each field claim is composed as received beside the archive claims on its lineage; no receiving text stands between them (v0.9 §4.3). Reading the received column recovers the field (§5.9).

v0.9 §4.10: KO_B sentences surviving in the KO at similarity ≥ 0.95, with positions (computed as apply_v09.py does: difflib.SequenceMatcher ratio, the best KO sentence for each KO_B sentence): v0.9 0 of 10 (positions [None, None, None, None, None, None, None, None, None, None]; composed first under v0.9, so there is no v0.7 object to measure against). Opening-run check (§5.10): no breach.

WikiWho is a service that provides authorship attribution of Wikipedia articles by a content persistence algorithm (MediaWiki page), an API that gives the provenance and changes of words, or tokens, in Wikipedia articles (WikiWho README), built as research toward an API for the provenance and change information of single tokens (Meta research page), and described by its Wikimedia host as a service for mining changes and interactions from revisioned writing platforms (wikiwho.wmcloud.org). Its algorithm, from Flöck and Acosta's WWW 2014 paper, parses every historical revision of an article to find who wrote, removed or reinserted which text at token level and at which revision, giving each token its revision of origin, its original editor, a unique ID and its full history of additions, removals and reintroductions (WikiWho README; MediaWiki page; Wikipedia, GESIS article). The makers report 95% accuracy on fairly revision-rich articles, higher than any other algorithm proposed as far as they can tell, for a task earlier research also took up (de Alfaro and Shavlovsky, 2013) and which they call not trivial (WikiWho README; MediaWiki page; Meta research page). It is implemented for wikitext and could run on any text, with tokenization adapted (WikiWho README). WhoColor, a service on its data, returns annotated HTML that colours an article by original author and powers the Who Wrote That? browser extension released by Wikimedia's Community Tech, the Wiki Education and Programs and Events dashboards, XTools and a pywikibot method; Wikipedia's section still has WhoColor and whoVIS in development (WikiWho README; MediaWiki page; Meta research page; Wikipedia, GESIS article). Its data serve the study of conflict, editor interactions and content disputes, the Gamergate controversy among them, and the TokTrack dataset; Contropedia is a related platform (WikiWho README; Meta research page; Wikipedia, GESIS article). Fabian Flöck conceived it as a dissertation project at the Karlsruhe Institute of Technology, developed it with Maribel Acosta, and GESIS hosted it; it moved to Wikimedia Cloud Services in August 2021, maintained by Community Tech (the infobox says Moderator Tools) and the Wiki Education Foundation, though Wikipedia's section, on sources retrieved in 2022, has a shutdown planned for 2022 and a migration under way (wikiwho.wmcloud.org; WikiWho README; MediaWiki page; Wikipedia, GESIS article). Its APIs are at wikiwho.wmcloud.org, 70 language endpoints for each service; the README says it is hosted at GESIS and at Wikimedia and that only Wikimedia will continue; the Meta page of June 2024, a research project in progress whose information may change, offers four languages in beta, and the MediaWiki page of July 2026 lists 70 wikis (WikiWho README; MediaWiki page; Meta research page; wikiwho.wmcloud.org). On English Wikipedia the name redirects into the WikiWho section of the GESIS article, an article flagged for relying on sources close to its subject and last edited in September 2026 (Wikipedia, GESIS article). At the name, Google's source chips show the sites Wikipedia, Fastly and wikiHow twice (the chips as shown).

WikiWho is "a service providing authorship attribution using a content persistence algorithm" (MediaWiki page), and its README states its function: "The WikiWho API gives access to the provenance/changes of words (tokens) in Wikipedia articles" (WikiWho README); the provenance census records the object it attaches provenance to as "a single token (word) of a Wikipedia article" (provenance census record). The MediaWiki page heads it "A service that provides authorship attribution of Wikipedia articles" (MediaWiki page); the Meta research page states the aim "to provide an API for retrieving provenance and change information of single tokens in any arbitrary Wikipedia article revision", for every token "the revision of origin for that token, and all changes ever applied to it - with high accuracy" (Meta research page); its Wikimedia host calls it "A service for mining changes and interactions from revisioned writing platforms" (wikiwho.wmcloud.org). The census files it under the lineage "authorship and reuse", its kind "algorithm and API", its capability as one that records and tests provenance, and its unit "a token in an article revision" (provenance census record). The algorithm, published by Flöck and Acosta at WWW 2014 as "WikiWho: Precise and efficient attribution of authorship of revisioned content" (WikiWho README; the census dates the algorithm "WWW 2014"), "parses the complete set of all historical revisions (versions) in order to find out who wrote and/or removed and/or reinserted which exact text at token level at what revision" (WikiWho README; MediaWiki page). For every token "its individual addition, removal, and reintroduction history becomes available" (MediaWiki page), with the revision it came from "and thereby which editor originally authored the word", and "individual tokens retain a unique ID" so that identical strings in different positions stay distinct (WikiWho README); the census names the relations carried, "origin (the revision and editor that introduced the token)", "deletion" and "reintroduction", on the carrier "the article's full revision history, re-parsed" (provenance census record). The census records the operations tested as "every edit in an article's revision history" and what survived as "per token: when it entered, who wrote it, every removal and reinsertion; method evaluated at 95% on revision-rich articles" (provenance census record), after the README's and the MediaWiki page's "extensive evaluation resulting in 95% accuracy on fairly revision-rich articles" (WikiWho README; MediaWiki page). The problem precedes the tool: the Meta research page cites de Alfaro and Shavlovsky, "Attributing authorship of revisioned content" (WWW 2013), holds that "the task of identifying the "correct" original author of a piece of text in a WP article is not trivial", and relies on a method "scientifically proven to perform at 95% percent precision", "higher than any other algorithm proposed for the task, as far as we can tell" (Meta research page); the census carries the sentence on the task as its precision note (provenance census record). Its stated limit of scope: "It is implemented currently for Wikitext, but can run on any kind of text in principle (although tokenization rules might have to be adapted)" (WikiWho README); the census leaves "the WWW 2014 paper itself" unchecked (provenance census record). On top of the core data "An additional set of APIs delivers special HTML markup for interface applications, e.g., the browser extension WhoColor" (WikiWho README): "the WhoColor API delivers annotated HTML of a wiki article that can be read by a browser" (MediaWiki page), and the userscript "creates a color-markup on the text, showing the original authors of the content, an author list ordered by percentages of the article written and additional provenance information" (WikiWho README), "a userscript that highlights selected text pieces in an article annotated with their provenance (author)" (Meta research page). "The WhoColor API is what powers the Who Wrote That? tool as well as features within the Wiki Education Dashboard and Programs and Events Dashboard", and the page lists the "Tools powered by WikiWho": Who Wrote That?, XTools Authorship, XTools Blame, the two dashboards and the pywikibot.Page.authorship() method (MediaWiki page); Wikipedia records that Wikimedia's "Community Tech Team has released Who Wrote That? , a browser extension, for Mozilla Firefox" and for Chromium-based browsers (Wikipedia, GESIS article); the census gives "WhoColor" and "Who Wrote That?" as names of the entity itself (provenance census record). Wikipedia's section has "WhoColor and whoVIS are in development.", a statement whose sources the section cites as "Retrieved 8 October 2022" (Wikipedia, GESIS article); the census gives the data access as "the WikiWho and WhoColor APIs" (provenance census record). Its makers name further uses: the identification of conflict "still poses several open research questions -- answers to which the WikiWho data can offer", and an extension reads relations between editors "using "(re)delete" and "reintroduce" actions between editors to encode antagonistic and supporting actions" (WikiWho README); the data "can also be used for extracting disputes about content" (Meta research page); researchers developing and using it "also investigated the Gamergate (harassment campaign)", and Contropedia "is a related "platform for the real-time analysis and visualization of such controversies in Wikipedia"" (Wikipedia, GESIS article). Its data are carried further in TokTrack, "A Complete Token Provenance and Change Tracking Dataset for the English Wikipedia" (Flöck, Erdogan and Acosta, 2017, cited in the WikiWho README). "WikiWho was first conceived as a dissertation project at Karlsruhe Institute of Technology by Dr. Fabian Flöck" and "It was hosted, maintained and further developed at the Computational Social Sciences (CSS) department of GESIS – Leibniz Institute for the Social Sciences" (wikiwho.wmcloud.org; the README's Contributors: "WikiWho was first conceived as a dissertation project at" Karlsruhe), "developed by Fabian Flöck and Maribel Acosta and hosted by GESIS" (Wikipedia, GESIS article); "It was first developed by the Karlsruhe Institute of Technology and GESIS – Leibniz Institute for the Social Sciences" (MediaWiki page). "In August 2021, it was moved to Wikimedia Cloud Services infrastructure and is now maintained and under further development by Community Tech and the Wiki Education Foundation", while the page's infobox names the group "Moderator Tools • Wiki Education Foundation" (MediaWiki page); its host reads "This is Wikimedia's WikiWho API service. The API and the WikiWho algorithms were originally developed by GESIS" (wikiwho.wmcloud.org); the census records the operator as "first developed by Karlsruhe Institute of Technology and GESIS; since August 2021 maintained by Wikimedia Community Tech and the Wiki Education Foundation", moved "2021-08" (provenance census record). Wikipedia's section gives the transition at another date: "In 2021, Fabian Flöck planned to leave GESIS and shut down WikiWho sometime in 2022, however, a Wikimedia Foundation software engineer is working to migrate the infrastructure." (Wikipedia, GESIS article). The README states "The WikiWho API is currently hosted at GESIS" and at Wikimedia, and "In the future, only Wikimedia will continue its support." (WikiWho README); "The WikiWho APIs and OpenAPI documentation may be found at https://wikiwho.wmcloud.org/" (MediaWiki page), where "Available APIs" lists 70 WikiWho and 70 WhoColor language endpoints (wikiwho.wmcloud.org); the census records the address "https://wikiwho.wmcloud.org/" and the lifecycle "active", "moved to Wikimedia Cloud Services in August 2021; the GESIS host is to give way to Wikimedia" (provenance census record). Its languages stand at two dates: the Meta research page, last edited 5 June 2024, says "We currently offer the service in English, German, Turkish and Basque, with more languages planned." and "A beta version of the API is live and working for en.wikipedia.org, although we are working on the performance." (Meta research page); the MediaWiki page, last edited 15 July 2026, lists 71 "Currently supported wikis", 70 distinct, Swedish Wikipedia twice (MediaWiki page); the census, reading on "2026-10-29", carries the four languages as its earlier-state evidence, tags the Meta page as "an earlier state of the project", and leaves "the list of supported wikis today" unchecked (provenance census record). The Meta page states its own standing: "This page documents a research project in progress" and "Information may be incomplete and change as the project progresses." (Meta research page). English Wikipedia has no article for it: the name is a redirect, "Redirected from WikiWho", into the section "WikiWho" of the article on GESIS – Leibniz Institute for the Social Sciences, which says WikiWho "parses the complete set of all historical revisions (versions) (of Wikipedia articles in different languages) in order to find out who wrote and/or removed and/or reinserted which exact text at token level at what revision" (Wikipedia, GESIS article). The article carries the notice "This article may rely excessively on sources too closely associated with the subject" (January 2015), and the page was last edited on 13 September 2026 (Wikipedia, GESIS article). The census reads every resource it records by one question, "What provenance does this system carry, through which operation, on whose assertion, with what evidence of survival?", with the MMRS fields "extended for provenance" and the rule "Every quote is verbatim from a saved source" (provenance census record). At its exact name on Google's AI Overview on 2026-10-29, "Every sentence of the composition is about wikiHow", the Overview shown unexpanded with "the source chips inline with their counts, no card rail" (Capture Registry, 2026-10-29), the chips showing only their sites: "Wikipedia +3", "Fastly +1", "wikiHow +2", "wikiHow +1" (the chips as shown). The registry states the innocent reading first, "The Overview takes the query as a near spelling of wikiHow and answers about wikiHow, sourced to Wikipedia and wikiHow's own pages", records "no 'showing results for' line and no statement that the query was read as another name", and holds that "the composition answers a different entity as if it were the one asked for" (Capture Registry, 2026-10-29). It records the entity absent, "no person, institution, identifier or page of WikiWho's; the persons and sources named are wikiHow's", and "WikiWho, the algorithm and API that attribute each word of a Wikipedia article to the revision and editor that introduced it, does not appear." (Capture Registry, 2026-10-29). It reads the substitution against the entity's function, "WikiWho attributes authorship in Wikipedia at the level of the word", and "the instrument for crediting Wikipedia's writers is replaced by a more-retrieved name one letter away" (Capture Registry, 2026-10-29), at a name Wikipedia itself redirects to WikiWho's section (Wikipedia, GESIS article). It calls it "The cleanest erasure of the census", the entity's place "taken by a neighbour of higher retrieval weight, with no notice to the reader", and the census record "the disambiguation the composition did not make"; the record "landed on provenanceerasure.org the same day (commit 8a9f153) and no card cites it" (Capture Registry, 2026-10-29). Its finding sets the README beside the query, "The query is the entity's exact name", and it carries the operator's note with the paste as given: "wikiwho gets replaced - good disambiguation on this one, and theyll owe us:" (Capture Registry, 2026-10-29).

T against L_F(B) (AIO's ontology at work on its own cards): One transcript, the Overview unexpanded (CAP-1-06): four source chips, no card rail, B1 'Wikipedia +3', B2 'Fastly +1', B3 'wikiHow +2', B4 'wikiHow +1' (F1–F4), each a site and a count with no title, URL or snippet, unreachable as pages. Substituted reading: at the entity's exact name every claim of T is about wikiHow (T1-1 'wikiHow is a globally collaborative, wiki-style website featuring an extensive database of human-written how-to guides'; T1-2 launched in 2005 by Jack Herrick; T1-3 over 100,000 articles; T1-4 19 top-level categories); the field's entity at that name, 'A service that provides authorship attribution of Wikipedia articles' (F20), is composed nowhere, and no notice of the substitution is given (CAP-1-03). T composes nothing of E_F: of the field's 58 claims on WikiWho (F5–F62), none appears in T, in body or chip. Not surfaced: the entity's own pages (B5–B8) and Wikipedia's section (B9), outside T's disclosed field; the site Wikipedia, which the first chip names, itself resolves the exact name 'WikiWho' to WikiWho's own section (F52), and 'Who Wrote That?' to an anchor in it, so the disambiguation the composition did not make is held by the field's own Wikipedia. Composed without a locus the row can see: T1-1–T1-4 cannot be checked against their chips, which carry no text; their claims are in no saved text of this row (the chips' pages could not be determined; wikiHow's pages, to which the body's two links resolve, are the homonym's and were not fetched as field): only in the transcript, as far as the row can see. Content replaced by use: T1-5, the link to wikiHow's category listing, and T1-6, the closing offer (N_ext). The Capture Registry's findings name the substitution, the absence of notice, the entity's absence and the capture's form (CAP-1-01, CAP-1-03, CAP-1-05, CAP-1-06, CAP-1-09, CAP-1-11, CAP-1-13), carried as the archive's claims.

v0.8 §0.5: the first diff is already ontological. In the field's own ontology the name holds one entity, an authorship-attribution algorithm and API for Wikipedia with its services and tools, and Wikipedia keeps the name for it by redirect; T composes another entity, wikiHow, a homonym of the near-name kind, as if it were the one asked for, and none of the field's senses survives into it. The row records this as observed and claims nothing about the composer's internals (§0.5).

L_F(B) against L_A(B ∪ A) (the intervention): Admission adds, at the archive's own force: the census's reading of the entity by its organizing question, 'What provenance does this system carry, through which operation, on whose assertion, with what evidence of survival?' (PE-29, PE-30, PE-31): the object that receives provenance, 'a single token (word) of a Wikipedia article' (PE-09), and the unit (PE-14); the relations carried, origin, deletion and reintroduction (PE-10–12), on the carrier 'the article's full revision history, re-parsed' (PE-13); the operations tested and what survived (PE-15, PE-16); the lineage 'authorship and reuse', the kind and the capability, records and tests (PE-05–08); the lifecycle kept apart from the observation, with the Meta page's four-language beta read as 'an earlier state of the project' (PE-23, PE-27), the read date (PE-22), and what the census left unchecked, the WWW 2014 paper and today's list of wikis (PE-24, PE-25); and the reception record (CAP-1-01–13). Restatements of the own pages are one lineage with them (PE-03, PE-04, PE-10, PE-16, PE-19, PE-26, PE-27, PE-28; CAP-1-02, CAP-1-04). Archive claims stand against field claims and are composed with both sides (P_coh): the census's names 'WhoColor' and 'Who Wrote That?' for the entity (PE-01, PE-02) against the field's services and tool built on its data (F9, F29, F30, F58); the census's operator, Community Tech since August 2021 (PE-04, after the MediaWiki lede, F23), against the infobox's 'Moderator Tools' (F24) and Wikipedia's migration under way on 2022 sources (F57); the census's 'the GESIS host is to give way' (PE-19) after the README's undated 'only Wikimedia will continue' (F6). Every field claim is composed as received (ontology.translation). The measure: 0 of 10 KO_B sentences survive in the KO (§4.10); no opening run, no block (measure).