---
id: RAIL-FAB-WP-0031
type: workplan
title: "Follow the flex-auth to access-engine repository rename in Fabric"
domain: financials
repo: railiance-fabric
status: ready
flavor: residual
origin: residual
origin_ref: FLEX-WP-0020
owner: codex
topic_slug: railiance
created: "2026-09-22"
updated: "2026-09-22"
---

# RAIL-FAB-WP-0031 - flex-auth to access-engine rename (fabric-projection)

## Goal

FLEX-WP-0020 renames the repository coordinate `flex-auth` to `access-engine`.
The repository UUID `fda8ad85-a7d7-4055-8f21-902a533e59df` and Forge ID 42
stay. Runtime names stay `flex-auth` (FLEX-DEC-2026-013), so the
`flex-auth.*` runtime graph IDs must not change.

Origin: handoff request from flex-auth on 2026-09-15 (hub message
`10d4b1a2-8976-42a5-8d76-6fc1ce54fe87`, surface `fabric-projection`).

## T01 - Wait for the rename to land

```task
id: RAIL-FAB-WP-0031-T01
status: wait
priority: medium
```

Start T02 only once flex-auth reports FLEX-WP-0020 as executed: the Forgejo
repository is `coulomb/access-engine` and the local checkout is
`~/access-engine`. As of 2026-09-22 neither exists.

## T02 - Update repository coordinates

```task
id: RAIL-FAB-WP-0031-T02
status: wait
priority: medium
```

- `registry/local-repos.yaml` and `registry/railiance-repos.yaml`: slug, name,
  path, and `remote_url` move to `access-engine`.
- Repo-owned `fabric/**` declarations with `repo: flex-auth` move to
  `repo: access-engine`. Keep every `flex-auth.*` node id, service name, and
  file name, because they are runtime names.

## T03 - Re-ingest and confirm

```task
id: RAIL-FAB-WP-0031-T03
status: wait
priority: medium
```

Re-run `scan-manifest` for the renamed entry and re-export the graph. Confirm
that no `repo:flex-auth` repository node remains, that the `flex-auth.*`
runtime nodes are unchanged, and that no edge endpoint is left unresolved.
Then reply to flex-auth with the evidence.