generated from coulomb/repo-seed
tegwick
02bfcbc27f
Some checks failed
ci / validate-registry (push) Has been cancelled
Honest first-pass maturity vector grounded in README/docs/tests present in this repo; no invented evidence. Flagged for human review before publish. See reuse-surface history/2026-07-06-coverage-classification.md. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
121 lines
4.2 KiB
Markdown
121 lines
4.2 KiB
Markdown
---
|
|
id: capability.infotech.oss-integration-continuity
|
|
name: Managed Continuity For OSS Integrations
|
|
summary: 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.
|
|
owner: open-reuse
|
|
status: draft
|
|
domain: infotech
|
|
tags:
|
|
- oss
|
|
- integration
|
|
- maintenance
|
|
maturity:
|
|
discovery:
|
|
current: D2
|
|
target: D4
|
|
confidence: medium
|
|
rationale: 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:
|
|
current: A1
|
|
target: A3
|
|
confidence: low
|
|
rationale: 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.
|
|
external_evidence:
|
|
completeness:
|
|
level: C1
|
|
confidence: low
|
|
basis: scope_vs_intent_and_consumer_expectations
|
|
satisfied_expectations:
|
|
- framework/service-model concept for sustainable reuse under change documented in INTENT.md
|
|
broken_expectations: []
|
|
out_of_scope_expectations: []
|
|
reliability:
|
|
level: R0
|
|
confidence: low
|
|
basis: consumer_quality_signals
|
|
known_reliability_risks:
|
|
- 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)
|
|
discovery:
|
|
intent: Ensure that valuable OSS integrations, once pragmatically created, become robust, transparent,
|
|
and continuously maintainable long-term dependencies rather than silent rot.
|
|
includes:
|
|
- structured integration-asset model
|
|
- update-loop tracking for upstream evolution
|
|
excludes:
|
|
- the integrations themselves (this repo manages the meta-layer, not specific integrations)
|
|
assumptions: []
|
|
use_cases: []
|
|
research_memos: []
|
|
availability:
|
|
current_level: A1
|
|
target_level: A3
|
|
current_artifacts:
|
|
- Python package (`open-reuse`)
|
|
target_artifacts: []
|
|
consumption_modes:
|
|
- library import
|
|
relations:
|
|
depends_on: []
|
|
supports: []
|
|
related_to: []
|
|
evidence:
|
|
documentation:
|
|
- SCOPE.md
|
|
- INTENT.md
|
|
tests:
|
|
- tests/
|
|
- .gitea/
|
|
consumer_feedback: []
|
|
bug_reports: []
|
|
incidents: []
|
|
consumer_guidance:
|
|
recommended_for:
|
|
- teams wanting a structured process for keeping OSS integrations maintainable over time
|
|
not_recommended_for:
|
|
- consumers needing a stable published API today (not independently verified in this sweep)
|
|
known_limitations:
|
|
- README.md needs fixing (stale repo-seed leftover); availability not independently verified this sweep
|
|
promotion_history: []
|
|
---
|
|
|
|
# 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
|
|
|
|
- [x] ID follows `capability.<domain>.<name>` pattern
|
|
- [x] Maturity enums match `specs/CapabilityMaturityStandard.md`
|
|
- [x] `external_evidence` is populated separately from `maturity`
|
|
- [ ] Relations reference valid capability IDs (none yet)
|
|
- [x] Index entry added in `registry/indexes/capabilities.yaml`
|