coulomb/open-reuse
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Automation maximising upstream integration continuity framework.
20 commits 1 branch 0 tags 112 KiB
Find a file
tegwick 675198b753 Replace stale repo-seed template README with a real one 
Written from SCOPE.md/INTENT.md and direct source inspection. Requested
during reuse-surface REUSE-WP-0017-T05 review follow-up.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-07 01:34:42 +02:00
.claude/rules feat(cli): add open-reuse validate and register portfolio integrations 2026-06-24 18:25:13 +02:00
.gitea/workflows feat(cli): add open-reuse validate and register portfolio integrations 2026-06-24 18:25:13 +02:00
open_reuse feat(cli): add open-reuse validate and register portfolio integrations 2026-06-24 18:25:13 +02:00
registry Draft capability entry (reuse-surface REUSE-WP-0017-T04, cohort 3) 2026-07-06 19:50:53 +02:00
schemas feat(registry): add Integration Definition schema v0.1 2026-06-24 15:30:55 +02:00
templates feat(registry): add Integration Definition schema v0.1 2026-06-24 15:30:55 +02:00
tests feat(cli): add open-reuse validate and register portfolio integrations 2026-06-24 18:25:13 +02:00
workplans feat(cli): add open-reuse validate and register portfolio integrations 2026-06-24 18:25:13 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-06-24 18:25:36 +02:00
.gitignore Initial commit 2026-05-04 01:11:15 +00:00
.repo-classification.yaml Add .repo-classification.yaml (CUST-WP-0050 T11 agent first-pass) 2026-06-22 17:47:39 +02:00
AGENTS.md feat(cli): add open-reuse validate and register portfolio integrations 2026-06-24 18:25:13 +02:00
CLAUDE.md Add credential routing instructions for all agent runtimes 2026-06-18 22:48:38 +02:00
INTENT.md Intent and requirements for efficiently integrating thirdparty functionality. 2026-05-04 12:38:59 +02:00
LICENSE Initial commit 2026-05-04 01:11:15 +00:00
ProductRequirementsDocument.md Intent and requirements for efficiently integrating thirdparty functionality. 2026-05-04 12:38:59 +02:00
pyproject.toml feat(cli): add open-reuse validate and register portfolio integrations 2026-06-24 18:25:13 +02:00
README.md Replace stale repo-seed template README with a real one 2026-07-07 01:34:42 +02:00
SCOPE.md Complete State Hub bootstrap workplans (WP-0001) 2026-06-22 23:35:16 +02:00

README.md

open-reuse

Managed continuity for valuable open-source integrations.

Pragmatically-created integrations with open-source software — a reused component, an adapted service, an extracted module — become long-term dependencies on upstream evolution once they prove valuable. open-reuse turns those integrations into structured, maintainable, explicitly-owned assets instead of letting them degrade into undocumented, silently-breaking liabilities. The goal is not merely reuse, but sustainable reuse under change.

Every integration is analyzed, classified by reuse mode, given clear boundaries and interfaces, and tracked with an explicit update loop against its upstream.

Quick start

open-reuse validate
open-reuse validate path/to/thing.integration.yaml --root .

validate checks integration definitions (registry/integrations/*.integration.yaml) against schemas/integration.schema.yaml and the registry index (registry/indexes/integrations.yaml).

Getting oriented

  • Intent and problem statement: INTENT.md
  • Scope and boundaries: SCOPE.md
  • Product requirements: ProductRequirementsDocument.md
  • Integration entry template: templates/integration-entry.template.yaml
  • CLI source: open_reuse/cli.py, open_reuse/registry.py, open_reuse/validate.py

In scope

Integration analysis docs, registry, and workplans; reuse-mode classification and continuity policies; State Hub progress and decisions. See SCOPE.md for the full in/out-of-scope breakdown.