PI 2 — 14 July – 7 September 2026 · v0.9

Focus: Implementation (PA4)

• A Module Verification Report must be extended for every module, showing at least 75% component requirement test coverage (linked via FullyVerifies / PartiallyVerifies on comp_req__... IDs in unit tests and component integration tests)

• A Platform Verification Report must be created, showing at least 75% feature requirement test coverage (linked via FullyVerifies / PartiallyVerifies on feat_req__... IDs in Feature Integration Tests)

• Detailed design documented for all modules (no open TBDs, status valid)

• Fill in and approve chklst_impl_inspection.rst for all modules — each checklist point is either completed or the finding is noted in the checklist with a tracked issue

• Remaining requirements (the ~20%) must have tracked tickets in the main S-CORE GitHub project — each ticket must have the component set and the milestone set to v1.0

Current State (19 May 2026)

Implementation

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

Verification Reports / Requirements Test Coverage

Note

Requirements test coverage is measured via FullyVerifies / PartiallyVerifies links in tests:

• Feature Req. Test Coverage → tracked in the Platform Verification Report: Feature Integration Tests link to feat_req__... IDs (Python decorator: @add_test_properties(partially_verifies=["feat_req__..."])).

• Component Req. Test Coverage → tracked in each module’s Module Verification Report: Unit tests and Component Integration Tests link to comp_req__... IDs (C++: RecordProperty("FullyVerifies", "comp_req__...");, Rust: #[record_property("FullyVerifies", "comp_req__...")]).

The docs-as-code tool parses Bazel test.xml output and creates testlink back-references on requirements. A few FIT tests in reference_integration already use the decorator for Persistency feature requirements.

Module	Feature Req. Test Coverage	Platform Ver. Report	Component Req. Test Coverage	Module Ver. Report
Baselibs	❌ Open	❌ Open	❌ Open	❌ Open
Communication	❌ Open	❌ Open	❌ Open	❌ Open
Logging	❌ Open	❌ Open	❌ Open	❌ Open
Orchestrator	❌ Open	❌ Open	❌ Open	❌ Open
Persistency	🔄 16% (6/37)	❌ Open	❌ Open	❌ Open
Time	❌ Open	❌ Open	❌ Open	❌ Open
Config Mgmt	❌ Open	❌ Open	❌ Open	❌ Open
Lifecycle	❌ Open	❌ Open	❌ Open	❌ Open
Security/Crypto	❌ Open	❌ Open	❌ Open	❌ Open