E-Commerce Platform

UNCERTAIN
5flows
13nodes
8assertions
9observations
24findings
/home/runner/work/traceos/traceos/examples/ecommerce · 2026-09-11 19:42 UTC

flow.purchase

order current coverage: partial user_action: external.customer
validinvalidSubmit OrderactionValidate OrderdecisionConfirm Orderactioninvokes → flow.paymentemits → event.order.createdtransitions_to → state.order.confirmedReject Orderactiontransitions_to → state.order.rejected

Why provenance, never truth (INV-028)

  • intent.a-confirmed-order-is-a-promise
    Once an order reads CONFIRMED the customer has been told it will be fulfilled, so nothing downstream may quietly leave it in that state without paying.
    docs/decisions/0004-order-confirmation.md#Decision

Outcomes and what checks them (INV-027)

  • purchase.confirmedorder=confirmed
    ◐ checked assert.purchase.confirms-order
  • purchase.rejectedorder=rejected
    no check declared

Assertions

  • ◐ likely assert.purchase.confirms-order
    a validated order reaches CONFIRMED and emits order.created

Parallel branches are drawn as the absence of a next arrow, not as a fork construct (INV-021). Arrows are next; every other relationship is listed under its node.