chemenu/work/link-taxonomy-migration/glossary.md

Glossary: link-taxonomy-migration

Vocabulary decided while processing one page, carried forward so u3 (concepts) and u2 (projects/people/comparisons) do not re-decide it. Add to this file before dispatching the next unit or sub-session.

Unit sizing correction (2026-09-02)

u1 as written in plan.md (kb/entities/systems, tools, technologies, estimated ~45 pages) is actually 57 pages carrying 199 related: entries (systems 6/19, technologies 20/69, tools 31/111). At one wikitool call per edge (no bulk mode exists for xref add/xref remove), that is far past the 60-call session ceiling. Decided with the user: run u1 as planned in scope (all three areas, one eventual publish), but as per-area sub-sessions, each under its own WIKITOOL_SESSION_ID, holding index rebuild/lint/log append/publish until every area is done:

• link-taxonomy-migration/u1 - systems (done, see below)
• link-taxonomy-migration/u1-technologies - technologies
• link-taxonomy-migration/u1-tools - tools

Recurring pattern: reverse-reading edge, correct statement already elsewhere

Several old bullets read true only backwards, and the correct forward statement already exists (as still-unmigrated prose) on the other page - sometimes in a collection this unit does not touch. Rule applied: drop the backward one from the current page's related: (via xref remove, so it stops showing as an unlabelled edge) and note the correct edge here for whichever unit owns the other page. Never invert the label to fake the direction.

Deferred edges for later units, discovered while processing systems:

• u3 (concepts): Denylist over Allowlist invokes-or-operates-on AGENTS.md (its own body already says "beruft sich auf: AGENTS.md" - pick the label when concepts' outbound set is in front of you).
• u3 (concepts): LLM Wiki Pattern derived-from-or-abstracted-from Memex (Memex's old "Geistiger Vorgänger von" bullet reads backwards from Memex's side).
• u2 (people): Vannevar Bush owns Memex (Memex's "Erfunden von" bullet is owns's unlabelled inverse; owns has no catalogue inverse, so it must be authored from Bush's page).
• u2 (people): E3DC GmbH owns E3DC (same reasoning: owns has no inverse to assert from the owned entity's side).
• u2 (projects): no action needed on ha-core/hacs-e3dc - E3DC's page independently asserts required-by (a real pair with a genuine inverse), which already covers the relationship without needing anything written on the project pages.

Label choices worth reusing

• A file that is normative because a tool enforces it (AGENTS.md vs. wikitool) is depends-on, not implements/mechanism - those realization labels are entities-to-concepts only, and these pages are both entities.
• An optional dependency that the source tolerates the absence of (CLAUDE.md's @ENVIRONMENT.md import) is uses, not depends-on - the catalogue's own test ("does removing the target break this thing?") answers no.
• A root file that another root file's own prose defines the rules for (AGENTS.md defines what ENVIRONMENT.md is and is allowed to contain) is owns from the defining page, not asserted back from the defined one (no inverse exists).
• A hardware/software pairing where the dependent side is a specific integration package, not the general platform (E3DC vs. ha-core/hacs-e3dc vs. Home Assistant broadly): assert required-by from the depended-upon entity's page, and do not manufacture an edge to the broad platform if no specific claim holds there.
• A device supporting a communication standard: implements reads fine even outside pure software (E3DC implements Modbus).
• Two entities in the same wiki cited as parallel real-world examples of the same concept, with no sharper label fitting: see-also is correct and not a cop-out (Memex/Tolkien Gateway).