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.
Style guides
How each document genre is structured, what register is appropriate, and how English and Spanish pairs relate.
- 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.
Editorial philosophy and standards
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 typography and layout 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.
Glossary and terminology
- PointSav encyclopedia — glossary and lexicon — 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
- 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
- Governance — formal decision records and compliance posture
- Design System — visual and component design reference