linking all feature requirement to architecture - #626
Open
MaciejKaszynski wants to merge 3 commits into
Open
Conversation
MaciejKaszynski
requested a deployment
to
workflow-approval
September 11, 2026 08:44 — with 
GitHub Actions
Waiting
GitHub Actions
Waiting
MaciejKaszynski
requested a deployment
to
workflow-approval
September 11, 2026 08:44 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaciejKaszynski
changed the title
MaciejKaszynski
requested a deployment
to
workflow-approval
September 11, 2026 10:31 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaciejKaszynski
requested a deployment
to
workflow-approval
September 11, 2026 10:31 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaciejKaszynski
requested a deployment
to
workflow-approval
September 11, 2026 11:14 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaciejKaszynski
requested a deployment
to
workflow-approval
September 11, 2026 11:14 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaciejKaszynski
marked this pull request as ready for review
September 11, 2026 11:15
MaciejKaszynski
requested review from
FScholPer,
NicolasFussberger,
anmittag,
antonkri,
pawelrutkaq and
ramceb
as code owners
September 11, 2026 11:15
| feat_req__lifecycle__hm_deadline[version==1], | ||
| :belongs_to: feat__lifecycle[version==1] | ||
|
|
||
| .. uml:: _assets/application_health_monitoring_dynamic.puml |
Contributor
There was a problem hiding this comment.
The linked diagram is a little bit outdated. As error reaction it is noted "notify State manager". I know it is not updated in your PR, but may be you can still rephrase it to "execute recovery action".
Comment on lines
+90
to
+94
| This dual approach ensures that both modern SCORE-aware applications and legacy | ||
| native applications can participate in the dependency management system, | ||
| allowing the :term:`Launch Manager` to orchestrate complex startup sequences | ||
| where components depend on each other's readiness rather than just their launch | ||
| order. |
Contributor
There was a problem hiding this comment.
Sounds like advertisement.
|
|
||
| - **SIGTERM**: Graceful shutdown request | ||
| - **SIGKILL**: Forced termination (after timeout) | ||
| - **SIGUSR1/SIGUSR2**: Application-specific signals (if configured) |
Contributor
There was a problem hiding this comment.
How can SIGUSR1/SIGUSR2 be configured?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adding links to feature architecture with the feature requirements that are considered for v1