open-reuse/registry/capabilities/capability.infotech.oss-integration-continuity.md

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance, promotion_history

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.infotech.oss-integration-continuity	Managed Continuity For OSS Integrations	Turns proven open-source integrations into structured, maintainable, continuously managed assets with clear boundaries and update loops, so they remain robust and transparent as upstream evolves.	open-reuse	draft	infotech	oss integration maintenance	discovery availability current target confidence rationale D2 D4 medium SCOPE.md and INTENT.md document the core idea (structured, maintainable integration assets with update loops) clearly; note README.md is a stale repo-seed template leftover — SCOPE/INTENT are authoritative. current target confidence rationale A1 A3 low Python package (`open-reuse`) with tests and .gitea CI present, but availability confidence is low pending independent verification of a working install/CLI path during this sweep.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C1 low scope_vs_intent_and_consumer_expectations framework/service-model concept for sustainable reuse under change documented in INTENT.md level confidence basis known_reliability_risks R0 low consumer_quality_signals README.md is stale/misleading (leftover repo-seed template text) — needs fixing regardless of registry status availability not independently verified (no CLI run during this sweep)	intent includes excludes assumptions use_cases research_memos Ensure that valuable OSS integrations, once pragmatically created, become robust, transparent, and continuously maintainable long-term dependencies rather than silent rot. structured integration-asset model update-loop tracking for upstream evolution the integrations themselves (this repo manages the meta-layer, not specific integrations)	current_level target_level current_artifacts target_artifacts consumption_modes A1 A3 Python package (`open-reuse`) library import	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents SCOPE.md INTENT.md tests/ .gitea/	recommended_for not_recommended_for known_limitations teams wanting a structured process for keeping OSS integrations maintainable over time consumers needing a stable published API today (not independently verified in this sweep) README.md needs fixing (stale repo-seed leftover); availability not independently verified this sweep

Managed Continuity For OSS Integrations

Overview

open-reuse turns proven open-source integrations into structured, maintainable, continuously managed assets — the goal is not merely reuse, but sustainable reuse under change, with clear boundaries and update loops as upstream evolves.

Assessment notes

Discovery

SCOPE.md and INTENT.md document the core idea (structured, maintainable integration assets with update loops) clearly; note README.md is a stale repo-seed template leftover — SCOPE/INTENT are authoritative.

Availability

Python package (open-reuse) with tests and .gitea CI present, but availability confidence is low pending independent verification of a working install/CLI path during this sweep.

Completeness

First-pass honest assessment from the REUSE-WP-0017 coverage campaign (reuse-surface). No external consumer feedback exists yet; levels reflect scope-vs-intent documentation quality, not internal code quality.

Reliability

No production consumer telemetry exists yet; reliability level is intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence.

Promotion checklist

• ID follows capability.<domain>.<name> pattern
• Maturity enums match specs/CapabilityMaturityStandard.md
• external_evidence is populated separately from maturity
• Relations reference valid capability IDs (none yet)
• Index entry added in registry/indexes/capabilities.yaml