Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions BUILD
Original file line number Diff line number Diff line change
Expand Up @@ -47,8 +47,10 @@ exports_files([
# - `:docs` for building documentation at build-time
docs(
data = [
# "@score_platform//:needs_json",
# "@score_process//:needs_json",
"@score_platform//:needs_json",
"@score_baselibs//:needs_json",
"@score_baselibs_rust//:needs_json",
"@score_process//:needs_json",
],
source_dir = "docs",
)
39 changes: 29 additions & 10 deletions MODULE.bazel
Original file line number Diff line number Diff line change
Expand Up @@ -28,11 +28,22 @@ bazel_dep(name = "platforms", version = "1.0.0")
# S-CORE process rules
bazel_dep(name = "score_bazel_platforms", version = "0.0.3")
bazel_dep(name = "score_docs_as_code", version = "2.2.0")
git_override(
module_name = "score_docs_as_code",
commit = "9132272642711b06a8f3f6e07183506e0f9e4603",
Comment on lines +31 to +33

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important

[Maintainability] Several git_override entries now point to etas-contrib forks (score_docs-as-code.git, score_score.git, score_baselibs.git, score_baselibs_rust.git) instead of the canonical eclipse-score GitHub org. If this is intentional for a POC, these should be reverted before merging to main — otherwise the build depends on forks that may diverge, be deleted, or have different access controls, breaking reproducibility for all contributors.

Is this intended to be temporary? If so, add a # TODO: revert to eclipse-score before merge comment, or gate behind a local override mechanism.

Context for Agents
Several `git_override` entries now point to `etas-contrib` forks (`score_docs-as-code.git`, `score_score.git`, `score_baselibs.git`, `score_baselibs_rust.git`) instead of the canonical `eclipse-score` GitHub org. If this is intentional for a POC, these should be reverted before merging to `main` — otherwise the build depends on forks that may diverge, be deleted, or have different access controls, breaking reproducibility for all contributors.

Is this intended to be temporary? If so, add a `# TODO: revert to eclipse-score before merge` comment, or gate behind a local override mechanism.

File: MODULE.bazel
Line: 33
Chain of Thought
  • Validation Decision: accepted
  • Confidence: 0.97
  • Likelihood Score: 5/5
  • Likelihood Reason: If merged to main as-is, all contributors will depend on etas-contrib forks that could diverge, be deleted, or have different access controls. This is inevitable to cause issues unless reverted.
  • Suggested Action: keep
  • Tool Calls Used: 2

Reasoning

The comment is factually accurate and highly actionable.

Evidence:

  • In BASE, all git_override entries pointed to eclipse-score (the canonical org) or had no git_override at all.
  • In HEAD, the PR introduces 4 new etas-contrib fork references:
    1. score_docs_as_codeetas-contrib/score_docs-as-code.git (new override)
    2. score_platformetas-contrib/score_score.git (new override)
    3. score_baselibsetas-contrib/score_baselibs.git (changed from eclipse-score/baselibs.git)
    4. score_baselibs_rustetas-contrib/score_baselibs_rust.git (new override)

Introduced by this PR: Yes, 100%. None of these etas-contrib references existed in BASE.

PR context: The title "process: DR-005 POC" confirms this is a proof of concept, which makes the comment's concern about these being temporary even more relevant.

Actionability: The comment provides two concrete actions:

  1. Revert to eclipse-score before merging to main
  2. Add # TODO: revert to eclipse-score before merge comments, or use a local override mechanism

This is a critical review finding for build reproducibility and supply chain integrity.

Evidence Summary

1. File Snapshot (BASE)

  • File: MODULE.bazel
1: # *******************************************************************************
2: # Copyright (c) 2025 Contributors to the Eclipse Foundation
3: #
4: # See the NOTICE file(s) distributed with this work for additional
5: # information regarding copyright ownership.
6: #
7: # This program and the accompanying materials are made available under the
8: # terms of the Apache License Version 2.0 which is available at
9: # https://www.apache.org/licenses/LICENSE-2.0
10: #
...

2. File Snapshot (HEAD)

  • File: MODULE.bazel
1: # *******************************************************************************
2: # Copyright (c) 2025 Contributors to the Eclipse Foundation
3: #
4: # See the NOTICE file(s) distributed with this work for additional
5: # information regarding copyright ownership.
6: #
7: # This program and the accompanying materials are made available under the
8: # terms of the Apache License Version 2.0 which is available at
9: # https://www.apache.org/licenses/LICENSE-2.0
10: #
...

Fix in Cursor

remote = "https://github.com/etas-contrib/score_docs-as-code.git",
)
bazel_dep(name = "score_tooling", version = "1.0.4")
bazel_dep(name = "score_rust_policies", version = "0.0.3")

bazel_dep(name = "score_process", version = "1.4.0", dev_dependency = True)
bazel_dep(name = "score_process", version = "1.4.3", dev_dependency = True)
bazel_dep(name = "score_platform", version = "0.5.1", dev_dependency = True)
git_override(
module_name = "score_platform",
commit = "7f07f2382aeddd218d0e091ffe3198c913819a8c",
remote = "https://github.com/etas-contrib/score_score.git",
)


# Toolchains and extensions
bazel_dep(name = "score_toolchains_gcc", version = "0.5", dev_dependency = True)
Expand All @@ -43,9 +54,10 @@ bazel_dep(name = "score_toolchains_rust", version = "0.4.0", dev_dependency = Tr
bazel_dep(name = "score_crates", version = "0.0.6")

# Overrides
# update to same version as baselib
git_override(
module_name = "score_tooling",
commit = "612d6f180a9bb6338de5f0e6667fcf83068d9c37", #until 1.0.5 is released
commit = "8894fe5440436a8c6d9e214c97b18d619c7f7eac",
remote = "https://github.com/eclipse-score/tooling.git",
)

Expand Down Expand Up @@ -92,20 +104,27 @@ use_repo(toolchains_qnx, "toolchains_qnx_ifs")

bazel_dep(name = "googletest", version = "1.17.0.bcr.1")
bazel_dep(name = "rapidjson", version = "1.1.0")
bazel_dep(name = "score_communication", version = "0.1.2")
git_override(
module_name = "score_communication",
commit = "5a70133dd8bd632f5c07f200a5ee4bc9f507c23b",
remote = "https://github.com/eclipse-score/communication.git",
)
# bazel_dep(name = "score_communication", version = "0.1.2")
# git_override(
# module_name = "score_communication",
# commit = "5a70133dd8bd632f5c07f200a5ee4bc9f507c23b",
# remote = "https://github.com/eclipse-score/communication.git",
# )
Comment on lines +107 to +112

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important

[Reliability] Commenting out score_communication as a bazel_dep will break any target that transitively depends on it. If this dependency is truly unused, the removal should be confirmed by a clean build of all affected targets. If it's temporarily disabled for the POC, add a tracking comment.

Suggested change
# bazel_dep(name = "score_communication", version = "0.1.2")
# git_override(
# module_name = "score_communication",
# commit = "5a70133dd8bd632f5c07f200a5ee4bc9f507c23b",
# remote = "https://github.com/eclipse-score/communication.git",
# )
# TODO(POC): Re-enable score_communication before merging to main
# bazel_dep(name = "score_communication", version = "0.1.2")
Context for Agents
Commenting out `score_communication` as a `bazel_dep` will break any target that transitively depends on it. If this dependency is truly unused, the removal should be confirmed by a clean build of all affected targets. If it's temporarily disabled for the POC, add a tracking comment.

```suggestion
# TODO(POC): Re-enable score_communication before merging to main
# bazel_dep(name = "score_communication", version = "0.1.2")
```

File: MODULE.bazel
Line: 112
Chain of Thought
  • Validation Decision: accepted
  • Confidence: 0.95
  • Likelihood Score: 5/5
  • Likelihood Reason: The message_passing_server target in score/datarouter/BUILD (line 862) explicitly depends on @score_communication//score/mw/com/message_passing. With the score_communication bazel_dep commented out in MODULE.bazel, building this target (or any target that transitively depends on it, like datarouter_lib and datarouter) will inevitably fail.
  • Suggested Action: keep
  • Tool Calls Used: 12

Reasoning

The comment claims that commenting out score_communication as a bazel_dep will break targets that transitively depend on it.

Evidence found:

  1. In the BASE MODULE.bazel (line 95), score_communication was an active dependency: bazel_dep(name = "score_communication", version = "0.1.2")
  2. In the HEAD MODULE.bazel (line 107), this has been commented out: # bazel_dep(name = "score_communication", version = "0.1.2")
  3. Critically, score/datarouter/BUILD line 862 still has an active dependency on @score_communication//score/mw/com/message_passing in the message_passing_server target.
  4. The message_passing_server target is used by datarouter_lib (line 391), which is used by socketserver_config_lib, datarouter_socketserver, and ultimately the datarouter binary (line 829).
  5. This dependency reference was NOT modified in the PR (the score/datarouter/BUILD file is not in the changed files list), meaning it's still expecting @score_communication to be available.

The comment correctly identifies that commenting out the bazel_dep while leaving active references to @score_communication in BUILD files will cause build failures. The suggestion to add a TODO tracking comment is actionable and appropriate for a POC branch. This is a real, introduced issue since the PR changes MODULE.bazel to comment out the dependency without also removing/commenting the usages.

Evidence Summary

1. File Snapshot (HEAD)

  • File: MODULE.bazel
  • Lines: 100-130
100: use_repo(toolchains_qnx, "toolchains_qnx_qcc")
101: use_repo(toolchains_qnx, "toolchains_qnx_ifs")
102: 
103: # C++ dependencies
104: 
105: bazel_dep(name = "googletest", version = "1.17.0.bcr.1")
106: bazel_dep(name = "rapidjson", version = "1.1.0")
107: # bazel_dep(name = "score_communication", version = "0.1.2")
108: # git_override(
109: #     module_name = "score_communication",
...

2. File Snapshot (BASE)

  • File: MODULE.bazel
1: # *******************************************************************************
2: # Copyright (c) 2025 Contributors to the Eclipse Foundation
3: #
4: # See the NOTICE file(s) distributed with this work for additional
5: # information regarding copyright ownership.
6: #
7: # This program and the accompanying materials are made available under the
8: # terms of the Apache License Version 2.0 which is available at
9: # https://www.apache.org/licenses/LICENSE-2.0
10: #
...

3. File Snapshot (HEAD)

  • File: BUILD
1: # *******************************************************************************
2: # Copyright (c) 2025 Contributors to the Eclipse Foundation
3: #
4: # See the NOTICE file(s) distributed with this work for additional
5: # information regarding copyright ownership.
6: #
7: # This program and the accompanying materials are made available under the
8: # terms of the Apache License Version 2.0 which is available at
9: # https://www.apache.org/licenses/LICENSE-2.0
10: #
...

4. File Snapshot (BASE)

  • File: BUILD
1: # *******************************************************************************
2: # Copyright (c) 2025 Contributors to the Eclipse Foundation
3: #
4: # See the NOTICE file(s) distributed with this work for additional
5: # information regarding copyright ownership.
6: #
7: # This program and the accompanying materials are made available under the
8: # terms of the Apache License Version 2.0 which is available at
9: # https://www.apache.org/licenses/LICENSE-2.0
10: #
...

5. File Lookup

  • Filename: BUILD
  • Max Results: 10
Found 10 file(s) matching 'BUILD':
- BUILD
- examples/BUILD
- score/datarouter/BUILD
- score/datarouter/build_configuration_flags/BUILD
- score/datarouter/daemon_communication/BUILD
- score/datarouter/dlt_filetransfer_trigger_lib/BUILD
- score/datarouter/error/BUILD
- score/datarouter/lib/synchronized/BUILD
- score/datarouter/network/BUILD
...

6. File Lookup

  • Filename: BUILD
  • Max Results: 10
Found 10 file(s) matching 'BUILD':
- BUILD
- examples/BUILD
- score/datarouter/BUILD
- score/datarouter/build_configuration_flags/BUILD
- score/datarouter/daemon_communication/BUILD
- score/datarouter/dlt_filetransfer_trigger_lib/BUILD
- score/datarouter/error/BUILD
- score/datarouter/lib/synchronized/BUILD
- score/datarouter/network/BUILD
...

7. File Snapshot (BASE)

  • File: score/datarouter/daemon_communication/BUILD
1: # *******************************************************************************
2: # Copyright (c) 2025 Contributors to the Eclipse Foundation
3: #
4: # See the NOTICE file(s) distributed with this work for additional
5: # information regarding copyright ownership.
6: #
7: # This program and the accompanying materials are made available under the
8: # terms of the Apache License Version 2.0 which is available at
9: # https://www.apache.org/licenses/LICENSE-2.0
10: #
...

8. File Snapshot (BASE)

  • File: score/datarouter/network/BUILD
1: # *******************************************************************************
2: # Copyright (c) 2025 Contributors to the Eclipse Foundation
3: #
4: # See the NOTICE file(s) distributed with this work for additional
5: # information regarding copyright ownership.
6: #
7: # This program and the accompanying materials are made available under the
8: # terms of the Apache License Version 2.0 which is available at
9: # https://www.apache.org/licenses/LICENSE-2.0
10: #
...

9. File Snapshot (BASE)

  • File: score/datarouter/BUILD
1: # *******************************************************************************
2: # Copyright (c) 2025 Contributors to the Eclipse Foundation
3: #
4: # See the NOTICE file(s) distributed with this work for additional
5: # information regarding copyright ownership.
6: #
7: # This program and the accompanying materials are made available under the
8: # terms of the Apache License Version 2.0 which is available at
9: # https://www.apache.org/licenses/LICENSE-2.0
10: #
...

10. File Snapshot (HEAD)

  • File: score/datarouter/BUILD
  • Lines: 846-865
846: cc_library(
847:     name = "message_passing_server",
848:     srcs = [
849:         "src/daemon/message_passing_server.cpp",
850:     ],
851:     hdrs = [
852:         "include/daemon/message_passing_server.h",
853:     ],
854:     features = COMPILER_WARNING_FEATURES,
855:     strip_include_prefix = "include",
...

Fix in Cursor


bazel_dep(name = "score_baselibs", version = "0.2.0")
git_override(
module_name = "score_baselibs",
commit = "3c65b223e9f516f95935bb4cd2e83d6088ca016f",
remote = "https://github.com/eclipse-score/baselibs.git",
commit = "c8402e0304f8c1d4e48afd33909713718f697fec",
remote = "https://github.com/etas-contrib/score_baselibs.git",
)


# Rust dependencies

bazel_dep(name = "score_baselibs_rust", version = "0.0.3")
git_override(
module_name = "score_baselibs_rust",
commit = "7bfda59d5e9a7dab25c4bcd546eb16b5bc43edbc",
remote = "https://github.com/etas-contrib/score_baselibs_rust.git",
)

2 changes: 1 addition & 1 deletion docs/conf.py
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@
"sphinx_design",
"sphinx_needs",
"sphinxcontrib.plantuml",
# "score_plantuml",
"score_plantuml",
"score_metamodel",
"score_draw_uml_funcs",
"score_source_code_linker",
Expand Down
146 changes: 146 additions & 0 deletions docs/data_router_recorder/docs/architecture/index.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,146 @@
..
# *******************************************************************************
# Copyright (c) 2025 Contributors to the Eclipse Foundation
#
# See the NOTICE file(s) distributed with this work for additional
# information regarding copyright ownership.
#
# This program and the accompanying materials are made available under the
# terms of the Apache License Version 2.0 which is available at
# https://www.apache.org/licenses/LICENSE-2.0
#
# SPDX-License-Identifier: Apache-2.0
# *******************************************************************************

.. _component_architecture_data_router_recorder:

data_router_recorder Component Architecture
===========================================

.. document:: data_router_recorder Architecture
:id: doc__data_router_recorder_architecture
:status: draft
:safety: ASIL_B
:security: NO
:realizes: wp__component_arch
:tags: template

.. attention::
The above directive must be updated according to your needs.

- Modify ``Your Component Name`` to be your Component Name
- Modify ``id`` to be your Component Name in upper snake case preceded by ``doc__`` and followed by ``_architecture``
- Adjust ``status`` to be ``valid``
- Adjust ``safety`` and ``tags`` according to your needs

Overview
--------
<Brief summary>

Requirements Linked to Component Architecture
---------------------------------------------

.. code-block:: none

.. needtable:: Overview of Component Requirements
:style: table
:columns: title;id
:filter: search("comp_arch_sta__archdes$", "fulfils_back")
:colwidths: 70,30

Description
-----------

<General Description>

<Design Decisions - For the documentation of the decision the :need:`gd_temp__change_decision_record` can be used.>

<Design Constraints>

Rationale Behind Architecture Decomposition
*******************************************

Mandatory: A motivation for the decomposition or reason for not further splitting it into internal components.

.. note:: Common decisions across components / cross cutting concepts is at the higher level.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Advisory

[Documentation] Fix grammar: use a plural verb and hyphenation, e.g., "Common decisions across components or cross-cutting concepts are at the higher level."

Note: The same template text with the same grammar issue also appears in:

  • docs/recorders/docs/architecture/index.rst (line 65)
  • docs/datarouter/docs/architecture/index.rst (line 68)
  • docs/features/logging/docs/architecture/index.rst (line 65)
Context for Agents
[**Documentation**]

Fix grammar: use a plural verb and hyphenation, e.g., "Common decisions across components or cross-cutting concepts are at the higher level."

Note: The same template text with the same grammar issue also appears in:
- `docs/recorders/docs/architecture/index.rst` (line 65)
- `docs/datarouter/docs/architecture/index.rst` (line 68)
- `docs/features/logging/docs/architecture/index.rst` (line 65)

File: docs/data_router_recorder/docs/architecture/index.rst
Line: 65
Chain of Thought
  • Validation Decision: accepted
  • Confidence: 0.90
  • Likelihood Score: 5/5
  • Likelihood Reason: The grammar error is definitively present in the text. "Common decisions ... is" uses a singular verb with a plural subject, and "cross cutting" should be hyphenated as a compound adjective. This is not speculative—it's a clear, visible error in newly added documentation.
  • Suggested Action: modify
  • Tool Calls Used: 8

Reasoning

The comment flags a grammar issue on line 65 of docs/data_router_recorder/docs/architecture/index.rst:

Current text: "Common decisions across components / cross cutting concepts is at the higher level."

Issues identified by the comment:

  1. Subject-verb agreement: "Common decisions ... is" should be "Common decisions ... are" (plural subject requires plural verb).
  2. Hyphenation: "cross cutting" should be "cross-cutting" (compound adjective).

Both grammar corrections are valid. The suggested fix — "Common decisions across components or cross-cutting concepts are at the higher level." — is clear and actionable.

Diff responsibility: The file is entirely new (added in this PR), confirmed by the base commit returning "file not found." This issue is introduced by this PR, not pre-existing debt.

Additional context: The same template text with the same grammar error appears in at least three other new files added by this PR:

  • docs/recorders/docs/architecture/index.rst (line 65)
  • docs/datarouter/docs/architecture/index.rst (line 68)
  • docs/features/logging/docs/architecture/index.rst (line 65, with slight variation)

The comment is accurate, actionable (provides specific corrected text), and addresses an issue introduced by this PR.

Evidence Summary

1. File Snapshot (HEAD)

  • File: docs/recorders/docs/architecture/index.rst
  • Lines: 60-70
60: Rationale Behind Architecture Decomposition
61: *******************************************
62: 
63: Mandatory: A motivation for the decomposition or reason for not further splitting it into internal components.
64: 
65: .. note:: Common decisions across components / cross cutting concepts is at the higher level.
66: 
67: Static Architecture
68: -------------------
69: 
...

2. File Snapshot (HEAD)

  • File: docs/datarouter/docs/architecture/index.rst
  • Lines: 60-70
60: 
61: <Design Constraints>
62: 
63: Rationale Behind Architecture Decomposition
64: *******************************************
65: 
66: Mandatory: A motivation for the decomposition or reason for not further splitting it into internal components.
67: 
68: .. note:: Common decisions across components / cross cutting concepts is at the higher level.
69: 
...

3. File Snapshot (HEAD)

  • File: docs/features/logging/docs/architecture/index.rst
  • Lines: 60-70
60: 
61: Rationale Behind Architecture Decomposition
62: *******************************************
63: mandatory: a motivation for the decomposition
64: 
65: .. note:: Common decisions across features / cross cutting concepts is at the high level.
66: 
67: Static Architecture
68: -------------------
69: ..
...

Fix in Cursor


Static Architecture
-------------------

The components are designed to cover the expectations from the feature architecture
(i.e. if already exists a definition it should be taken over and enriched).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Advisory

[Documentation] Fix grammar: "if already exists a definition" should be "if a definition already exists". Note: the same phrase also appears in docs/recorders/docs/architecture/index.rst (line 71) and likely other similar template files added in this PR—please fix all occurrences.

Context for Agents
[**Documentation**]

Fix grammar: "if already exists a definition" should be "if a definition already exists". Note: the same phrase also appears in `docs/recorders/docs/architecture/index.rst` (line 71) and likely other similar template files added in this PR—please fix all occurrences.

File: docs/data_router_recorder/docs/architecture/index.rst
Line: 71
Chain of Thought
  • Validation Decision: accepted
  • Confidence: 0.97
  • Likelihood Score: 5/5
  • Likelihood Reason: The grammar error is clearly present on line 71 and will appear in the published documentation as-is unless fixed.
  • Suggested Action: modify
  • Tool Calls Used: 5

Reasoning

The comment correctly identifies a grammar issue on line 71 of the newly added file. The phrase "if already exists a definition" uses non-standard English word order and should be "if a definition already exists." The file is entirely new (not found in base), so this issue is introduced by this PR. The same problematic phrase also appears in other new template files added by this PR (e.g., docs/recorders/docs/architecture/index.rst line 71). The comment is accurate, specific, and actionable—it identifies the exact text and provides the corrected wording.

Evidence Summary

1. File Snapshot (HEAD)

  • File: docs/data_router_recorder/docs/architecture/index.rst
  • Lines: 69-73
69: 
70: The components are designed to cover the expectations from the feature architecture
71: (i.e. if already exists a definition it should be taken over and enriched).
72: 
73: .. comp:: data_router_recorder

2. File Snapshot (HEAD)

  • File: docs/datarouter/docs/architecture/index.rst
  • Lines: 69-73
69: 
70: Static Architecture
71: -------------------
72: 
73: The components are designed to cover the expectations from the feature architecture

3. File Snapshot (HEAD)

  • File: docs/recorders/docs/architecture/index.rst
  • Lines: 69-73
69: 
70: The components are designed to cover the expectations from the feature architecture
71: (i.e. if already exists a definition it should be taken over and enriched).
72: 
73: .. comp:: recorders

Fix in Cursor


.. comp:: data_router_recorder
:id: comp__data_router_recorder
:security: YES
:safety: ASIL_B
:status: invalid
:implements: logic_arc_int__log_cpp__recorder, logic_arc_int__logging__buffer

.. needarch::
:scale: 50
:align: center

{{ draw_component(need(), needs) }}
..
TEMPLATE: Uncomment and fill out the following comp_arc_sta directive:

.. comp_arc_sta:: Component Name (Static View)
:id: comp_arc_sta__component_name__static_view
:security: YES
:safety: ASIL_B
:status: invalid
:implements: logic_arc_int__feature_name__interface_name1
:fulfils: comp_req__component_name__some_title
:includes: comp_arc_sta__component_name__2

.. needarch::
:scale: 50
:align: center

{{ draw_component(need(), needs) }}

Dynamic Architecture
--------------------

..
TEMPLATE: Uncomment and customize the comp_arc_dyn directive:

.. comp_arc_dyn:: Dynamic View
:id: comp_arc_dyn__component_name__dynamic_view
:security: YES
:safety: ASIL_B
:status: invalid
:fulfils: comp_req__component_name__some_title

Put here a sequence diagram


Interfaces
----------


Internal Components
-------------------

..
TEMPLATE: Uncomment and customize the comp_arc_sta directive:

.. comp_arc_sta:: Component Name Static View
:id: comp_arc_sta__component_name__2
:status: invalid
:safety: ASIL_B
:security: YES
:fulfils: comp_req__component_name__some_title
:implements: logic_arc_int__feature_name__interface_name1

No architecture but detailed design

.. note::
Architecture can be split into multiple files. At component level the public interfaces to be used by the user and tester to be shown.

.. attention::
The above directives must be updated according to your component architecture.

- Replace the example content by the real content (according to :need:`gd_guidl__arch_design`)
- Set the status to valid and start the review/merge process
Loading