WIP: sphinx-needs filtering, Markdown & TRLC export rules (demo playground)

CHANGES_trlc_to_sphinx_needs_summary.txt

@@ -0,0 +1,89 @@
+Zusammenfassung der Änderungen: trlc_to_sphinx_needs – Vererbung & Links
+==========================================================================
+
+Datum: 2026-07-01
+Branches:
+  - docs-as-code: ankr_rules_score_playground
+  - baselibs:     ankr_score_rules_wip
+
+Ziel
+----
+Der TRLC->sphinx-needs-Konverter soll Vererbung/Links (`derived_from`)
+respektieren und die referenzierten Requirements (z.B. Feature Requirements)
+mit in die generierte needs.json aufnehmen, damit die Links auflösen.
+
+
+1) Konverter: scripts_bazel/trlc_to_sphinx_needs.py (docs-as-code)
+------------------------------------------------------------------
+- `derived_from` wird jetzt als echter sphinx-needs-Link mit Versions-
+  constraint gerendert:
+    TRLC   `SampleSEooC.FEAT_001@1`
+    -> Need `FEAT_001[version==1]`
+  (Paketpräfix `SampleSEooC.` entfernt, `@<version>` -> `[version==N]`).
+  Das entspricht exakt dem Speicherformat von sphinx-needs (an echter
+  needs.json verifiziert, z.B. `satisfies=['wf__cr_mt_featarch[version==1]']`).
+- Parser bewahrt den `@version`-Suffix in Referenzlisten (vorher verworfen).
+- Neue Typ-Zuordnung `AssumedSystemReq -> stkh_req` (Stakeholder Requirement)
+  inkl. Ausgabe des Pflichtfeldes `rationale`.
+- `convert()` / `main()` akzeptieren jetzt mehrere `.trlc`-Eingabedateien
+  (nargs="+"), damit paketübergreifend referenzierte Requirements in
+  derselben needs.json landen und die Links auflösen.
+- Neue Hilfsfunktion `_link_ref()` für die Referenz-/Versionsumwandlung.
+
+
+2) Bazel-Regel: docs.bzl (docs-as-code)
+---------------------------------------
+- `trlc_to_sphinx_needs` nimmt jetzt `srcs` (Liste) statt `src` (Einzeldatei)
+  und übergibt alle Dateien via `$(SRCS)` an das Tool.
+- Docstring entsprechend erweitert (neuer Typ, Link-/Versionsverhalten,
+  Hinweis auf das Mitliefern referenzierter Requirements).
+
+
+3) baselibs
+-----------
+- Referenzierte Requirement-Dateien aus dem tooling-Beispiel kopiert:
+    - feature_requirements.trlc        (package SampleSEooC, FeatReq)
+    - assumed_system_requirements.trlc (package SampleSEooC, AssumedSystemReq)
+  (component_requirements.trlc existierte bereits.)
+- BUILD: Ziel `baselibs_aous_from_trlc` verweist nun auf alle drei TRLC-Dateien
+  über `srcs = [component_requirements.trlc, feature_requirements.trlc,
+  assumed_system_requirements.trlc]`.
+
+
+Metamodell-Hintergrund (score_metamodel)
+----------------------------------------
+- comp_req.derived_from -> feat_req   (optional link)
+- feat_req.derived_from -> stkh_req   (optional link)
+- Link-Werte werden in needs.json inkl. Versionsconstraint gespeichert:
+  z.B. `"derived_from": ["FEAT_001[version==1]"]`.
+- Pflichtfelder stkh_req: reqtype, safety (QM|ASIL_B), status, rationale,
+  security.
+
+
+Verifikation
+------------
+Befehl:
+  cd /workspaces/baselibs && bazel build //:baselibs_aous_from_trlc
+
+Ergebnis: "Converted 3 file(s) -> ... (11 requirements, project 'Baselibs')"
+  - 2x stkh_req (ASR_SAMPLE_001/002, mit rationale)
+  - 4x feat_req (FEAT_001..004, derived_from -> ASR_SAMPLE_00x[version==1])
+  - 5x comp_req (REQ_COMP_001..005, derived_from -> FEAT_00x[version==1])
+    - REQ_COMP_004 mit zwei Links: FEAT_003[version==1], FEAT_004[version==1]
+Aufgelöste Kette: comp_req -> feat_req -> stkh_req.
+
+
+Noch offen / nicht committet
+----------------------------
+- Diese Änderungen sind noch NICHT committet (auf Wunsch).
+- Frühere Commits in dieser Session (bereits erledigt):
+    - docs-as-code: a6eca138 (feat_arch/comp_reqs/comp_arch Sub-Targets +
+      trlc_to_sphinx_needs Regel/Skript)
+    - baselibs:     2afce64  (component_requirements.trlc + BUILD-Verdrahtung)
+- Betroffene, noch uncommittete Dateien:
+    - docs-as-code/docs.bzl
+    - docs-as-code/scripts_bazel/trlc_to_sphinx_needs.py
+    - baselibs/BUILD
+    - baselibs/feature_requirements.trlc (neu)
+    - baselibs/assumed_system_requirements.trlc (neu)
+</content>

How-to: S-Core process step-by-step.md

@@ -0,0 +1,13 @@
+# How-to: S-Core process step-by-step
+
+## 1. Feature & Feature requirements in main score repository
+
+### a. What to do
+
+1. Define Feature
+2. Define Feature Requirements and map them to the stakeholder requirements
+
+### b. How to check
+
+1. Automated checks for requirements in docs-as-code.
+2. Checklist for things, that can not be automated -> automated check, that checklist is up to date.

README.md

@@ -32,3 +32,29 @@ pre-commit install --hook-type pre-push
 ```
 
 Execute the pre-commit manually via `pre-commit run` or `pre-commit run --all-files` to run it on all files.
+
+## Sphinx-needs processing rules
+
+> [!WARNING]
+> These rules are currently a **work-in-progress / demonstration** and are not yet production ready.
+
+In addition to building the documentation, docs-as-code ships a set of Bazel macros
+(in [docs.bzl](docs.bzl), backed by the Python tools in [scripts_bazel/](scripts_bazel))
+that post-process the `needs.json` produced by the documentation build. They let you:
+
+- **Filter** `needs.json` down to selected element types and/or components
+  (`filtered_needs_json`, plus convenience wrappers such as `component_requirements`,
+  `feature_requirements`, `assumptions_of_use`, `feature_architecture`, `component_architecture`).
+- **Render** the selected needs as a Markdown document (`sphinx_needs_to_md`).
+- **Convert** S-CORE requirements into [TRLC](https://github.com/bmw-software-engineering/trlc)
+  (`sphinx_needs_to_trlc`).
+- **Validate checklists** by pinning a SHA256 hash on a `mod_insp` / `mod_ver_report`
+  record and failing the build when the reviewed output drifts
+  (`requirements_checklist`, `architecture_checklist`, `dfa_checklist`,
+  `fmea_checklist`, `verification_report`).
+- **Bundle** a component's or feature's checklists, docs and sub-components
+  (`score_component`, `score_module`).
+
+See [scripts_bazel/README_needs_rules.md](scripts_bazel/README_needs_rules.md) for the
+full guide, including usage examples, transitive-dependency hashing and resolving
+external needs via `extra_needs`.