---
id: USER-WP-0034
type: workplan
title: "Follow the flex-auth to access-engine repository rename (FLEX-WP-0020 handoff)"
domain: communication
repo: user-engine
status: active
flavor: implementation
owner: claude-code
topic_slug: user-engine
created: "2026-09-22"
updated: "2026-09-22"
related: [FLEX-WP-0020]
---

Intake for the FLEX-WP-0020 consumer handoff (hub message 94fd6ef0). The
repository coordinate changes from flex-auth to access-engine. The State Hub
UUID fda8ad85-a7d7-4055-8f21-902a533e59df and Forge ID 42 are unchanged.
Runtime names stay flex-auth (FLEX-DEC-2026-013). FLEX-WP-0020 orders the
change: the old source path stays correct until the rename lands.

## Verify flex-auth runtime vocabulary stays intentional

```task
id: USER-WP-0034-T01
status: done
priority: medium
```

2026-09-22: a scan of the repo (excluding `.git`) finds exactly one
repository coordinate: the absolute source path at
`wiki/ArchitectureBlueprint.md:14`. Every other `flex-auth` occurrence is
product or runtime vocabulary, and it stays unchanged. That covers
`FlexAuthHTTPAdapter`, the `USER_ENGINE_FLEX_AUTH_*` environment variables,
the `flex-auth-user-engine` Deployment/caller, and flex-auth as the decision
boundary in SCOPE, INTENT and the architecture docs. No runtime rename, image
change or rollout belongs to user-engine.

## Re-point the absolute source path after the rename lands

```task
id: USER-WP-0034-T02
status: wait
priority: medium
```

Waits for FLEX-WP-0020 §8: the fresh canonical `access-engine` clone must be
registered. Then change `wiki/ArchitectureBlueprint.md:14` from
`/home/worsch/flex-auth/docs/iam-profile-consumption.md` to the registered
access-engine path, confirm the target file exists there, and reply on the
FLEX-WP-0020 handoff thread with the commit. Leave historical workplans and
evidence unchanged.