railiance-platform/intakes/intakes.md

Intake records

RPF-IN-0001 — flex-auth → access-engine repository rename: confirm no live repository URL/path

id: RPF-IN-0001
kind: intake
title: "flex-auth → access-engine repository rename: confirm no live repository URL/path"
status: closed
origin: cross-repo
origin_ref: FLEX-WP-0020
priority: low
owner: railiance-platform
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:
  confirm no live repository URL or path to flex-auth remains in this repo, and
  repoint any that does after flex-auth announces that access-engine resolves;
  retain product/runtime terminology. The live rename (FLEX-WP-0020-T06) has not
  happened. Record completion evidence here. Request message: b55a40cb-eb03-4972-a9bc-aac6e131a63e.
closed: '2026-09-30'
resolution: >-
  Repointed the one live coordinate (scripts/create-t03-approval-requests.py, /home/worsch/flex-auth/examples -> /home/worsch/access-engine/examples), commit d32baa9; file verified present. Runtime/product vocabulary retained.
state_hub_intake_id: "01a0f26d-0c87-791e-8cc6-8d09cd794160"

RPF-IN-0002 — tenant-engine audit-core sender token: ESO Kubernetes-auth policy and role

id: RPF-IN-0002
kind: intake
title: "tenant-engine audit-core sender token: ESO Kubernetes-auth policy and role"
status: open
origin: cross-repo
origin_ref: TEN-IN-0005
priority: medium
owner: railiance-platform
requested_by: tenant-engine
description: >-
  Declared 2026-10-03 (founder-approved ops-mason plan
  tenant-engine-audit-core-sender-projection, rows 2-3):
  openbao/policies/workload-kv-read-tenant-engine-audit-core-sender-eso.hcl and
  the attended apply script scripts/openbao-tenant-engine-audit-core-sender-eso-attended.sh
  (policy + role tenant-engine-audit-core-sender-eso; SA tenant-engine/tenant-engine-eso,
  audience openbao, 15m ttl/max/explicit max, no default policy). Not applied.
  Open: attended apply, then the founder-attended KV seed (plan row 7).
  No RBAC change needed here (see message).

RPF-IN-0003 — npm publish lane for @coulomb/testdrive-jsui (coulomb Forgejo registry)

id: RPF-IN-0003
kind: intake
title: "npm publish lane for @coulomb/testdrive-jsui (coulomb Forgejo registry)"
status: open
origin: cross-repo
origin_ref: MARKITECT-WP-0002-T07
priority: medium
owner: railiance-platform
requested_by: markitect-main
description: >-
  Request for a governed publish-token lane (catalog entry, OpenBao path, read
  policy) for @coulomb/testdrive-jsui on the coulomb Forgejo npm registry, scoped
  to the coulomb tenant, plus an optional separate read/install token id. Model:
  whynot-design-npm-publish (CCR-2026-0001), which is bound to @whynot/design and
  cannot be reused. Publishing stays operator-approved and manual; no secret value
  requested. Request message: e5ac57f9-850a-4a8f-bbae-6c2fdac4b58e.
  Open: CCR draft and approval, then catalog id reply. Overlaps the governed npm
  migration gate in RPF-WP-0035.