Step 5 — Build

During Development you can enable a build with warnings instead of errors for all checks:

maturity = "development"

Each example under examples/ (e.g. examples/minimal/) is its own standalone Bazel module with its own MODULE.bazel, separate from the main rules_score module. Bazel commands therefore need to be run from within that module’s directory, not from the repository root — the code blocks below include the cd step so they can be copy-pasted as-is from the repository root.

Run the build from within the examples/minimal/ standalone module:

cd bazel/rules/rules_score/examples/minimal
bazel build //:my_element

bazel build //:my_element compiles the Sphinx documentation for the dependable_element together with its LOBSTER traceability report — the report is rendered as part of the same documentation build.

Expected output files:

bazel-bin/my_element_doc/html/                                ← Sphinx HTML documentation

Running Validations

All validations — TRLC requirement checks, unit/component/dependable-element tests, and the traceability completeness gate — are exposed as Bazel tests and run with a single command:

cd bazel/rules/rules_score/examples/minimal
bazel test //...