repo-manager/intakes/intakes.md
tegwick 90e8d78ad3 index identifier migration residual
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a053ff-1d6f-7fe2-ac1c-a6eb40a42a0c
2026-08-31 19:44:39 +02:00

2.2 KiB

Intake records

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

id: RMGR-IN-0001
kind: intake
title: Validate assistant provenance on a natural multi-session window
status: open
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-08-21T20:09:23.942286+00:00'
state_hub_intake_id: "01a025f3-40b0-7243-8002-dbe4609a6245"

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

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-08-21T20:34:42.177493+00:00'
state_hub_intake_id: "01a02611-a663-7712-bd4b-e39c13e7bf20"

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

id: RMGR-IN-0003
kind: intake
title: Scope normal sync identity validation to actionable records
status: open
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-08-31T17:30:00+00:00'
state_hub_intake_id: "4f1d9836-e0a6-56ea-bf19-2587c153f338"