4. Glossary and Normative Language
Glossary and Normative Language requirements from the authoritative Glitchpad Technical Specification.
The key words MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, and MAY are interpreted as requirement levels consistent with RFC 2119 and RFC 8174 when capitalized.
| Term | Definition |
|---|---|
| Capability | One independently advertised operation such as view, edit, save, search, navigate, zoom, print, copy, or inspect |
| Document identity | The strongest stable host identity available for duplicate detection and external-revision tracking |
| Document session | Runtime state for one open source, renderer, tab, navigation state, editable buffer, and recovery relationship |
| Document source | A native source handle plus explicit read, seek, metadata, watch, permission, and write capabilities |
| External revision | Host-observed facts used to determine whether a source changed outside the session |
| Foundation | Normative design exists, but no released application artifact implements the capability |
| Host | The platform adapter that acquires and persists sources and owns native authority |
| Metadata fact | A typed value with provenance, availability, sensitivity, and copy policy |
| Mermaid diagram document | Standalone .mmd or .mermaid text source with rendered and source modes; Mermaid is its own diagram language and is also commonly embedded in Markdown fences |
| Planned | A versioned roadmap target with no current support claim |
| Renderer | An internal format module implementing the renderer contract and no broad native authority |
| Stable | Supported in official artifacts and covered by release-blocking evidence |
| Experimental | Available behind an explicit label with documented limitations and non-stable compatibility |
| Release documentation pass | Blocking reconciliation of completed Spec Kit slices and shipped behavior into release-facing records |
Notes and rationale are non-normative. Tables labeled as matrices are normative unless their heading states “informative.” Roadmap version targets are commitments subject to the same feature and release gates as any other behavior; they are not current support claims.