1. Document Control and Authority
Document Control and Authority requirements from the authoritative Glitchpad Technical Specification.
This document is the architecture, behavior, platform, security, development, and delivery contract for Glitchpad v0.1.4, the fourth corrective successor to the first installable community release. Its version MUST equal the product version.
The root Rust workspace version becomes the canonical product-version authority when the repository-foundation slice creates application manifests. Tauri configuration, npm package metadata, Android version name, this document, changelog release heading, release tag, artifact filenames, SBOM metadata, and provenance attestations MUST mirror that value. Automated consistency checks MUST reject any mismatch.
Issued records the date this specification was first published. It remains stable across corrective revisions. Updated records the effective date of the current specification text and MUST equal the date of the latest revision-history entry.
Unreleased changes belong in numbered Spec Kit feature directories under specs/. A completed feature does not alter the latest-release architecture of record until a release documentation pass reconciles it into this document. The pass MUST review every completed slice since the prior release, update affected architecture and behavior, revise capability and platform matrices, update contributor prerequisites and security posture, assemble changelog fragments, regenerate notices, and produce a reviewed documentation-pass receipt before the release tag is created.
flowchart TB
change["Product decision or behavior change"] --> feature["Spec Kit feature specification"]
feature --> design["Clarification, plan, contracts, and tasks"]
design --> implementation["Implementation and mapped verification"]
implementation --> docsPass["Release documentation pass"]
docsPass --> consistency{"Versions, behavior, claims, and notices agree?"}
consistency -->|No| blocked["Release blocked"]
consistency -->|Yes| release["Official vX.Y.Z release"]Revision history
| Specification | Date | Product release | Change |
|---|---|---|---|
| 0.0.0 | 2026-08-30 | 0.0.0 | Established the product, architecture, platform, security, contributor, license, release, and standalone/embedded Mermaid baseline |
| 0.1.0 | 2026-09-07 | 0.1.0 | Reconciled the stable text-family application, four-platform packages, community trust policy, and first publication gate |
| 0.1.1 | 2026-09-08 | 0.1.1 | Reconciled the S027 content-first interface correction and the governed corrective-release transaction |
| 0.1.2 | 2026-09-09 | 0.1.2 | Reconciled public presentation and brand corrections, Markdown rendering resilience, stable menu placement, README cleanup, and Android provider-backed file delivery |
| 0.1.3 | 2026-09-11 | 0.1.3 | Reconciled universal Markdown recovery, reserved shell chrome, sectioned public specification documentation, automated post-merge housekeeping, and exact-package practical-use evidence |
| 0.1.4 | 2026-09-29 | 0.1.4 | Reconciled the BrandBuilder 2.0.3 kit, AppFrame shell geometry, refreshed web and Android brand assets, and compatible dependency updates while keeping image-format activation at the v0.2.0 gate |
Changes to normative released behavior require a product release and a matching specification version. Typographical corrections that do not alter meaning may be applied to the current version with a dated revision-history note and reviewed pull request.