Explore Alexandria · Optio Alexandria

2 use cases: 2 still miss something, and 0 things on the map have no use case.

Use case	Input Buy the €100 lamp	Input Read an order’s payment evidence	Input Request refund-1001	Input Receive payment confirmation	Input Receive refund confirmation	Output Submit the same payment operation	Output Check the existing operation	Output Submit the same refund operation	Part Checkout	Part Confirmation handler	Part Payment records	Part Payment service	Part Fictional processor
Refund the unavailable lamp 1 missing		E	E		E			O		W	W	W	W
Covered by	0	1	1	0	1	0	0	1	0	1	1	1	1

E Enters the system here O Leaves the system here W Writes to it or sends it work R Reads from it C Only calls out from it

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

Refund the unavailable lamp

Illustrative system · authored sample records. The lamp is unavailable after payment confirmation. Support requests refund-1001 for EUR 10000 against pay-1001.

Actor: Merchant support
Trigger: The shop cannot supply Mira’s lamp.
Goal: Request one refund and explain whether its processor outcome is known.

What is missing

No load scenario puts demand on its connections

What it has

Trigger and goal
Steps on the map
Data named
Failure path

Ask your agent

In Alexandria, complete the use case “Refund the unavailable lamp” (id uc-refund-payment). Add or extend a load scenario with demand on its first interaction. Read it with settings_get, change it with settings_apply, and add interactions with drafts_apply.