81 lines
2.4 KiB
Markdown
81 lines
2.4 KiB
Markdown
|
---
|
|||
|
|
id: OPEN-WP-0004
|
|||
|
|
type: workplan
|
|||
|
|
title: "Integration portfolio registration"
|
|||
|
|
domain: infotech
|
|||
|
|
repo: open-reuse
|
|||
|
|
status: ready
|
|||
|
|
owner: codex
|
|||
|
|
topic_slug: infotech
|
|||
|
|
created: "2026-06-24"
|
|||
|
|
updated: "2026-06-24"
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
# Integration portfolio registration
|
|||
|
|
|
|||
|
|
Grow `registry/indexes/integrations.yaml` beyond the markitect-quarkdown
|
|||
|
|
reference entry. Survey the portfolio for proven OSS integrations, coordinate
|
|||
|
|
definition authoring in consuming repositories, and register discovery rows in
|
|||
|
|
open-reuse.
|
|||
|
|
|
|||
|
|
## Design decisions
|
|||
|
|
|
|||
|
|
- **Source of truth:** Integration definitions live in consuming repos;
|
|||
|
|
open-reuse holds the discovery index only (per PRD open question 7).
|
|||
|
|
- **Entry bar:** Only integrations that have **proven value** in practice —
|
|||
|
|
open-reuse does not register experiments or planned work.
|
|||
|
|
- **Dependency:** Prefer `open-reuse validate` from OPEN-WP-0003 for final
|
|||
|
|
verification; manual checklist is acceptable until that workplan completes.
|
|||
|
|
|
|||
|
|
## Survey portfolio candidates
|
|||
|
|
|
|||
|
|
```task
|
|||
|
|
id: OPEN-WP-0004-T01
|
|||
|
|
status: todo
|
|||
|
|
priority: high
|
|||
|
|
```
|
|||
|
|
|
|||
|
|
Scan the local repo portfolio (reuse-surface `local-repo-roster.yaml`, domain
|
|||
|
|
`INTENT.md` files, and existing `*.integration.yaml` files) for proven
|
|||
|
|
integrations not yet indexed. Produce a short candidate list with owner repo,
|
|||
|
|
upstream project, reuse mode estimate, and registration readiness
|
|||
|
|
(ready / needs-definition / needs-boundary-work).
|
|||
|
|
|
|||
|
|
## Prioritize and assign targets
|
|||
|
|
|
|||
|
|
```task
|
|||
|
|
id: OPEN-WP-0004-T02
|
|||
|
|
status: todo
|
|||
|
|
priority: high
|
|||
|
|
```
|
|||
|
|
|
|||
|
|
Select 2–3 candidates for registration in this workplan cycle. Record the
|
|||
|
|
selection and rationale in the task result. Defer remaining candidates to
|
|||
|
|
backlog with explicit blockers.
|
|||
|
|
|
|||
|
|
## Author integration definitions
|
|||
|
|
|
|||
|
|
```task
|
|||
|
|
id: OPEN-WP-0004-T03
|
|||
|
|
status: todo
|
|||
|
|
priority: high
|
|||
|
|
```
|
|||
|
|
|
|||
|
|
For each selected candidate, ensure a conforming Integration Definition exists
|
|||
|
|
in the consuming repo at `integration/<id>.integration.yaml` using
|
|||
|
|
`templates/integration-entry.template.yaml`. Complete at minimum: upstream,
|
|||
|
|
reuse classification, boundary, validation harness, and maintainers. Coordinate
|
|||
|
|
PRs in owning repos where definitions are missing.
|
|||
|
|
|
|||
|
|
## Expand registry index
|
|||
|
|
|
|||
|
|
```task
|
|||
|
|
id: OPEN-WP-0004-T04
|
|||
|
|
status: todo
|
|||
|
|
priority: medium
|
|||
|
|
```
|
|||
|
|
|
|||
|
|
Add index rows to `registry/indexes/integrations.yaml` for each registered
|
|||
|
|
integration. Update `registry/README.md` reference section. Run
|
|||
|
|
`open-reuse validate` (or manual checklist) and confirm all new rows pass
|
|||
|
|
promotion gates for `registered` or `active` status.
|