Glossary and Reference

Where to start

Thirteen pages sit here, and most readers want exactly one of them. These five are the ones reached for most often: the lexicon, two orientation maps, the guide index, and the register standard this wiki holds its own writing to.

• Glossary and lexicon — The A-to-Z definition of every platform-specific term, and the page most other articles link to on first use.
• How this knowledge base is organized — The sixteen areas and what belongs in each; the map to read before browsing categories.
• Getting started with the PointSav platform — Orientation for a reader who has not picked a starting point yet: the main surfaces and how they fit together.
• Developer guide index — Every how-to guide grouped by task, for a reader who already knows what they need to do.
• Editorial language registers — The three registers the PointSav wikis are written in, and which reader each one serves.

Platform orientation

• Getting started with the PointSav platform — An orientation to the PointSav developer platform: what it is, who it is for, where to start, and how the pieces fit together before the first task.
• PointSav encyclopedia — glossary and lexicon — A canonical A-to-Z lexicon bridging standard industry terminology with PointSav platform concepts, with authoritative definitions across technical and financial domains.
• How this knowledge base is organized — A reader's map of the platform knowledge base: sixteen areas covering what PointSav builds, how it's built, and why it can be trusted, for every reader.
• Developer guide index — Developer guide index for the PointSav platform — task-oriented how-to guides organised by concern, from toolchain setup to session lifecycle.
• Hardware reference — Reference hardware profiles for developer workstations and fleet devices, specifying CPU requirements including Haswell-generation x86_64 and fsgsbase support.
• SLM operationalization plan — The plan for transitioning from externally hosted language model calls toward a per-tenant small language model substrate that heals via a feedback loop.

Editorial and publishing standards

• Editorial language registers — Three distinct language registers matching the PointSav wikis to their audiences: financial-press, developer-platform, and regulatory-specification prose.
• Editorial philosophy — Every article is a learning resource that teaches understanding rather than retrieving facts, structured with encyclopedic leads and internal linking for readers.
• News release typography and layout standards — Strict formatting rules for corporate news syndication: left alignment, title case discipline, geographic precision, and standardized header and dateline structures.
• Preprint notice — What the mandatory preprint notice on every research paper means: a working draft, not yet peer-reviewed, subject to revision, and not a final or authoritative account.
• Root files discipline — The convention that every repository and project sub-clone keeps a small, explicitly enumerated set of canonical companion files at its root — and nothing else.
• Structural positioning — Structural positioning is PointSav's approach to market differentiation: architectural commitments visible in code and topology, not named-competitor comparisons.
• Wiki provider landscape — A structural audit of the wiki-shaped knowledge-surface market by archetype, documenting why no category of provider has closed Wikipedia's encyclopedic gap, and what closing it would require.

For a specific term, go to the glossary directly. Architectural terms are defined with their subject, not listed here.

See also

• Background — general computing concepts defined from first principles, for reading through rather than consulting
• Architecture — where architectural terms are defined in context, not just listed
• Core Concepts — the reusable mechanisms this wiki's vocabulary describes
• Platform Tasks — procedural guides that assume this vocabulary