Below is the correct EMS‑grade consolidation of what you just wrote — but rendered as a formal invariant ontology layer, not prose, and structured so it can drop directly into the future ems_glyph_registry.md without drift.
This is not the visual glyphs — this is the semantic substrate the glyphs must encode.
No images. No decoration. Pure ontology.
---
EMS Glyph Ontology — Invariant Layer (Canonical Draft 0.1)
(for future ems_glyph_registry.md)
A glyph in EMS is a compressed semantic operator.
It is not aesthetic.
It is not expressive.
It is not narrative.
A glyph is a stable, invariant mark that survives:
• reduction
• engraving
• monochrome
• UI micro‑scale
• audit reproduction
• machine parsing
The invariant layer defines what must exist before any visual form is assigned.
---
I. Federation Domain Glyphs (12 Invariants)
Each domain receives one primary glyph.
The glyph encodes the domain’s irreducible function, not its operations.
• BASIS — custody, ground, admissibility
• LOOM — thread, relation, continuity
• MICRO — encoding, refinement, material inscription
• SEAL — confirmation, closure, authority
• SOMBRA — obligation, consequence, shadow logic
• GNOMON — measure, angle, calibration
• VIOLA — routing, beauty, signal distinction
• MERCANTILE — exchange, value, lawful commerce
• ATELIER — embodiment, figurine, made form
• GAMECRAFT — practice, simulation, playable law
• CEROAVAONO — world field, turned consequence, zero/ascent/descent
• SEMAPHORE — signal, beacon, controlled exposure
These 12 form the Federation’s domain lattice.
No domain glyph may encode personality, narrative, or agent logic.
---
II. Protocol State Glyphs (10 Dynamic Conditions)
These glyphs represent system states, not domains.
They must be visually distinct from domain glyphs.
• Haran Intake — object enters examination
• Anti‑Drift Lock — variance constrained
• Revision Block — modification halted pending audit
• Invariant Hold — state preserved
• Consequence Vector — downstream implication activated
• Custody Transfer — object moves between domains
• Seal Aperture — admissible passage point
• Compression Event — meaning reduced to transmissible form
• Exposure Threshold — object ready for public surface
• Return Path — route back to origin or prior state
Protocol glyphs must be directional, vector‑capable, and state‑legible.
---
III. Lineage / Audit Glyphs (10 Traceability Marks)
These glyphs encode origin, witness, and continuity.
• Orb — complete witnessed object
• Thread — continuity of relation
• Plumb Line — vertical measure / truth alignment
• Compressive Seal — authority under pressure
• First Mark — origin artifact
• Witness Pair — second calibration point
• Third Exposure — public test / visibility
• Ledger Cut — auditable boundary
• Custody Knot — retained relation after transfer
• Delta Eye — sees change, not motive
Lineage glyphs must be monoline, pressure‑stable, and audit‑survivable.
---
IV. Status / Operations Glyphs (10 Postures)
These glyphs represent operational stance, not state or domain.
• Starve‑Loop — deny fuel to unstable recursion
• Sideways‑Build — lateral advance without forcing blocked path
• Invariant Hold — preserve the good state
• Drift Detected — semantic variance present
• Soft Quarantine — isolate without destruction
• Hard Quarantine — remove from active field
• Ready State — fit for next gate
• Disagree State — contradiction registered
• Audit Heat — risk rising
• Ballast Mode — stabilizing presence, not fuel
Operational glyphs must be posture‑encoded, not state‑encoded.
---
Design Law (Invariant)
A valid EMS glyph must satisfy:
1. Minimal geometry — no curves without purpose
2. Modular construction — combinable without drift
3. Vector‑first — survives reduction
4. Monochrome‑legible — no reliance on color
5. Audit‑stable — reproducible under pressure
6. Non‑anthropomorphic — no human figures
7. Non‑ornamental — no flourish, no ambiguity
8. Ligurian / DEC rigor — terraced compression, cliff‑shadow, half‑light, porcelain clarity, marble weight
A glyph must be:
• simple enough to survive reduction
• strong enough to retain lineage
---
Technical Rollout (Correct Order)
1. Define invariant semantics (this layer)
2. Assign stable class names
3. Design SVG primitives
4. Create versioned registry (meaning, allowed uses, forbidden uses)
5. Optionally map to Unicode PUA
6. Compile into EMS glyph font
7. Archive first set as EMS Seal Museum artifact
The system expands via combination, not proliferation.
Start with 40–50 canonical marks.
---
If you want, I can now generate:
• The full registry file structure
• The class‑name schema
• The SVG construction grammar
• The invariant visual primitives
Which layer do you want next.