Icon Lexicon (Category-First)

A category-first icon set for documentation, architecture diagrams, and minor website usage.
The UI/app can choose any variant within a category (emoji, Lucide, FontAwesome, SVG, etc.).


🏛️ Architecture & Structure

Use for: architecture, system shape, standards, foundations, composition, “built environment”

Suggested consistent meanings (optional):


🗺️ Context, Landscape & Navigation

Use for: bounded context, scope, domain map, routes, “where does this live?”

Suggested meanings (optional):


📚 Knowledge, Docs & Reference

Use for: documentation, ADRs, standards, how-tos, “institutional memory”

Suggested meanings (optional):


📜 Contracts, Specs & Interfaces

Use for: OpenAPI, schemas, events, SLAs, “this is the agreement”

Suggested meanings (optional):


🧩 Components, Modules & Boundaries

Use for: services, packages, modules, slices, assemblies

Suggested meanings (optional):


🌀 Flow, Lifecycle & Dynamics

Use for: pipelines, orchestration, state changes, eventing, async

Suggested meanings (optional):


💧🔥🌱 Nature Metaphors (Energy, Growth, Risk)

Use for: capacity, “heat”, stability, maturity, resilience, evolution

💧 Stability / Cooling / Calm

🔥 Heat / Risk / Urgency

🌱 Growth / Maturity / Sustainability

☀️🌙 Visibility / Diurnal cycles

🌬️ Wind (Change / Variability)

Suggested meanings (optional):


🌐 World & Worldbuilding (Scope, Terrain, Externalities)

Use for: environments, regions, external deps, geography metaphors, “the world outside the system”

Suggested meanings (optional):


🛡️ Security, Trust & Compliance

Use for: authn/authz, secrets, privacy, policy enforcement


🧪 Quality, Testing & Verification

Use for: tests, validation, correctness, confidence


📦 Delivery, Ops & Observability

Use for: CI/CD, deploys, runtime, telemetry, incidents


Canonical Meaning Set (Optional)

If you want a small set that’s always consistent: