railiance-master/workplans/RAILIANCE-WP-0018-first-wave-repo-family-materialization.md

id	type	title	domain	repo	status	owner	topic_slug	planning_priority	planning_order	created	updated	related_repos	state_hub_workstream_id
RAILIANCE-WP-0018	workplan	First-Wave Repo Family Materialization	financials	railiance-master	active	codex	railiance	high	18	2026-07-25	2026-07-25	railiance-master railiance-cluster railiance-platform railiance-infra railiance-fabric	054a494c-e430-4164-b2c3-e32e759cc3e0

RAILIANCE-WP-0018 - First-Wave Repo Family Materialization

Goal

Turn the completed separation architecture into the first concrete rail-*, rapp-*, and reef-* repo materialization wave.

This workplan governs the first implementation wave that makes the new repo families real rather than only defined. It stays in railiance-master because the sequencing still spans multiple ownership repos and Fabric integration.

Why This Exists

RAILIANCE-WP-0017 completed the architecture baseline and launched the first repo-local follow-up workplans.

What is still missing is the shared control plane for:

• creating the first concrete repo-family baselines
• keeping their boundaries consistent across repos
• aligning repo-local declarations with Fabric and State Hub ingestion
• preventing the first repo creations from drifting into ad hoc local patterns

Current Starting Point

The architecture baseline already exists in railiance-master:

• docs/repository-axes.md
• docs/rail-kubernetes-boundary.md
• docs/rapp-first-wave-candidates.md
• docs/reef-first-wave-rollout.md
• docs/fabric-state-hub-adaptation.md

The first implementation follow-up work also already exists:

• railiance-cluster/workplans/RAIL-BS-WP-0012-rail-kubernetes-extraction.md
• railiance-platform/workplans/RAILIANCE-WP-0012-rapp-openbao-extraction-boundary.md
• railiance-infra/workplans/RAIL-HO-WP-0007-first-reef-rollout-and-s1-canonicalization.md
• railiance-fabric/workplans/RAIL-FAB-WP-0025-rail-rapp-reef-fabric-adaptation.md

Fabric now has first repo-family-aware repository metadata, but the ecosystem still lacks:

• the first actual rail-* repo
• the first actual rapp-* repo
• the first actual reef-* repo
• relation projection for rail/rapp/reef topology

Target Outcome

When this workplan is complete:

1. Railiance has a repeatable bootstrap contract for first-wave rail-*, rapp-*, and reef-* repos.
2. The first concrete rail-kubernetes repo exists and is registered.
3. The first concrete rapp-openbao repo exists and is registered.
4. The first concrete reef-railiance01 repo exists and is registered.
5. Fabric can project the minimum rail/rapp/reef relation topology needed to answer placement questions.

Boundaries

This workplan may coordinate repo creation, repo-family bootstrap, and graph integration across Railiance repos.

It must not weaken the existing ownership boundaries:

• railiance-cluster remains the S2 ownership home
• railiance-platform remains the S3 ownership home for OpenBao
• railiance-infra remains the canonical S1 ownership home for first-wave reefs
• railiance-fabric remains the implementation home for graph ingestion and projection

Tasks

T01 - Publish the first-wave repo bootstrap contract

id: RAILIANCE-WP-0018-T01
status: done
priority: high
state_hub_task_id: "d6ba9286-222d-49d2-83e9-fd251c534dde"

Record the minimum bootstrap contract future rail-*, rapp-*, and reef-* repos should follow so the first materialization wave does not invent three incompatible patterns.

Acceptance:

• one framework document defines the minimum file baseline
• one framework document defines the first declaration path per repo family
• the metadata projection rule into Fabric and State Hub is named

2026-07-25: Added docs/repo-family-bootstrap-contract.md.

T02 - Launch the first rail-kubernetes repo materialization

id: RAILIANCE-WP-0018-T02
status: progress
priority: high
state_hub_task_id: "726a0c5c-2fa5-4bb9-a730-3200abc40ac8"

Create the concrete repo bootstrap and extraction path for rail-kubernetes using the boundary already defined in railiance-master and the repo-local follow-up work already opened in railiance-cluster.

Acceptance:

• the new repo has the required baseline files
• the repo declares the Kubernetes rail contract in source-controlled form
• the compatibility path from railiance-cluster is preserved
• the repo is ready for Fabric and State Hub registration

T03 - Launch the first rapp-openbao repo materialization

id: RAILIANCE-WP-0018-T03
status: wait
priority: high
state_hub_task_id: "3e46e1bd-c730-4e41-a00a-6aa7a4645023"

Create the concrete repo bootstrap and workload-package declaration for rapp-openbao without letting the package repo absorb platform ownership.

Acceptance:

• the new repo has the required baseline files
• the repo declares OpenBao as a managed workload package
• the repo declares supported rails and rollout/smoke/rollback contract
• the remaining ownership boundary with railiance-platform stays explicit

T04 - Launch the first reef-railiance01 repo materialization

id: RAILIANCE-WP-0018-T04
status: wait
priority: medium
state_hub_task_id: "f6f2ea73-0ff3-4cfa-b7a7-7b71db3afb4a"

Create the concrete repo bootstrap and substrate declaration for reef-railiance01 as the first durable reef repo.

Acceptance:

• the new repo has the required baseline files
• the repo declares substrate kind, lifecycle, criticality, hosted rails, and primary rail
• the repo stays compatible with the canonical S1 ownership role of railiance-infra

T05 - Add relation projection for rails, rapps, and reefs in Fabric

id: RAILIANCE-WP-0018-T05
status: wait
priority: medium
state_hub_task_id: "ef999db5-e75e-467a-a72a-d45fda2b6fa7"

Extend Fabric beyond repo-family-aware metadata so it can project the minimum rail/rapp/reef relation topology.

Acceptance:

• Fabric can project supports_rail
• Fabric can project hosts_rail
• Fabric can project binds_rapp
• Fabric can project governed_by
• the projection path is grounded in repo-local declarations rather than registry-only guesses

T06 - Verify first-wave registration and coordination end to end

id: RAILIANCE-WP-0018-T06
status: wait
priority: medium
state_hub_task_id: "5834f122-b9e9-41c1-93e9-d5525cd720bf"

Verify that the first concrete repos participate cleanly in:

• State Hub registration and indexing
• Fabric registration and graph projection
• workplan tracking across ownership repo and repo-family repo boundaries

Acceptance:

• the first concrete repos are visible to State Hub
• the first concrete repos are visible to Fabric
• cross-repo ownership and runtime relations are queryable
• the wave can continue to second candidates without redefining the bootstrap model

Exit Criteria

• The first-wave bootstrap contract is published
• rail-kubernetes exists as a first-class repo baseline
• rapp-openbao exists as a first-class repo baseline
• reef-railiance01 exists as a first-class repo baseline
• Fabric projects the minimum rail/rapp/reef relation topology
• State Hub and Fabric can coordinate the first concrete repo-family wave end to end

Notes

This workplan should stay focused on the first concrete repo-family wave.

Second-wave candidates such as rapp-vergabe-teilnahme, reef-coulombcore, or a future rail-knative should be launched only after the first wave proves the bootstrap contract, registration path, and relation model.