Feature and Process Status

This page tracks the completion status of all 5 process areas per module. Update the status column for each module after completing the respective deliverable.

Process Status chart legend:

Process req. status	ISO 26262 std_req status	Req. verification status
🟢 Valid 🟡 Draft 🔴 Invalid ⬜ Other	🟢 Ok 🔵 Recommendation 🟡 Open 🟠 Action 🔴 Deviation ⬜ N/A · ◻ Other	🟢 Automated 🟡 Waiting for automation 🔵 Inspection list ⬜ Other

Implementation Status Values:

• ✅ Available — Work product created, reviewed and approved

• 🔄 NN% — In Progress: artifact exists with at least one valid element, percentage shows valid/total

• ❌ Open — Not yet started, not found, or 0% valid

• — — Not applicable for this module

Process Area 1 — Change Management

A Change Request must be created and approved by the Architecture Community before module development begins. See Change Management Workflows.

Process Status

Process req. status	ISO 26262 std_req status	Req. verification status

Implementation status: ✅ Available (9/9 deliverables complete)

Module	CR approved
Baselibs	✅ Available
Communication	✅ Available
Logging	✅ Available
Orchestrator	✅ Available
Persistency	✅ Available
Time	✅ Available
Config Mgmt	✅ Available
Lifecycle	✅ Available
Security/Crypto	✅ Available

Process Area 2 — Requirements Engineering

Feature and component requirements must be written and inspected. Work products: wp__requirements_feat, wp__requirements_comp, wp__requirements_inspect. See Requirements Engineering Workflows.

Process Status

Process req. status	ISO 26262 std_req status	Req. verification status

Implementation status: 🔄 26% (7/27 deliverables complete)

Module	Feature Requirements	Component Requirements	Req. Inspection
Baselibs	🔄 93% (14/15)	🔄 93% (124/134)	🔄 20% (2/10) bitmanipulation, concurrency, containers, filesystem, json, safecpp, result, srs, utils, feature-level
Communication	✅ Available (50/50)	🔄 97% (34/35)	❌ Open
Logging	✅ Available (46/46)	❌ Open	❌ Open
Orchestrator	🔄 84% (26/31)	❌ Open	❌ Open executor, orchestrator
Persistency	✅ Available (40/40)	🔄 95% (36/38)	✅ Available (2/2) feature-level, kvs
Time	✅ Available (15/15)	❌ Open	❌ Open
Config Mgmt	✅ Available (13/13)	❌ Open	❌ Open
Lifecycle	🔄 0% (0/92) requirements (all 92 entries :status: invalid)	🔄 0% (0/1) health_monitor (template placeholder, :status: invalid)	❌ Open
Security/Crypto	✅ Available (42/42)	❌ Open	❌ Open

Process Area 3 — Architecture Design

Feature and component architecture must be designed and inspected. Work products: wp__feature_arch, wp__component_arch, wp__sw_arch_verification. See Architecture Workflows.

Process Status

Process req. status	ISO 26262 std_req status	Req. verification status

Implementation status: 🔄 19% (5/27 deliverables complete)

Module	Feature Architecture	Component Architecture	Arch. Inspection
Baselibs	✅ Available (4/4)	🔄 98% (172/175)	🔄 80% (8/10) bitmanipulation, concurrency, containers, filesystem, json, safecpp, result, srs, utils, feature-level
Communication	✅ Available (3/3)	🔄 94% (17/18)	❌ Open
Logging	✅ Available (4/4)	✅ Available (3/3)	❌ Open
Orchestrator	🔄 66% (4/6)	🔄 98% (42/43)	❌ Open executor, orchestrator
Persistency	✅ Available (12/12)	🔄 25% (1/4)	❌ Open feature-level, kvs
Time	❌ Open	❌ Open	❌ Open
Config Mgmt	❌ Open	❌ Open	❌ Open
Lifecycle	🔄 94% (30/32)	🔄 94% (15/16)	❌ Open
Security/Crypto	❌ Open	❌ Open	❌ Open

Process Area 4 — Implementation

Source code and detailed design must be implemented and inspected. Work products: wp__sw_development_plan, wp__sw_implementation, wp__sw_implementation_inspection. See Implementation Workflows.

Process Status

Process req. status	ISO 26262 std_req status	Req. verification status

Implementation status: 🔄 47% (17/36 deliverables complete)

