C4 TOOL EVALUATION — CHECKOUT EXERCISE
Use one copy per candidate. These are blank observations, not vendor ratings.

Tool and version/plan:
Date and evaluator:
Authoring owner:
Reader/reviewer:
Documentation destination:

COMMON MODEL
Customer -> Commerce platform -> Payment provider
Storefront -> Checkout API -> Orders
Checkout API -> Order events -> Notification worker
Inside API: Checkout controller -> Order service -> Payment adapter
Payment adapter -> Payment provider; Order service -> Orders
Source specification: https://uxxu.io/examples/checkout-c4.dsl
The DSL needs translation for tools with another input format.

RECORD FOR EACH TASK
Elapsed minutes:
Manual corrections:
Reviewer errors/questions:
Evidence (link, screenshot, diff):
Pass / fail / not tested:

1. Build context and container views over the same provider.
   Pass: one identifiable provider is reused without ambiguous duplicates.
2. Rename the provider to Payment gateway in your own copy.
   Pass: all views using that element show the new name; relationships remain.
3. Add asynchronous notification work.
   Pass: a reader can distinguish order acceptance from notification processing.
4. Share the model through the team's documentation.
   Pass: the intended reader can navigate it with the intended access rights.
5. Review and recover a proposed change.
   Pass: reviewers can identify the change and restore the previous state.

EXPECTED / OBSERVED
Strongest workflow for this team:
Recurring maintenance burden:
Missing or untested requirement:
Monthly/annual price for actual authors and readers (include currency):
Hosting, publishing and operational effort:
Trial restriction or paid-plan dependency:
Decision and supporting evidence:
Owner and next review date: