Skip to content

Feat/set satisfied by requirements - #3130

Closed
antonkri wants to merge 2 commits into
mainfrom
feat/set-satisfied-by-requirements
Closed

Feat/set satisfied by requirements#3130
antonkri wants to merge 2 commits into
mainfrom
feat/set-satisfied-by-requirements

Conversation

@antonkri

Copy link
Copy Markdown
Contributor

No description provided.

antonkri added 2 commits July 28, 2026 07:55
Set the satisfied_by link on all feat_req/comp_req that were missing it,
following the existing convention (feat_req -> feat__<feature>[version==1],
comp_req -> comp__<component>[version==1]).

- 37 feat_req in existing features (lifecycle, orchestration)
- 118 feat_req in 8 features for which a parent feat:: need was created
  (feat__ai_platform, feat__gen_ai, feat__code_generation, feat__config_mgmt,
   feat__diagnostics, feat__daal, feat__security_crypto, feat__time)
- 63 lifecycle comp_req -> comp__lifecycle_launch_manager
- migrated comp_req__lifecycle__launch from belongs_to to satisfied_by

The 8 new feat:: needs are minimal (analogous to feat__feo/feat__os,
without includes) since the underlying feature-request documents do not
yet define logic_arc_int interfaces.

Result: 0 feat_req and 0 comp_req remain without satisfied_by.
Validated with `bazel build //:docs` (success).
@github-actions

Copy link
Copy Markdown

The created documentation from the pull request is available at: docu-html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done
Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant