---
id: RAIL-FAB-WP-0025
type: workplan
title: "Rail Rapp Reef Fabric Adaptation"
domain: financials
repo: railiance-fabric
status: finished
owner: codex
topic_slug: railiance
created: "2026-07-25"
updated: "2026-07-25"
state_hub_workstream_id: "42b0b53f-5071-5127-bc50-d446a4e06ffe"
---

# RAIL-FAB-WP-0025 - Rail Rapp Reef Fabric Adaptation

## Goal

Adapt `railiance-fabric` so the new `rail-*`, `rapp-*`, and `reef-*` repo
families can become visible ecosystem entities in the registry and graph model,
instead of remaining naming conventions documented only in `railiance-master`.

This follows:

- `/home/worsch/railiance-master/docs/fabric-state-hub-adaptation.md`
- `/home/worsch/railiance-master/docs/repository-axes.md`

## Boundaries

This workplan may:

- update repo-local documentation and workplan conventions
- update onboarding manifests
- extend compatibility-first Fabric vocabulary and declaration guidance
- define the next implementation gaps for registry and graph support

It must not:

- invent full `rail-*`, `rapp-*`, or `reef-*` declarations before those repos
  exist
- redesign the financial Fabric model just to accommodate repo-family rollout
- treat repo-family metadata as done before registry and export support exist

## T01 - Fix Fabric repo-local orientation for the adaptation wave

```task
id: RAIL-FAB-WP-0025-T01
status: done
priority: high
state_hub_task_id: "a67f49b0-f5a6-5804-aef2-7c5542f404dc"
```

Bring the live repo docs in line with actual repository maturity and the local
workplan prefix so the new adaptation work lands on the real repo shape.

Done when `SCOPE.md`, `AGENTS.md`, and orientation docs no longer describe
Fabric as only early planning with `RAILIANCE-WP-*` workplans.

2026-07-25: Updated `SCOPE.md` and `AGENTS.md` to reflect current registry,
validator, and graph-explorer maturity, and corrected the local workplan
prefix to `RAIL-FAB-WP-*`.

## T02 - Onboard missing Railiance architecture repos in the seed manifest

```task
id: RAIL-FAB-WP-0025-T02
status: done
priority: high
state_hub_task_id: "7e531a5d-73e2-59f8-851a-b6c1920f3dd5"
```

Add the missing architecture-home and forge repos to the Railiance onboarding
manifest so registry sync can see the full current ownership family before new
repo families are introduced.

Done when `registry/railiance-repos.yaml` includes `railiance-master` and
`railiance-forge`.

2026-07-25: Added `railiance-master` and `railiance-forge` to
`registry/railiance-repos.yaml`.

## T03 - Publish the first compatibility-first Fabric vocabulary for rails

```task
id: RAIL-FAB-WP-0025-T03
status: done
priority: high
state_hub_task_id: "d338ba06-c7d7-5402-9694-59de51290561"
```

Record the minimum graph conventions future `rail-*`, `rapp-*`, and `reef-*`
repos should use before stronger first-class schema support exists.

Done when Fabric has a documented first-use convention for:

- `execution-rail`
- `managed-workload-package`
- `substrate-boundary`
- `workload-execution-contract`

2026-07-25: Added `workload-execution-contract` to the capability catalog and
documented the initial declaration guidance in
`docs/rail-rapp-reef-adaptation.md`, `docs/declaration-schema.md`, and
`docs/type-catalog.md`.

## T04 - Define the follow-on registry and export gaps

```task
id: RAIL-FAB-WP-0025-T04
status: done
priority: medium
state_hub_task_id: "df0876bf-853e-59f8-8e36-9de504c82a84"
```

Define the next implementation slice for:

- repo-family-aware registry metadata
- rail or reef relation projection
- State Hub export extensions needed for repo-family visibility

Done when the next repo-local implementation wave can start without reopening
the compatibility-first vocabulary decisions above.

2026-07-25: Implemented the first repo-family-aware registry metadata path in
the registry store, manifest sync flow, and graph-explorer repository
projection. Remaining relation and State Hub projection gaps are now recorded
explicitly in `docs/rail-rapp-reef-adaptation.md`.