Conversation
Communication does not use docs-as-code for its safety case; it generates self-contained reports (incl. LOBSTER traceability) via the dependable_element rule from eclipse-score/tooling and publishes them on its own GitHub Pages site. Split the module verification report index into reports built into this site and reports generated outside docs-as-code, and link the mw_com and message_passing reports in the latter section. Mounting them is currently not possible: the generated targets are testonly (deps reference other dependable elements' test rules), so a non-testonly docs target cannot depend on them.
antonkri
requested review from
AlexanderLanin,
FScholPer,
MaximilianSoerenPollak,
PiotrKorkus,
dcalavrezo-qorix,
lurtz,
nradakovic,
opajonk and
pawelrutkaq
as code owners
September 29, 2026 13:06
|
The created documentation from the pull request is available at: docu-html |
This branch has not been deployed
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
1 participant
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.
What
Links the verification reports that Communication generates for its dependable
elements from the module verification report index.
docs/verification_report/modules/index.rstnow has two sections:(Baselibs, Lifecycle, Logging, Persistency), unchanged.
mw_com(LoLa) andmessage_passingdependable element reports plus theirL.O.B.S.T.E.R. traceability reports.
Why not mount them?
Communication does not describe its safety case with docs-as-code. It uses the
dependable_elementrule fromeclipse-score/tooling, which emits a
self-contained multi-page report (architecture, components, units, assumed system,
LOBSTER traceability over feature requirements / failure modes / control measures /
root causes) and publishes it to Communication's own GitHub Pages site.
Pulling those pages into this site is currently not possible:
testonly, and a non-testonly docs target cannotdepend on them;
dependable_elementonly defaults totestonly = True— but settingtestonly = Falsedoes not help, because a dependable element'sdepsreferencethe
<name>target of other dependable elements, and that target is declared as aBazel
testrule, which is unconditionallytestonly;message_passingit is moot anyway, since it declares real test dependencies.Resolving this requires a change in
eclipse-score/tooling. Until then, linking isthe pragmatic option; this is called out in a note on the page.
Caveat (also noted on the page)
The links point at Communication's
latestdocs, which track itsmainbranch —they are not pinned to the Communication revision in
known_good.json.Verification
All four target URLs return HTTP 200. Docs-only change, no Bazel targets touched.