---
id: RAIL-FAB-WP-0025
type: workplan
title: "Rail Rapp Reef Fabric Adaptation"
domain: financials
repo: railiance-fabric
status: active
owner: codex
topic_slug: railiance
created: "2026-07-25"
updated: "2026-07-25"
state_hub_workstream_id: "e6080e39-d60c-4a29-bc1f-adf1875461b2"
---

# 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: "5424575c-4dc8-45d2-bfb5-623a32114962"
```

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: "d8a5db60-f8ce-4c86-80a5-21eef6b85f5f"
```

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: "6067ab7d-a9cb-4db3-8a01-f910f3142728"
```

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: wait
priority: medium
state_hub_task_id: "dbfd3000-0204-473e-b1b8-eeb44d3fcd06"
```

Blocked on T01-T03.

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.