Glossary and Reference

@@ -1,37 +1,61 @@
---
schema: foundry-doc-v1
title: "Reference — Category Landing"
title: "Reference"
slug: _index
category: reference
type: reference
quality: complete
short_description: "Definitional materials for contributors across all audiences: style guides for each document genre, editorial philosophy, BIM and real-property reference corpus, glossary, and platform-specific terminology."
status: active
bcsc_class: public-disclosure-safe
last_edited: 2026-04-29
last_edited: 2026-05-15
editor: pointsav-engineering
paired_with: _index.es.md
---

## Reference
Reference articles are looked up, not read front to back. Each article defines a bounded domain — what a term means, how a document genre is structured, what industry standards apply to a specific workflow. When an article in another category introduces a term or cites a standard, the canonical definition or context is in this category.

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.
## Style guides

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.
How each document genre is structured, what register is appropriate, and how English and Spanish pairs relate.

## Articles in this category

- [[style-guide-readme]] — How to write a README: the bilingual convention, the required sections, and the register appropriate for each audience.
- [[style-guide-topic]] — How to write a TOPIC article: frontmatter schema, body structure, wikilink syntax, and the relationship between English and Spanish pairs.
- [[style-guide-topic]] — How to write a TOPIC article: frontmatter schema, body structure, wikilink syntax, and the bilingual pairing convention.
- [[style-guide-guide]] — How to write a GUIDE runbook: the operational register, command blocks, recovery procedures, and the catalog vs instance distinction.
- [[style-guide-architecture]] — How architecture articles are structured and what distinguishes them from TOPIC articles.

<!-- 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. -->
## Editorial philosophy and standards

## See also
The principles and voice guidelines that govern all content on this wiki.

- [[editorial-philosophy]] — The editorial principles behind PointSav's documentation: institutional register, the Bloomberg four-paragraph lede, and the CFO sentence test.
- [[editorial-language-registers]] — The four language-register families (PROSE, COMMS, LEGAL, TRANSLATE) and how they route editorial work through the platform's adapter taxonomy.
- [[structural-positioning]] — How the platform positions itself without naming competitors; the rules that govern comparative statements.
- [[news-release-standards]] — Standards for news releases and BCSC-compliant continuous-disclosure communications.

## BIM and real-property reference

Reference materials for Building Information Modelling and real-property workflows.

- [[bim-aec-muscle-memory]] — AEC industry muscle memory: the standard locations, conventions, and interface patterns a PointSav deployment maps onto.
- [[bim-design-philosophy]] — Design philosophy for BIM tooling: why flat-file ISO 19650 records rather than hosted databases.
- [[bim-market-context]] — Market context for the BIM software industry: regulatory landscape, adoption patterns, and structural positioning.
- [[bim-token-taxonomy]] — The token taxonomy for BIM design-system primitives.
- [[bim-token-three-layers]] — The three-layer token model applied to BIM: primitive, semantic, and component layers.
- [[bim-token-what-it-is]] — What a BIM design token is and why the field uses them.
- [[open-bim-regulatory-acceptance]] — The regulatory landscape for open BIM standards: IFC, ISO 19650, and their adoption by national building authorities.

- [Wiki home](/)
- [Help](/help/)
- [Governance](/governance/)
## Glossary and terminology

- [[glossary-documentation]] — The master glossary of PointSav platform terms: canonical definitions, disambiguation notes, and cross-references.
- [[hardware-reference]] — Hardware specifications and reference configurations for PointSav deployments.
- [[root-files-discipline]] — The canonical set of files permitted at a repository root and how misplaced files are handled.

## Operational reference

- [[service-slm-operationalization-plan]] — Operationalization plan for service-slm: the rollout sequence, evaluation criteria, and go/no-go gates.
- [[wiki-provider-landscape]] — The landscape of wiki and documentation platforms; where PointSav's approach fits relative to the field.

## See also

<!-- 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. -->
- [Governance](/governance/) — formal decision records and compliance posture
- [Design System](/design-system/) — visual and component design reference