Referencing Attributes via Project-Unique Slugs in API and Schema Workflows

Dynamic Entity-Attribute-Value (EAV) architectures rely on immutable UUID identifiers to map entity attributes across dynamic schemas. While UUIDs guarantee collision-free uniqueness across multi-tenant data structures, requiring raw database keys in client payloads introduces unnecessary friction. Application developers, ingestion scripts, and automated pipelines must execute pre-flight schema lookups or hardcode internal IDs into application code before transmitting data.

Omnismith resolves this coupling by introducing string-based attribute aliases through project-unique slugs. Attributes can now accept an optional slug (attribute_slug), allowing API write payloads, entity search filters, metric telemetry streams, and schema management workflows to reference fields using human-readable names.

Attribute Identifier Resolution

Attribute definitions can be assigned a slug during initial creation or through subsequent schema updates. Slugs are scoped to their active project, allowing different projects to use identical, intuitive slug names (such as sku or product_title) without collision.

When interacting with entity endpoints, Omnismith accepts a lightweight attributes dictionary keyed by attribute slugs or UUIDs. Values are automatically type-cast and validated against the template schema:

{
  "attributes": {
    "product_title": "Ergonomic Mechanical Keyboard",
    "sku": "KB-ERG-01"
  }
}

The payload resolver evaluates attribute slugs and canonical attribute UUIDs interchangeably. Both can be mixed freely in a single request, providing ergonomic developer experience without sacrificing schema guarantees.

Entity Operations and Metric Ingestion

Support for attribute_slug references is integrated across core entity data paths:

• Entity Operations & Search: Entity creation (POST /v1/entities/template/{template}), updates (PATCH /v1/entities/{id}), and entity search filters (POST /v1/entities/search/{template_id}) accept attribute slugs directly in payload bodies and query filters.
• Metric Telemetry Ingestion: For high-frequency telemetry streams and hardware sensors, the metric ingestion endpoint (POST /v1/entities/{id}/metrics) processes attribute_slug values directly within stream payloads:

{
  "metric_values": [
    {
      "attribute_slug": "warehouse_stock_level",
      "value": "84",
      "updated_at": "2026-08-07T09:30:00Z"
    }
  ]
}

During execution, telemetry payloads referencing slugs are resolved automatically and streamed directly into the metric store without performance penalties.

Platform and AI Assistant Integration

Slugs serve as surface-level references across all platform tools:

• Web Console UI: Attribute creation and configuration dialogs include dedicated input fields for slugs. In attribute directory tables, active slugs display as monospace badge tags to simplify copying identifiers into codebase configurations.
• AI Assistant Tooling: Schema scaffolding and modification tool calls support the slug property across schema generation functions. When generating or modifying project data models, the AI Assistant assigns standard snake_case slugs to created attributes automatically.

Scoping and Backward Compatibility

Attribute slugs are optional and can be introduced progressively into existing projects without breaking existing integrations.

• Project-Level Scoping: Slugs are enforced per project scope, so teams can use familiar naming conventions across separate projects without cross-project naming conflicts.
• Optimized Resolution: Slug resolution is cached per project, preserving low-latency execution paths across real-time writes and high-frequency telemetry streams.
• 100% Backward Compatibility: Existing integrations and scripts relying on internal UUIDs continue to function seamlessly.

By introducing project-unique attribute slugs, Omnismith eliminates identifier coupling, making dynamic schema integrations cleaner and far more approachable for developer teams and AI workflows alike.