Orders

v3.2.0 ·Commerce · team-commerce

Owns the Order aggregate. Accepts order placement over HTTP, emits lifecycle events, and consumes payment settlement to close orders out.

At a glance

Artifacts

OpenAPI

API Contract

Synchronous order placement and lookup API.

v3.1.0gatedraw

AsyncAPI

Events

Events emitted and consumed by the Order aggregate.

v3.0.0gatedraw

ODCS

Order events history

Append-only historical record of the order lifecycle events.

v1.2.0gatedraw

Gherkin

Placing an order

Acceptance criteria for order placement and guaranteed event publication.

v2.1.0gatedraw

Drive an implementation

These specs are packaged for consumption — an implementation proves it satisfies them; it never redefines them.

Pin the released surface in a contracts.lock at the implementation repo's root and fetch it read-only:

# contract pin - version is the specs release tag, sha its commit
version: orders/v3.2.0
sha: 957d7b4c77e475e821122db086301c0eaac436eb

The full loop — fetch, strict binding, verification, staying converged via Renovate — is on Drive an implementation.

Commands

• placeOrder — POST /orders

Queries

• getOrder — GET /orders/{order_id}

Produces

• orders.placed.v2 — consumed by Payments
• orders.cancelled.v2 — no consumer in the specs

Consumes

• payments.settled.v2 — produced by Payments

Data products

• Order events history