Glossary and Reference
Merge project-language cluster content into vendor main — sync 30+ TOPIC/bilingual pairs committed by Root and project-language Task
@@ -0,0 +1,36 @@ --- schema: foundry-doc-v1 title: "Reference — Category Landing" slug: _index category: reference status: pre-build last_edited: 2026-04-29 editor: pointsav-engineering --- ## Reference This category holds the definitional materials that contributors across all audiences use when writing or reviewing content: the glossary of platform terms, the nomenclature matrix that governs how entities are named, and the style guides that describe how each document genre is written. Reference articles are not narrative — they are looked up, not read front to back. Each article defines a bounded domain: what a term means, what prefix identifies an entity type, how a README differs from a TOPIC in structure and register. The reference category is the source of truth that all other articles in this wiki are expected to conform to. When an article in another category introduces a term, the canonical definition is in this category. ## Articles in this category - [[topic-style-guide-readme]] — How to write a README: the bilingual convention, the required sections, and the register appropriate for each audience. - [[topic-style-guide-topic]] — How to write a TOPIC article: frontmatter schema, body structure, wikilink syntax, and the relationship between English and Spanish pairs. - [[topic-style-guide-guide]] — How to write a GUIDE runbook: the operational register, command blocks, recovery procedures, and the catalog vs instance distinction. <!-- ENGINE: this list is editorial in iteration-1; iteration-2+ generates it from category-directory file listing once PL.7 chunked-migration moves articles into category subdirectories. --> ## See also - [Wiki home](/) - [Help](/help/) - [Governance](/governance/) <!-- EDITORIAL NOTE: PL.7 chunked normalization sweep will migrate root-prefixed TOPICs into this category subdirectory. Until migration lands, the existing root TOPICs render at their current URLs (topic-<slug>.md); this landing references them by current slug. -->