At the counter

Counter

Runtime disconnected

The capabilities currently modelled by the counter contract, and whether each can be planned from the evidence available now. Every answer on this page is computed by that contract — none is a success claim written here.

Contract planning decisions

9/9

ring_up_itemsUnavailable: planning_snapshot_unreadable
hold_saleUnavailable: planning_snapshot_unreadable
resume_saleUnavailable: planning_snapshot_unreadable
take_cashUnavailable: planning_snapshot_unreadable
take_cardUnavailable: planning_snapshot_unreadable
issue_refundUnavailable: planning_snapshot_unreadable
print_receiptUnavailable: planning_snapshot_unreadable
open_shiftUnavailable: planning_snapshot_unreadable
close_shiftUnavailable: planning_snapshot_unreadable

What this surface will govern

Ring up, hold and resume a sale
Take cash, take card, issue a refund
Open and close a shift, with the count reconciled
Print a receipt for a sale or a refund

Declared vocabulary

These are the only values this surface’s contract admits. They are identifiers, not labels, so they read the same in every language — which is what makes them searchable in a log.

tenders: card_presentcashexternal
counterSaleUnits: eachgrammillilitreminute
itemKinds: goodservicemembership
salesChannels: counteronlineinvoice