Explore Alexandria · Optio Alexandria

Data Command Query Event In-process Scroll or drag to pan · Ctrl + scroll or pinch to zoom

Notes

Explore Alexandria 6 of 6

Illustrative payment system · authored sample knowledge

Can the next conversation start with the reason included?

Read the Payment service’s actual generated context. Copy it for your external agent with its source identity, connected knowledge and recorded reasons.

Give people and agents the same project knowledge.

Back

Explore freely Open my projects

Checkout

Makes the payment outcome understandable

Owns the fictional checkout interface. Its 10-second wait may end before the payment outcome is known. A timeout shows Confirming payment rather than inventing failure.

Inside: Copper Lane Payments
ID: part-checkout

Outgoing

Read the recorded answer · Checkout → Payment service · Query · Network · Payment service API Checkout reads the current logical payment. Confirming payment means its processor outcome is still unknown; it is not a failed charge.
Request one logical payment · Checkout → Payment service · Command · Network · Payment service API Checkout supplies ord-1042 and EUR 10000. The payment service retains logical payment pay-1001 and operation key pay-op-1001.

Incoming

Buy the €100 lamp · Mira · customer → Checkout · Command · Network · Checkout interface Mira submits order ord-1042 through the fictional checkout. src-purchase-requirement records the desired business outcome.

Use-case steps

Mira chooses Pay for the €100 lamp. · Pay for the €100 lamp
The service records, submits and resolves one logical payment. · Pay for the €100 lamp
Checkout reads what is known; a missing answer remains visibly unknown. · Pay for the €100 lamp