To make missions even more dynamic it would be great to have the support for "lanes".
General Idea
Lanes are where MissionStage are grouped together.
So you can have multiple "threads" inside of your mission.
Current flows and ideas
A stage is started when it meets the requirements.
All existing previous stages in it's lane need to be completed.
In example: A4 requires A1, A2 to be completed. A3 does not exist and is therefore deemed "completed".
GlobalStage primary lane needs to be at or above it's own stage number
In example: A4 requires STAGE 3 to be completed.
This enables the ME to create:
Multiple independent lanes
Multi-verse style
Merging into the "primary" lane when all need to come together.
Current Blocker/Issue
CAP only will look at the "global" stage, at the moment.
The naming convention for the CAP units does not easily support lanes.
It could, but the naming conventions easily get confusing and insanely long.
OnCompletion handling for lanes
StageLane Mermaid diagram creation for easier visualisation
OnStageNumberChanged implementation
Pre-activation on correct stage and stagelane
Activation on correct stage and stagelane
wired into persistence
Correctly wire for "pre-activation"
To make missions even more dynamic it would be great to have the support for "lanes".
## General Idea
Lanes are where `MissionStage` are grouped together.
So you can have multiple "threads" inside of your mission.

## Current flows and ideas
- A stage is started when it meets the requirements.
- All existing previous stages in it's lane need to be completed.
In example: A4 requires A1, A2 to be completed. A3 does not exist and is therefore deemed "completed".
- GlobalStage `primary lane` needs to be at or above it's own stage number
In example: A4 requires `STAGE 3` to be completed.
## This enables the ME to create:
- Multiple independent lanes
- Multi-verse style
- Merging into the "primary" lane when all need to come together.
## Current Blocker/Issue
CAP only will look at the "global" stage, at the moment.
The naming convention for the CAP units does not easily support lanes.
It could, but the naming conventions easily get confusing and insanely long.
- [x] OnCompletion handling for lanes
- [x] StageLane Mermaid diagram creation for easier visualisation
- [ ] OnStageNumberChanged implementation
- [ ] Pre-activation on correct stage and stagelane
- [ ] Activation on correct stage and stagelane
- [ ] wired into persistence
- [ ] Correctly wire for "pre-activation"
I've started on this anyway.
It would still be worth while and it will have the options to kinda have branches.
CAP integration will be a seperate issue.
create issue for cap integration
Although CAP compatibility is not figured out.
I've started on this anyway.
It would still be worth while and it will have the options to kinda have branches.
CAP integration will be a seperate issue.
- [ ] create issue for cap integration
dutchie031
self-assigned this 2026-08-22 14:52:58 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
To make missions even more dynamic it would be great to have the support for "lanes".
General Idea
Lanes are where
MissionStageare grouped together.So you can have multiple "threads" inside of your mission.
Current flows and ideas
In example: A4 requires A1, A2 to be completed. A3 does not exist and is therefore deemed "completed".
primary laneneeds to be at or above it's own stage numberIn example: A4 requires
STAGE 3to be completed.This enables the ME to create:
Current Blocker/Issue
CAP only will look at the "global" stage, at the moment.
The naming convention for the CAP units does not easily support lanes.
It could, but the naming conventions easily get confusing and insanely long.
Although CAP compatibility is not figured out.
I've started on this anyway.
It would still be worth while and it will have the options to kinda have branches.
CAP integration will be a seperate issue.