railiance-fabric/workplans/archived/260702-RAIL-FAB-WP-0006-multi-repo-registry-onboarding.md
tegwick 0507b0861b
All checks were successful
CI Smoke / host-smoke (push) Successful in 2s
CI Smoke / container-smoke (push) Successful in 7s
CUST-WP-0055 T06/T07: workplan-first fabric source docs and archive notes
Update catalog, integration docs, and fabric capability declarations to
use workplan terminology. Add archive grandfather notes.
2026-07-08 20:26:24 +02:00

64 lines
1.6 KiB
Markdown

---
id: RAIL-FAB-WP-0006
type: workplan
title: "Multi-Repo Registry Onboarding"
domain: financials
repo: railiance-fabric
status: finished
owner: codex
topic_slug: railiance
planning_priority: high
planning_order: 6
state_hub_workstream_id: "1b8328d9-dc5e-4d3f-957d-5b6b5e9eb1b4"
created: "2026-05-17"
updated: "2026-05-17"
---
> **Terminology note:** Historical text in this archived workplan may use the legacy term "workstream". The fleet term is **workplan** (`canon/standards/workplan-terminology-fleet_v0.1.md`).
# RAIL-FAB-WP-0006 - Multi-Repo Registry Onboarding
## Goal
Make the registry useful with real ecosystem data by registering available
Railiance repositories, feeding their graph snapshots and library inventory, and
documenting the operating loop agents should use before inspecting the combined
model.
## Tasks
### T01 - Onboarding Manifest
```task
id: RAIL-FAB-WP-0006-T01
status: done
priority: high
state_hub_task_id: "4a17b588-daa2-4b79-b17a-b5806d96a111"
```
Define the repo onboarding manifest and expected local path, remote, graph,
artifact, and SBOM inputs for registry sync.
### T02 - Multi-Repo Sync Command
```task
id: RAIL-FAB-WP-0006-T02
status: done
priority: high
state_hub_task_id: "d993b52a-d253-4869-9de5-a7e1f1b268ce"
```
Add a local command that can register and sync multiple available Railiance
repositories into the registry service.
### T03 - Verification And Operating Notes
```task
id: RAIL-FAB-WP-0006-T03
status: done
priority: medium
state_hub_task_id: "e256b295-eacd-4321-b386-a08c143cdc77"
```
Verify the multi-repo registry loop and document how agents should run it before
inspecting the ecosystem model.