The served surfaces
| Surface | URL | What it is |
|---|---|---|
| Icon catalog | https://nika.sh/brand/icons/<namespace>-<name>.svg | One SVG per entity (e.g. verb-infer · builtin-fetch · state-recovered) |
| JSON ontology | /brand/icons.json | Labels, semantics, hue tokens, effects and links for every entity |
| RDF projection | /brand/icons.ttl | The same graph in Turtle — SPARQL-ready, namespace nkd: |
| Identity kit | /brand/ + BRAND.md | The butterfly-supernova marks, lockups, tiles and usage rules |
<namespace>/<name> across seven namespaces: verb ·
builtin · feature · state · ui · social · anim. The builtin
entries track the -builtin stdlib — the ontology is
parity-gated against the spec canon, so a new builtin cannot ship without
its icon.
The color law
The four verb hues mean a run is alive — they appear only on live-run surfaces (an executing DAG, a replay). Static UI renders every icon in the surrounding text ink. If you consume the catalog, keep that rule: it is what makes color a signal instead of decoration.| Verb | Hue |
|---|---|
infer | blue #5b8cff |
exec | orange #ff7a3c |
invoke | cyan #22d3ee |
agent | violet #b07bff |
Motion
Theanim/* entities define the dot-matrix motion register: each verb’s
pattern is its execution model — infer samples (a sparkle emerges from
seeded noise), exec scans like stdout, invoke round-trips, agent
orbits its bounded loop. The pattern names and parameters ride
icons.json; the reference renderer lives in the
site source.
Querying the ontology
The Turtle projection answers SPARQL. For example, every builtin and its glyph:nkd:Verb · nkd:Builtin · nkd:Feature · nkd:RunState ·
nkd:UiGlyph · nkd:SocialMark · nkd:Animation. Relations worth
knowing: nkd:parent (every builtin points at verb/invoke — everything
callable is a tool reached through invoke:), nkd:sharesGlyphWith
(deliberate glyph reuse, e.g. the compose builtin and the check feature
share the shield — same oracle), and nkd:hueToken (the CSS custom
property a hue rides on the official surfaces).