repo-manager/intakes/intakes.md

# Intake records

## RMGR-IN-0001 — Validate assistant provenance on a natural multi-session window

```yaml
id: RMGR-IN-0001
kind: intake
title: Validate assistant provenance on a natural multi-session window
status: closed
origin: residual
origin_ref: RMGR-WP-0009
priority: low
owner: repo-manager
description: When two coding-assistant sessions naturally commit to one repository,
  run rmgr assistant-provenance report and retain the non-secret interleaving evidence.
  Do not manufacture or infer a collision.
created: '2026-08-21T20:09:23.942286+00:00'
updated: '2026-09-09T20:31:04.003556Z'
state_hub_intake_id: "01a025f3-40b0-7243-8002-dbe4609a6245"
closed_at: '2026-09-09T20:31:04.003556Z'
outcome: Natural multi-session evidence captured in docs/evidence/2026-09-09-natural-assistant-provenance.json.
```

## RMGR-IN-0002 — Assign dormant shared prefixes before their next allocation

```yaml
id: RMGR-IN-0002
kind: intake
title: Assign dormant shared prefixes before their next allocation
status: open
origin: residual
origin_ref: RMGR-WP-0004
priority: medium
owner: repo-manager
description: Before any new workplan is allocated under WHYNOT-WP, OPS-WP, or REPO-WP,
  assign one owner and distinct successor prefixes to the other repositories. Historical
  finished/archived files remain frozen. Re-run rmgr prefix-uniqueness and identifier
  preflight after assignment.
created: '2026-08-21T20:34:42.177493+00:00'
updated: '2026-10-03T08:32:00Z'
state_hub_intake_id: "01a02611-a663-7712-bd4b-e39c13e7bf20"
notes:
  - content: >-
      2026-09-09 review: the registry already assigns WHYNOT-WP to whynot-design,
      WNCTL-WP to whynot-control, OPS-WP to ops-hub, and BRIDGE-WP to ops-bridge.
      Fleet prefix scan reports no sharing or reused identifiers for these
      prefixes. However whynot-control/AGENTS.md still advertises WHYNOT-WP,
      despite its WNCTL-WP workplan files. Align that repository's instructions
      before its next allocation. REPO-WP remains unassigned in the registry. Current instructions advertise
      CORE-WP for core-hub, DISCTL-WP for disaster-control, and REPO-WP for
      repo-seed; finalize these registry assignments before reuse.
    author: codex
  - content: >-
      2026-10-03: registered CORE-WP to core-hub, DISCTL-WP to disaster-control,
      and REPO-WP to repo-seed after checking their current AGENTS.md declarations
      and the fleet prefix scan. No new ownership mismatch or reused identifier.
      Registry assignment is complete. This intake stays open because
      whynot-control/AGENTS.md still advertises WHYNOT-WP rather than its registered
      WNCTL-WP; that repository must align its instructions before allocation.
      The broader audit still reports pre-existing CUST-WP/RAILIANCE-WP sharing
      and NET-WP/RAILIANCE-WP retirement findings; historical files remain frozen.
    author: codex
```

## RMGR-IN-0003 — Scope normal sync identity validation to actionable records

```yaml
id: RMGR-IN-0003
kind: intake
title: Scope normal sync identity validation to actionable records
status: closed
origin: residual
origin_ref: RMGR-WP-0005
priority: low
owner: repo-manager
description: Normal rmgr sync currently refuses net-kingdom because the archived
  historical task id NK-WP-0003-T08a is noncanonical, even though that record
  already has an identifier and no assignment is requested. Align normal sync
  with the scoped legacy-repair behavior: unrelated historical invalid ids stay
  visible as conformance evidence but do not block deterministic assignment or
  forge-derived reconciliation of unrelated canonical records.
created: '2026-08-31T17:30:00+00:00'
updated: '2026-09-09T20:31:04.003556Z'
state_hub_intake_id: "4f1d9836-e0a6-56ea-bf19-2587c153f338"
closed_at: '2026-09-09T20:31:04.003556Z'
outcome: Implemented and verified in RMGR-WP-0015.
```

2026-09-09 resolutions: RMGR-IN-0001 is evidenced by
`docs/evidence/2026-09-09-natural-assistant-provenance.json`: 100 existing
commits, three assistants, and one naturally interleaved session pair. This
is a Git sequence signal, not proof of concurrent writes or a collision.
RMGR-IN-0003 is implemented and verified in RMGR-WP-0015.

## RMGR-IN-0004 — flex-auth → access-engine repository rename: reconcile the canonical path

```yaml
id: RMGR-IN-0004
kind: intake
title: "flex-auth → access-engine repository rename: reconcile the canonical path"
status: closed
origin: cross-repo
origin_ref: FLEX-WP-0020
priority: low
owner: repo-manager
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:
  reconcile the new canonical path; do not rewrite archived UUID-migration evidence. 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: 0a4b1825-99b1-4e1e-a4a0-448b0347b744.
state_hub_intake_id: "01a0f268-335d-7db0-b630-a4b451c73fde"
```

**Closed 2026-09-30:** rename landed (access-engine resolves; Forge ID 42; UUID
fda8ad85-a7d7-4055-8f21-902a533e59df unchanged). `config/repository-registry.yaml`
now records slug `access-engine` / `coulomb/access-engine` under the same
`repository_id`; INTENT.md and the deployment guide name the new coordinate.
Archived UUID-migration evidence under docs/evidence/ is untouched. `make test`: 196 passed.