RETICULUM · End-to-end journeys
Map processes from start to finish.
Connect processes from your ATLAS catalog to show the main journey and alternative paths.
Sign up for the beta to use ATLAS and RETICULUM on the Free plan. Verify your account, accept the terms and check that your workspace has access. Once signed in, choose RETICULUM in your ASTROMENTS workspace.
I want to understand how my processes connect from end to end
From the event that starts the work to the outcome you seek.
An end-to-end journey places processes that contribute to the same business response in context. You can read their connections even though each process has its own record and catalog position.
In RETICULUM you choose existing ATLAS processes, define their order and describe the initial event and final outcome or purpose. The event indicates what starts the journey; the outcome explains where you want to get. These are descriptions of the journey, not triggers or executable actions.
The same processes, another perspective
A main journey and an alternative with specific anchors.
Aurora Service’s fictitious journey uses Register requests, Evaluate requests and Resolve requests. Manage corrections takes part in a variant. All four belong to the catalog shown in ATLAS.
Conceptual diagram of the RETICULUM model. It does not reproduce a screen or execute decisions.
You can scroll the diagram horizontally, including with the arrow keys when it has focus.
- Initial eventRequest received
- N2Register requests
- N2Evaluate requests
- N2Resolve requests
- Final outcome / purposeRequest resolved and response communicated
How to read this example
Main: Request received → Register requests → Evaluate requests → Resolve requests → Request resolved and response communicated.
Variant: in this fictitious case, if data is missing at registration, the alternative segment starts after Register requests, passes through Manage corrections and rejoins before Evaluate requests.
The condition describes the case you have documented. It does not configure an automatic rule or execution loop.
Main journey
The reference sequence you describe: from receiving the request to resolving it and communicating the response. Participants are catalog processes, not copies of their records.
Contextual variant
An alternative segment associated with the main journey. It sits after a participant or the start and before another participant or the outcome. It replaces the segment between its anchors; it is not inserted as an extra step in the main journey.
Rejoining must occur after divergence in the main journey. In this example, the two anchors are consecutive: correction provides an alternative between registration and evaluation, without skipping the latter.
What you can do today
Build, browse and adjust your journeys.
Build the main journey
Define its name, initial event and outcome. Insert catalog processes, move them or remove their participation in a journey.
Add alternative paths
Describe an alternative, choose where it leaves and rejoins the main journey, and add its processes. Expand or collapse it to see its content.
View the context
Open a process’s details or read the journey’s edit history. This history shows changes to the diagram, not runs of the process.
Two complementary questions
Organizing and connecting are different perspectives.
RETICULUM uses processes from the ATLAS catalog. Joining a journey does not change a process’s N1, N2 or N3 level. Connections show the order of work, not its hierarchy.
If you need to analyze a problem before choosing an improvement, POLARIS helps you understand the gap and investigate its causes.
Back to the ASTROMENTS home page →The next step starts with you
See how your processes connect.
Sign up for the beta to use ATLAS and RETICULUM on the Free plan. Verify your account, accept the terms and check that your workspace has access. Once signed in, choose RETICULUM in your ASTROMENTS workspace.