coulomb/user-engine
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add USER-WP-0034: FLEX-WP-0020 access-engine rename handoff intake
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Has been cancelled
Details
Account journey acceptance / journeys (push) Successful in 9s
Details

Browse source 
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 58902@bnt-lap001
Assistant-Session: 7ac7f865-2dc5-4aa7-8eb7-27a342109c2f
This commit is contained in:
tegwick 2026-09-22 16:14:32 +02:00
parent abd4bf1fd8
commit c84224788e
1 changed files with 52 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

52
workplans/USER-WP-0034-access-engine-repository-rename-handoff.md Normal file
View file

@ -0,0 +1,52 @@
---
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.