Explore Alexandria · Optio Alexandria

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

Use case	Concept Logical payment	Concept Order	Concept Processor confirmation	Concept Refund
Pay for the €100 lamp 1 missing	W	R	W	T
Refund the unavailable lamp 1 missing	R	T	W	W
Covered by	2	2	2	2

W Writes to it or sends it work R Reads from it T Passes a part it lives in

Notes

Explore Alexandria 1 of 6

Illustrative payment system · authored sample knowledge

What must happen before the shop sends Mira her lamp?

Follow the payment use case through the real project views. Select a step, a part or its supporting context.

Connect a business outcome to the parts responsible for it.

Explore freely Open my projects

Payment records

Use cases write to this store, but none reads from it.

Use cases that touch it

Ask your agent

In Alexandria, “Payment records” (id part-payment-store) is a gap: Written, never read. Find the use case it belongs to and add it to that use case's steps with settings_apply, or say why it is not needed. Read the model with drafts_get and settings_get.