2026-06-24 18:16:42 +02:00
|
|
|
|
---
|
|
|
|
|
|
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"
|
2026-06-24 18:17:27 +02:00
|
|
|
|
state_hub_workstream_id: "6f4b82dc-a642-4104-98d2-12f7403152fa"
|
2026-06-24 18:16:42 +02:00
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
# 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
|
2026-06-24 18:17:27 +02:00
|
|
|
|
state_hub_task_id: "c4367626-a4a6-4c57-bf83-ba54df3e6df0"
|
2026-06-24 18:16:42 +02:00
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
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
|
2026-06-24 18:17:27 +02:00
|
|
|
|
state_hub_task_id: "bd2c5dc8-814e-4045-86ed-2f15db4faf59"
|
2026-06-24 18:16:42 +02:00
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
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
|
2026-06-24 18:17:27 +02:00
|
|
|
|
state_hub_task_id: "f12d9856-fd9f-44f0-b841-a82f521149c3"
|
2026-06-24 18:16:42 +02:00
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
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
|
2026-06-24 18:17:27 +02:00
|
|
|
|
state_hub_task_id: "c59c5fe2-6f55-4097-8419-a73593abd589"
|
2026-06-24 18:16:42 +02:00
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
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.
|