omni-channel journeys across channel using AJO

Enable a client into a journey. A journey in this case could be serious of steps a client has to taken to complete an action. Taking an action is supported in multiple channels like web, mobile in app, email and push notifications. How would one should think of creating an omni channel journey that helps us visualize end to end client move through the journey? 

Question: How can Adobe Journey Optimizer support an omnichannel client journey today and in the future?

I’m looking for guidance on how to model and orchestrate an end-to-end, omnichannel client journey using Adobe Journey Optimizer (AJO).

In this context, a journey represents a series of steps or actions that a client needs to take to accomplish a specific goal. These interactions may happen across multiple channels, such as:

• Web
• Mobile/in-app
• Email
• Push notifications

For example, a client may start an action on the web, receive an email as the next step, continue the process in the mobile app, and then receive a push notification based on their behavior.

What I’m trying to understand

How should we think about designing an omnichannel journey in AJO where we can not only orchestrate these cross-channel interactions, but also understand and visualize the client's end-to-end progression through the journey, regardless of which channel they use?

More specifically:

1. What does AJO support today?
   What capabilities are currently available in AJO for orchestrating and tracking a client's journey across web, mobile/in-app, email, push, and other channels?

2. How should the journey be modeled?
   Should the journey be designed as one centralized AJO journey with multiple channel touchpoints, or should different channel-specific journeys be connected through events, conditions, or other mechanisms?

3. How do we maintain continuity across channels?
   What is the recommended approach for identifying the client and maintaining their journey context as they move between web, mobile, email, and push?

4. How can we visualize the end-to-end client journey?
   Are there current AJO capabilities, Adobe Experience Platform capabilities, or recommended patterns that allow us to visualize the client's progression across channels rather than looking at each channel interaction separately?

5. What could AJO support in the future?
   From an architectural/roadmap perspective, where is AJO heading in terms of supporting a more holistic cross-channel client journey view, journey analytics, visualization, and real-time orchestration?

6. What are the recommended best practices?
   If anyone has implemented a similar omnichannel use case, I’d be interested in recommended architecture patterns, particularly around events, identity, journey state, channel handoffs, and measuring progression through the overall journey.

Ultimately, I’m trying to understand how we should design for an omnichannel journey today while keeping the architecture flexible enough to take advantage of future AJO capabilities.