Glossary and Reference
fix(reference): Glossary/Reference Index Topic wasn't actually rendering — same wikilink-syntax bug as self-hosting (plain Markdown links in AUTO-GENERATED membership blocks instead of [[wikilinks]]), silently falling back to the flat category list since it shipped in commit 40b0c4a. Found via Opus's design review, verified directly, fixed both EN/ES (24 links each), confirmed live via curl. Scanned all other _index.md files — no other instances of this bug found.
@@ -30,46 +30,46 @@ forward, since both were already stale pointers, not real content. <!-- START-HERE-HIGHLIGHT: engine reads this block to render the single "start here" card (reuses the existing cluster-card--start-here component). Do not add more than one. --> **Start here:** [PointSav encyclopedia — glossary and lexicon](/wiki/glossary-documentation) — the canonical A-to-Z definition of every platform-specific term, the page most other articles link to on first use. **Start here:** [[glossary-documentation|PointSav encyclopedia — glossary and lexicon]] — the canonical A-to-Z definition of every platform-specific term, the page most other articles link to on first use. <!-- END-START-HERE-HIGHLIGHT --> ## Platform orientation <!-- AUTO-GENERATED MEMBERSHIP: DO NOT EDIT BELOW — regenerate from index_group: platform-orientation --> - [Getting started with the PointSav platform](/wiki/getting-started) — what the platform is, who it's for, and where to go first - [PointSav encyclopedia — glossary and lexicon](/wiki/glossary-documentation) — the canonical term-by-term definition source - [How this knowledge base is organized](/wiki/wiki-structure) — a reader's map of all thirteen documentation-wiki areas - [Developer guide index](/wiki/guide-catalog) — every how-to guide, grouped by developer concern - [Hardware reference](/wiki/hardware-reference) — reference hardware profiles for workstations and fleet devices - [SLM operationalization plan](/wiki/service-slm-operationalization-plan) — the plan for moving from external model calls to a per-tenant local model - [[getting-started|Getting started with the PointSav platform]] — what the platform is, who it's for, and where to go first - [[glossary-documentation|PointSav encyclopedia — glossary and lexicon]] — the canonical term-by-term definition source - [[wiki-structure|How this knowledge base is organized]] — a reader's map of all thirteen documentation-wiki areas - [[guide-catalog|Developer guide index]] — every how-to guide, grouped by developer concern - [[hardware-reference|Hardware reference]] — reference hardware profiles for workstations and fleet devices - [[service-slm-operationalization-plan|SLM operationalization plan]] — the plan for moving from external model calls to a per-tenant local model <!-- END AUTO-GENERATED --> ## General computing concepts <!-- AUTO-GENERATED MEMBERSHIP: DO NOT EDIT BELOW — regenerate from index_group: computing-concepts --> - [Application programming interface](/wiki/application-programming-interface) — how software systems communicate through a defined set of calls - [Computer appliance](/wiki/computer-appliance) — hardware and software sealed together for one well-defined function - [Edge computing](/wiki/edge-computing) — placing computation near the data it operates on, rather than in a central data center - [Fog computing](/wiki/fog-computing) — the layer of compute and storage between edge devices and the cloud - [Just enough operating system](/wiki/just-enough-operating-system) — reducing the OS to only what a specific application needs - [Lightweight linux distribution](/wiki/lightweight-linux-distribution) — Linux builds engineered for far less RAM and CPU than a full distribution - [Virtual appliance](/wiki/virtual-appliance) — a pre-configured VM image combining a minimal OS with one application - [Security through obscurity](/wiki/security-through-obscurity) — why secrecy of design is not treated as a security mechanism here - [User experience design](/wiki/user-experience-design) — the discipline covering every aspect of a user's interaction with a product - [User interface design](/wiki/user-interface-design) — designing the human-machine interface itself, governed by ISO 9241 - [[application-programming-interface|Application programming interface]] — how software systems communicate through a defined set of calls - [[computer-appliance|Computer appliance]] — hardware and software sealed together for one well-defined function - [[edge-computing|Edge computing]] — placing computation near the data it operates on, rather than in a central data center - [[fog-computing|Fog computing]] — the layer of compute and storage between edge devices and the cloud - [[just-enough-operating-system|Just enough operating system]] — reducing the OS to only what a specific application needs - [[lightweight-linux-distribution|Lightweight linux distribution]] — Linux builds engineered for far less RAM and CPU than a full distribution - [[virtual-appliance|Virtual appliance]] — a pre-configured VM image combining a minimal OS with one application - [[security-through-obscurity|Security through obscurity]] — why secrecy of design is not treated as a security mechanism here - [[user-experience-design|User experience design]] — the discipline covering every aspect of a user's interaction with a product - [[user-interface-design|User interface design]] — designing the human-machine interface itself, governed by ISO 9241 <!-- END AUTO-GENERATED --> ## Editorial and publishing standards <!-- AUTO-GENERATED MEMBERSHIP: DO NOT EDIT BELOW — regenerate from index_group: editorial-standards --> - [Editorial language registers](/wiki/editorial-language-registers) — the three prose registers this wiki writes in, matched to audience - [Editorial philosophy](/wiki/editorial-philosophy) — why every article teaches understanding rather than just retrieving facts - [News release typography and layout standards](/wiki/news-release-standards) — formatting rules for corporate news syndication - [Preprint notice](/wiki/preprint-notice-convention) — what the mandatory notice on a working research paper actually means - [Root files discipline](/wiki/root-files-discipline) — the canonical, enumerated set of files every repository root keeps - [Structural positioning](/wiki/structural-positioning) — how this platform differentiates without naming competitors - [Wiki provider landscape](/wiki/wiki-provider-landscape) — a structural audit of why no existing provider has closed Wikipedia's gap - [[editorial-language-registers|Editorial language registers]] — the three prose registers this wiki writes in, matched to audience - [[editorial-philosophy|Editorial philosophy]] — why every article teaches understanding rather than just retrieving facts - [[news-release-standards|News release typography and layout standards]] — formatting rules for corporate news syndication - [[preprint-notice-convention|Preprint notice]] — what the mandatory notice on a working research paper actually means - [[root-files-discipline|Root files discipline]] — the canonical, enumerated set of files every repository root keeps - [[structural-positioning|Structural positioning]] — how this platform differentiates without naming competitors - [[wiki-provider-landscape|Wiki provider landscape]] — a structural audit of why no existing provider has closed Wikipedia's gap <!-- END AUTO-GENERATED --> ## What this is not