Repository navigation
Conversation
github-project-automation
Bot
added this to
S-CORE Roadmap and TLC - Technical Lead Circle
Member
|
you should put it under the folder of strategy decissions and add the dr-xxx-strat in your naming |
FScholPer
reviewed
Oct 8, 2026
Contributor
There was a problem hiding this comment.
Should we not move that to the new project
FScholPer
reviewed
Oct 8, 2026
| behavior and, for service modules, exercise the IPC/SOME-IP **wire contract** | ||
| across the process boundary. | ||
|
|
||
| Each conformance test links to the stakeholder requirement(s) it verifies |
Contributor
There was a problem hiding this comment.
I think we should bundle then the stakeholder requirements tests as SCTS
|
|
||
| ## Decision | ||
|
|
||
| Introduce the **S-CORE Compatibility Test Suite (SCTS)** as a dedicated, |
Contributor
There was a problem hiding this comment.
I would also add a definition document like https://source.android.com/docs/compatibility/17/android-17-cdd?hl=de#31_managed_api_compatibility. We should start with a small list like only use score logging as logging lib etc.
…patibility onward)
antonkri
force-pushed
the
feat/dr-010-scts-overview
branch
from
October 13, 2026 14:54
732fb65 to
0a02233
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds DR-010-Strat — a strategic Decision Record giving an overview of the S-CORE Compatibility Test Suite (SCTS): a portable way for third-party distributions to demonstrate conformance against S-CORE module contracts.
Why
There is currently no portable, distributor-runnable conformance mechanism. Two structural subtleties make a naive test suite insufficient:
What the DR proposes
SCTS as a separately versioned Bazel test module with two stages:
label_flag; an unbound binding is a hard error (fail-closed). Provenance is recorded in the report.Conformance is defined at the artifact boundary, not the build-method boundary.
reference_integrationacts as the first consumer / self-test, and existingstkh_reqtraceability is reused.Status
draft— scoped deliberately at overview level. The concrete mechanisms (unbound_bindingrule,compliance.bind()extension, Stage-1 baseline generator, per-module conformance) are called out as follow-up DRs/issues.