message_passing SEooC - #1051
Conversation
| @@ -0,0 +1,270 @@ | |||
| --- | |||
| name: rules-score-actualize | |||
There was a problem hiding this comment.
Is "actualize" an English wording at all? I only know "update" ...?
| @@ -0,0 +1,270 @@ | |||
| --- | |||
| name: rules-score-actualize | |||
| description: "Incremental, traceable actualization/update lifecycle for an EXISTING S-CORE Safety Element out of Context (SEooC) built with the rules_score Bazel rules, whose requirements/architecture/safety/test artifacts are the trusted baseline (not a discardable PoC) but may themselves be incorrect, obsolete, or out of date with a new need. USE FOR: adding a new requirement to an already-authored dependable_element; fixing a defect where code/tests contradict a frozen requirement or diagram; retiring an obsolete requirement/behaviour; extending the design for a new or changed consumer; deciding the minimal set of existing artifacts a change must touch; keeping version numbers, derived_from links, FTA aliases, and lobster-tracing ids consistent across a small, reviewable diff. Component-agnostic — do not hardcode any component's domain content here. NOT FOR: bootstrapping a brand-new dependable_element or discarding a low-maturity/PoC baseline wholesale — use rules-score for that." | |||
There was a problem hiding this comment.
maybe easier to read if the "listing" here is not a ";" separated large text, but a normal markdown listing ...
| SPDX-License-Identifier: Apache-2.0 | ||
| ----------------------------------------------------------------------------- --> | ||
|
|
||
| # S-CORE SEooC Actualization Lifecycle — Orchestrating Skill |
There was a problem hiding this comment.
see above ... Updating Lifecycle?
|
|
||
| This skill is the router and process backbone for building an S-CORE **Safety Element out of | ||
| Context (SEooC)** with the `rules_score` Bazel rules. It does not duplicate the mechanics already | ||
| covered by the four artifact skills — it sequences them, defines the human checkpoints between |
There was a problem hiding this comment.
what four artefact skills? These one, which you mentioned i the description at the top??
score-requirements / score-architecture / score-safety-analysis / score-testing
But these aren't "skills"? So I'm lost what you mean here.
|
|
||
| ## When to use | ||
|
|
||
| - Starting a brand-new `dependable_element` from an informal, human-provided problem description. |
There was a problem hiding this comment.
human-provided problem description == problem_statement.md?
| @@ -0,0 +1,203 @@ | |||
| # Message Passing — Baseline Snapshot (orientation, not source of truth) | |||
|
|
|||
| > **This file is reverse-documented orientation material**, written per the `rules-score-actualize` | |||
There was a problem hiding this comment.
So this is an AI generated file?
Generated from the content found under the score/message_passing/dependability dir?
Which contained the tlrc-files you added within this PR and also the existing tlrc files Jochen et al. added?
Then it needs no review? Or shall I review, that the AI has correctly summarized the tlrc-files?
2 participants
No description provided.