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

chore: retire duplicate ThreePhoenix workplan
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
S2 HA lives in railiance-cluster. Point here instead of keeping a
second RAIL-BS-WP-0007 with the same hub ids. New bootstrap work uses
RAIL-BOOT-WP-.
This commit is contained in:
tegwick 2026-08-15 20:52:03 +02:00
parent 0814ed3a19
commit a029025055
3 changed files with 18 additions and 238 deletions
Download patch file Download diff file Expand all files Collapse all files

18
AGENTS.md
View file

@ -2,12 +2,12 @@
## Repo Identity
**Purpose:** Infrastructure bootstrap and configuration management for the railiance domain. Contains Ansible playbooks, cluster provisioning scripts, and environment safety nets.
**Purpose:** First-boot path from a bare VM to a working Railiance host, then hand off. Not the S2 cluster runtime (`railiance-cluster`) and not S1 inventory/hardening (`railiance-infra`).
**Domain:** financials
**Repo slug:** railiance-bootstrap
**Topic ID:** `ca369340-a64e-442e-98f1-a4fa7dc74a38`
**Workplan prefix:** `RAIL-BS-WP-`
**Workplan prefix:** `RAIL-BOOT-WP-`
---
@ -169,10 +169,10 @@ get wrong.
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/RAIL-BOOT-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-RAIL-BOOT-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
@ -184,11 +184,11 @@ anything needing analysis, design, approval, dependencies, or multiple phases.
```yaml
---
id: RAILIANCE-WP-NNNN
id: RAIL-BOOT-WP-NNNN
type: workplan
title: "..."
domain: financials
repo: railiance-cluster
repo: railiance-bootstrap
status: proposed | ready | active | blocked | backlog | finished | archived
owner: codex
topic_slug: ...
@ -208,7 +208,7 @@ derived health labels, not frontmatter statuses.
## Task Title
` ` `task
id: RAILIANCE-WP-NNNN-T01
id: RAIL-BOOT-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
@ -221,5 +221,5 @@ Status progression: `todo` → `progress` → `done`; use `wait` for waiting/blo
To create a new workplan:
1. Write the file following the format above
2. Notify the custodian operator to run `make fix-consistency REPO=railiance-cluster`
(or send a message to the hub agent via `POST /messages/`)
2. Run `statehub fix-consistency` from this checkout. Ask the operator
only if the CLI or State Hub API is unavailable.