Explore Alexandria · Optio Alexandria

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

1 Trigger and goal 2 Steps on the map 3 Data named 4 Load scenario 5 Failure path Gap: something no use case explains

Notes

Explore Alexandria 3 of 6

Illustrative payment system · authored sample knowledge

What does the recorded payment tell us?

Inspect Payment and its confirmation records. The authored source explains when the outcome becomes known and how duplicate deliveries are recognized.

Read the data, its ownership and the evidence behind the picture.

Back Next

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.