Domains

Domains describe what problem a system solves (identity, asset management, data governance), while pipeline stages describe what role a system plays (ingestion, storage, engine, interface, adoption). A single system can span multiple domains and multiple stages—and that’s normal.

Use domains as entry points when you know the problem space but don’t yet know the system names.

Domain map

Domains tell you what problem a system solves. Pipeline stages tell you the role it plays in the Reality → Action trace. Use domains when you are orienting to a problem space, then follow pipeline and patterns to see how the work is implemented.