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

chore: use RMASTER-WP prefix for master workplans

Browse source 
Rename RAILIANCE-WP-0017..0021 to RMASTER-WP-* so railiance-master
IDs no longer collide with railiance-platform's RAILIANCE-WP series.
Hub UUIDs are unchanged.
This commit is contained in:
codex 2026-08-14 14:29:18 +02:00
parent 3cc0dc31d6
commit 4864b7852d
15 changed files with 121 additions and 119 deletions
Download patch file Download diff file Expand all files Collapse all files

12
AGENTS.md
View file

@ -7,7 +7,7 @@
**Domain:** financials
**Repo slug:** railiance-master
**Topic ID:** `ca369340-a64e-442e-98f1-a4fa7dc74a38`
**Workplan prefix:** `RAILIANCE-WP-`
**Workplan prefix:** `RMASTER-WP-`
---
@ -191,10 +191,10 @@ Requires the `warden` CLI from `~/ops-warden` (`uv tool install .` or `uv run wa
Work items originate as files in this repo — not in the hub. The hub is a
read/cache/index layer that rebuilds from files.
**File location:** `workplans/RAILIANCE-WP-NNNN-<slug>.md`
**File location:** `workplans/RMASTER-WP-NNNN-<slug>.md`
**Archived location:** finished workplans may move to
`workplans/archived/YYMMDD-RAILIANCE-WP-NNNN-<slug>.md`. The `YYMMDD` prefix is
`workplans/archived/YYMMDD-RMASTER-WP-NNNN-<slug>.md`. The `YYMMDD` prefix is
the completion/archive date; the frontmatter `id` does not change.
**Ad Hoc Tasks:** small opportunistic fixes discovered during a session use
@ -206,7 +206,7 @@ for anything needing analysis, design, approval, dependencies, or multiple phase
```yaml
---
id: RAILIANCE-WP-NNNN
id: RMASTER-WP-NNNN
type: workplan
title: "..."
domain: financials
@ -227,7 +227,7 @@ are derived health labels, not frontmatter statuses.
**Task block format** (one per `##` section):
```task
id: RAILIANCE-WP-NNNN-T01
id: RMASTER-WP-NNNN-T01
status: wait | todo | progress | done | cancel
priority: high | medium | low
state_hub_task_id: "<uuid>" # written by fix-consistency — do not edit
@ -241,6 +241,8 @@ blocked work and `cancel` for stopped work.
Use `railiance-master` workplans for framework changes that span multiple
Railiance repos, especially repository taxonomy changes, architecture boundary
changes, and migrations introducing `rail-*`, `rapp-*`, or `reef-*` concepts.
IDs use `RMASTER-WP-` so they do not collide with `RAILIANCE-WP-` in
`railiance-platform` and other ownership repos.
Do not use this repo to track implementation work that belongs entirely inside
one concrete ownership repo such as `railiance-platform` or `railiance-apps`.