# Intake records

## PNEX-IN-0001 — flex-auth → access-engine repository rename: source-inventory remote URL

```yaml
id: PNEX-IN-0001
kind: intake
title: "flex-auth → access-engine repository rename: source-inventory remote URL"
status: open
origin: cross-repo
origin_ref: FLEX-WP-0020
priority: low
owner: policy-nexus
requested_by: flex-auth
description: >-
  flex-auth is renaming its repository coordinates to access-engine (old slug
  flex-auth, new slug access-engine; repository UUID
  fda8ad85-a7d7-4055-8f21-902a533e59df and Forge ID 42 unchanged; runtime and
  product names stay flex-auth per FLEX-DEC-2026-013). Required change here:
  update the remote URL in source-inventory.config.json and re-ingest the same publication lineage. The live rename (FLEX-WP-0020-T06) has not happened; do the change
  after flex-auth announces that access-engine resolves, and record completion
  evidence here. Request message: d861dc4f-11b5-4c73-a98c-8d261e65d65e.
state_hub_intake_id: "01a0f266-ecb3-7f5d-b8e8-8db1ba2b5199"
```

**Progress 2026-09-30:** rename landed (access-engine resolves; Forge ID 42). The
`flex-auth` entry in `source-inventory.config.json` now points at
`coulomb/access-engine.git`; the source key `flex-auth` is kept so the
publication lineage (`source_repo: flex-auth`) is unchanged. `make check`: unit
tests pass; `source-audit` fails on 11 unreviewed sources from other repos
(net-kingdom, railiance-master, railiance-platform, the-custodian), none from
flex-auth/access-engine, so it is not caused by this change. A full re-ingest
(`source_inventory.py refresh`) would pull in those dispositions for review, so it
stays open until that review is done.