Fred Edison Registry
The Canonical Record
Glyph Lexicon
Authoritative definitions used across the Registry and Standards. Terms are stable; updates are recorded in the ledger.
- APP glyph
- An application surface backed by glyphs (web/mobile/CLI). Honors charter and stability; emphasizes delivery and accessibility.
- charter
- The scope and constraints a glyph must operate within. Requests outside charter should be declined or escalated.
- composite glyph
- A higher-order glyph that composes multiple glyphs behind one interface and charter.
- glyph
- A named, reviewable capability with a clear charter, version, and stability, accountable to the Registry.
- governance
- Processes and roles that maintain naming, versioning, and standards; decisions are logged to the ledger.
- interactive glyph
- Engages in a dialog loop with users or systems; composes services and mechanics while preserving intent.
- mechanical glyph
- Infrastructure/tooling-level capability. Narrow scope; deterministic inputs/outputs.
- registry
- The canonical, read-only list of chartered glyphs and their properties. Source of truth for names and versions.
- service glyph
- Exposes capability over an interface; receives requests and returns results reliably.
- stability
- Lifecycle indicator: draft (in flux), stable (backward-compatible), legacy (superseded, maintained minimally).
- submission workflow
- Procedure to propose, review, and publish a glyph. On approval, the Registry and site content are updated and logged.
- TLL (Trust Layer Ledger)
- Provenance layer capturing who/what/when for significant events; powers public ledger and status.
- version
- Semver-style identifier (
major.minor.patch). Major changes may require new entries or clear deprecation paths.