Orders
Owns the Order aggregate. Accepts order placement over HTTP, emits lifecycle events, and consumes payment settlement to close orders out.
v3.2.0 · Commerce · team-commerce
System specs
These are specs of what the system should be — not documentation of what exists. Implementations converge on them; they never bend to an implementation.
1Specify intent
Contracts and acceptance criteria, gated and versioned. Changing one is a deliberate, versioned act — CI rejects anything else.
2Build with context
Agents and engineers read these specs over MCP (thesysspec server) at implementation time — never from a remembered or vendored copy.
3Converge on gates
Implementations pin a release in contracts.lock, fetch it read-only, and prove conformance in CI: contract tests, strict-bound scenarios, schema fuzz.
2 services8 binding specs3 channelslast release 2026-08-30
Services
Payments
Authorises and settles payments against orders. Publishes settlement events and a daily reconciliation dataset.
v3.0.1 · Commerce · team-payments
Message flow
Click a node to trace its connections; double-click a service to open it.