Fred Edison Registry

Standards

Normative rules for names, versions, stability, and submissions. This page is canonical; narrative and discussion live on frededison.org.

Naming

• Use PascalCase or TitleCase for glyph names (e.g., Ariadne, Hephaestus).
• Names are globally unique; avoid punctuation and spaces.
• Provide a concise role (one‑line description) for the registry table.

Versioning

• SemVer‑style: MAJOR.MINOR.PATCH (e.g., 1.0.0).
• Increment MAJOR for breaking scope or contract changes.
• Increment MINOR for additive capability under the same charter.
• Increment PATCH for fixes or small, backward‑compatible improvements.

Stability

One of: experimental → alpha → beta → stable.

• experimental — rapid change; assumptions in flux.
• alpha — core loop works; significant change expected.
• beta — feature‑complete; stabilizing behavior and docs.
• stable — rare changes; requires explicit review.

Submission Rules

1. Prepare the registry fields: name, role, version, stability, last_review, and optional slug.
2. Propose changes on frededison.org or via a glyph handoff.
3. On approval, update /data/registry.json and publish any page content.
4. Record actions in the ledger with appropriate tags (e.g., REGISTRY,DATA or TEXT,STANDARDS).

Compliance

Entries that don’t meet naming/versioning/stability rules are not canonical. The registry is facts‑first and enforced by review.