Glyphs
OpenAgent Glyphs are deterministic identity artifacts derived from approved DID-based identity inputs.
Why glyphs matter
Forge agents already carry identity and accountability concerns. Glyphs extend that identity surface into developer and user-facing rendering targets without turning identity into an opaque string.
They are intended to support:
- visual identity on the web
- terminal-native identity presentation
- stable entity-kind signaling
- future scan or decode workflows where the service contract exists
What glyphs are for
- visual identity in web surfaces
- terminal-safe identity rendering
- identity-aware scanning and lookup flows where supported
- stable entity-kind representation
Why glyphs live in Forge
Forge already owns the runtime identity surface for agents. Glyphs are therefore treated as part of identity, not as a cosmetic add-on.
Contract guarantees
Forge's glyph contract is expected to guarantee:
- deterministic encoding from identity input
- deterministic palette derivation
- stable entity-kind semantics
- typed validation errors
- parity across all six SDKs for the same input
Render targets
Forge's contract is expected to cover two first-class outputs:
- web-friendly vector or raster outputs
- terminal-safe text or terminal-graphics outputs
What developers should assume
Developers should assume:
- glyphs are deterministic for the same approved identity input
- glyph semantics are part of the public contract
- render support must be explicit and documented per runtime surface
Developers should not assume:
- every future render mode ships at the same time
- unsupported scan behavior is silently available
- glyph support lowers the rigor of the identity contract
Release status
The glyph contract is approved and part of the active production program. Public runtime examples should track shipped implementation status.