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

Consolidate platform workplans and assess intent gaps

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06ecb-456a-71c2-b41e-0755d336e883
This commit is contained in:
codex 2026-09-05 11:14:42 +02:00
parent 9d958f8e09
commit 9f83e426c7
40 changed files with 2985 additions and 295 deletions
Download patch file Download diff file Expand all files Collapse all files

61
workplans/RPF-WP-0031-workplan-identity-collision.md
View file

@ -1,61 +0,0 @@
---
id: RPF-WP-0031
type: workplan
title: "Separate duplicated apps-pg and Core Hub workplan identities"
domain: financials
repo: railiance-platform
status: finished
owner: codex
created: "2026-09-05"
updated: "2026-09-05"
state_hub_workstream_id: "dcc4fab2-2e95-570a-a415-6528c4cd8d11"
---
# Separate duplicated workplan identities
## Diagnose and prepare the exact repair
```task
id: RPF-WP-0031-T01
status: done
priority: high
state_hub_task_id: "8f75c85f-b442-5188-8b07-47a99251c0cf"
```
The supported `rmgr sync --path . --push` path reached the verified primary
railiance01 projection in 5.8 seconds, but refused six duplicate identities.
Both the May apps-pg archive and August Core Hub onboarding use RPF-WP-0021,
the same workplan UUID, and the same first five task UUIDs. No projection rows
were created, changed, or retired by the refused reconciliation.
`docs/evidence/RPF-WP-0021-collision-repair-proposal.json` fixes the proposed
choice: retain the older archive and reidentify the newer onboarding record as
RPF-WP-0030, with six Repo Manager-derived UUIDs and four evidence-reference
updates. Existing source UUIDs have not been changed.
## Apply the identity repair and reconcile
```task
id: RPF-WP-0031-T02
status: done
priority: high
state_hub_task_id: "2990a940-634c-5d76-b74c-740de8c36b16"
```
Requires a one-time user exception to AGENTS.md's prohibition on editing managed
UUID fields. The existing Repo Manager migration command considers only live
workplans and unfinished tasks, so it does not repair these finished records.
After approval, apply the exact proposal, preserve the archived identity and
all completion evidence, check uniqueness across root and archived workplans,
commit/push, and run `rmgr sync`. Inspect any retirement refusal before proceeding;
never blanket-acknowledge unrelated retirements.
User approved the exact exception on 2026-09-05. Applied the six proposed UUIDs
and four evidence-reference updates; the archived file is byte-for-byte unchanged.
All 196 source IDs and 196 UUIDs are unique across root and archived files.
Primary/railiance01 verified the pushed `6b41a43` commit and applied the source
projection in 12 seconds: four workplans created, 30 updated, no retirements,
no refusals, no cancelled tasks. RPF-WP-0028/0029/0030/0031 are now projected.
Receipt: `docs/evidence/RPF-WP-0031-reconciliation-2026-09-05.json`.
The approved identity repair and its authoritative reconciliation are complete.