Skip to content

Event Schema Definition #34

@DakotaCondos

Description

@DakotaCondos

As a development team member,
I want robot-related events to follow documented schemas,
so that the simulator, Order Service, Robot Data Ingestion System, and other services can exchange data consistently.

Acceptance Criteria

  • Given an event is published by or to the simulator
    When the event is created
    Then it includes an event ID, event type, schema version, timestamp, and bot ID where applicable.

  • Given a telemetry event is published
    When the event is consumed
    Then it follows the documented telemetry schema.

  • Given an order assignment event is received
    When the simulator processes it
    Then it follows the documented order assignment schema.

  • Given an order response event is published
    When the Order Service consumes it
    Then it identifies whether the order was accepted, queued, rejected, or completed.

  • Given a stock update event is published
    When the event is consumed
    Then stock includes item ID, item name, quantity on hand, quantity reserved, and quantity available.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions