sysspec demo
A small commerce system specified end to end: orders accepted over HTTP, order lifecycle and payment settlement carried as events, and the historical record of both published as data contracts. Every toolkit change must keep it green, so what you read here is what the gates actually enforce.
The specs of record for sysspec demo, saying what it should be, rather than documentation of what exists. Implementations converge on them; they never bend to an implementation.
Contracts and acceptance criteria, gated and versioned. Changing one is a deliberate, versioned act, and CI rejects anything else.
Anyone can question these specs over MCP (thesysspec server), people in plain language and agents at implementation time, never from a remembered or vendored copy.
Implementations pin a release in contracts.lock, fetch it read-only, and prove conformance in CI: contract tests, strict-bound scenarios, the negative control, schema fuzz.
Services
Orders
Owns the Order aggregate. Accepts order placement over HTTP, emits lifecycle events, and consumes payment settlement to close orders out.
Payments
Authorises and settles payments against orders. Publishes settlement events and a daily reconciliation dataset.
Message flow
Producer → channel → consumer, left to right down the page; colour follows the domain. Click a node to trace its connections, double-click a service to open it.
ServiceChannelData productClientsHTTP operationsNo consumer yet