Skip to content

Proposal/itf target composition with backwards compatibility for supported targets - #155

Draft
ihebs3ideni wants to merge 2 commits into
eclipse-score:mainfrom
ihebs3ideni:proposal/itf-target-composition-compatible
Draft

ihebs3ideni wants to merge 2 commits into
eclipse-score:mainfrom
ihebs3ideni:proposal/itf-target-composition-compatible

Conversation

@ihebs3ideni

@ihebs3ideni ihebs3ideni commented Nov 10, 2026 •

Copy link
Copy Markdown

Summary

Propose composing ITF targets from self-describing capabilities and actions while preserving the original test API through the compatibility layer.

Proposed Model

  • Target YAML explicitly selects roles, configuration, goals and policy files.
  • Consumer Protocols describe minimal API requirements, shared at module scope with test-specific additions.
  • Packs reference canonical contract definitions instead of maintaining duplicate specifications.
  • Shared tests run through Docker exec, SSH or serial, with separate direct-console coverage.
  • Planning, version checks, policy expectations and evidence make compatibility and lifecycle behavior inspectable.

Scope

This proposal PR adds only docs/proposals/rfc.md. It contains no RST navigation or runtime implementation changes.

The RFC links a reference implementation for evaluation and suggests possible review groupings without prescribing individual PRs, commit boundaries or landing order. Maintainers choose the integration strategy. Validation boundaries and remaining runtime limitations are recorded explicitly.

Review Requested

Feedback is requested on policy ownership, contract and version semantics, migration compatibility, and an integration strategy suitable for the project. Compatibility-layer support duration and eventual removal remain open decisions.

@ihebs3ideni ihebs3ideni changed the title Proposal/itf target composition compatible Proposal/itf target composition with backwards compatibility for supported targets Nov 10, 2026
@ihebs3ideni
ihebs3ideni force-pushed the proposal/itf-target-composition-compatible branch 7 times, most recently from 28f0266 to 7bddb3f Compare November 12, 2026 12:21
@ihebs3ideni
ihebs3ideni force-pushed the proposal/itf-target-composition-compatible branch from 7bddb3f to bdcde52 Compare November 12, 2026 12:39
@ihebs3ideni

Copy link
Copy Markdown
Author

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

1 participant