Module	SW Development Plan	Code	Detailed Design	Impl. Inspection
Baselibs	✅ Available	✅ Available (~119,400 LOC) baselibs	❌ Open	❌ Open bitmanipulation, concurrency, containers, filesystem, json, safecpp, result, srs, utils
Communication	✅ Available	✅ Available (~71,300 LOC) communication	❌ Open	❌ Open
Logging	✅ Available	✅ Available (~22,900 LOC) logging	❌ Open	❌ Open
Orchestrator	✅ Available	✅ Available (~38,300 LOC) lifecycle	❌ Open	❌ Open
Persistency	✅ Available	✅ Available (~8,700 LOC) persistency	❌ Open	❌ Open kvs
Time	✅ Available	✅ Available (~11,700 LOC) inc_time	❌ Open	❌ Open
Config Mgmt	✅ Available	✅ Available (~5,400 LOC) config_management	❌ Open	❌ Open
Lifecycle	✅ Available	✅ Available (~38,300 LOC) lifecycle	🔄 50% (1/2)	❌ Open
Security/Crypto	✅ Available	❌ Open	❌ Open	❌ Open

Process Area 5 — Verification

All tests must be implemented and a module verification report must be approved. Work products: wp__verification_sw_unit_test, wp__verification_comp_int_test, wp__verification_feat_int_test, wp__verification_module_ver_report. See Verification Workflows.

Process Status

Process req. status	ISO 26262 std_req status	Req. verification status

Note

C0/C1 Coverage data is sourced from the reference_integration CI (Code Quality & Documentation workflow, bazel coverage --config=ferrocene-coverage). C0 = line coverage, C1 = branch coverage. Rust coverage reports line coverage only. Modules not yet integrated into the reference_integration CI (Time, Config Mgmt) or with disabled coverage extraction (Orchestrator) show ❌ Open.

Note

Static Code Analysis is tracked per module via dedicated CI workflows (clang-tidy for C++, Rust Clippy for Rust). All listed workflows are zero-tolerance (CI fails on any finding), so a passing main branch implies 0 open findings. Additionally, CodeQL runs centrally across all pinned repositories in reference_integration (finding counts require the GitHub Security tab).

Dynamic Code Analysis is tracked via sanitizer CI workflows (ASan/UBSan/LSan via --config=asan_ubsan_lsan, TSan via --config=tsan). All listed workflows are zero-tolerance, so a passing main branch implies 0 sanitizer findings.

Implementation status: 🔄 36% (23/63 deliverables complete)

Module	Unit Tests	C0/C1 Coverage	Comp. Integration Tests	Feature Integration Tests	Static Code Analysis	Dynamic Code Analysis	Module Verification Report
Baselibs	✅ Available (4,663 tests)	🔄 C0: 92.4% / C1: 60.4% (cpp) Rust line: 74.4%	✅ Available (13 tests)	❌ Open	✅ 0 findings clang-tidy	✅ 0 findings ASan/UBSan/LSan	❌ Open
Communication	✅ Available (2,374 tests)	🔄 C0: 87.9% / C1: 58.8% (cpp)	✅ Available (42 tests)	❌ Open	🔄 Configured (clang-tidy, CodeQL/MISRA) but no CI enforcement workflow yet	✅ 0 findings ASan/UBSan/LSan, TSan	❌ Open
Logging	✅ Available (619 tests)	🔄 C0: 79.4% / C1: 42.4% (cpp) Rust line: 39.9%	❌ Open	✅ Available (1 test) reference_integration (cross-module)	❌ Open	❌ Open	❌ Open
Orchestrator	✅ Available (2 tests)	❌ Open	✅ Available (9 tests)	✅ Available (3 tests) reference_integration (cross-module)	✅ 0 findings Clippy	❌ Open	❌ Open
Persistency	✅ Available (138 tests)	🔄 C0: 94.7% / C1: 63.0% (cpp) Rust line: 92.7%	❌ Open	✅ Available (6 tests) reference_integration (cross-module)	✅ 0 findings Clippy	❌ Open	❌ Open
Time	✅ Available (296 tests)	❌ Open	✅ Available (11 tests)	❌ Open	❌ Open	❌ Open	❌ Open
Config Mgmt	✅ Available (143 tests)	❌ Open	❌ Open	❌ Open	✅ 0 findings clang-tidy	❌ Open	❌ Open
Lifecycle	✅ Available (2 tests)	🔄 C0: 77.2% / C1: 45.8% (cpp) Rust line: 53.8%	✅ Available (9 tests)	❌ Open	✅ 0 findings Clippy	❌ Open	❌ Open
Security/Crypto	❌ Open	❌ Open	❌ Open	❌ Open	❌ Open	❌ Open	❌ Open

Done Criteria

A module is considered complete when all of the following are true:

1. All valid component requirements have 100% test coverage (linked via FullyVerifies or PartiallyVerifies).

2. All CI metadata checks pass (TestType, DerivationTechnique, Description set on every test).

3. Static analysis has no open Critical or High findings.

4. The Module Verification Report (wp__verification_module_ver_report) is generated and approved by a Committer.