# railiance-enablement — Claude Code Instructions **OAS Stack Level:** S4 Developer Enablement **Scope:** Tools that allow system evolution — CI/CD pipelines, developer portal, platform templates, SDKs, buildpacks. **Pre-condition:** `railiance-platform` must be operational before enablement tooling can depend on platform services. ## Custodian State Hub Integration Domain: **railiance** — topic ID: `ca369340-a64e-442e-98f1-a4fa7dc74a38` State Hub: http://127.0.0.1:8000 ### Session Protocol **Step 1 — Orient** Read the offline-safe brief first: ```bash cat .custodian-brief.md ``` Then call the MCP tool for richer context (skip if unreachable): ``` get_domain_summary("railiance") ``` **Step 2 — Scan workplans** ``` ls workplans/ # read all active workplans; note todo/in_progress tasks ``` **Step 3 — Present brief** 1. Active workstreams for railiance with `[repo:railiance-enablement]` tasks 2. Pending tasks from local workplans 3. Goal guidance from summary (needs_workplan / alignment_warnings) 4. Suggested next action **During work:** use `record_decision()`, `add_progress_event()`, `resolve_decision()`. **Session close:** `add_progress_event()` with topic_id and workstream_id. > Design boundary: hub is read model. Bootstrap tools are First Session > Protocol only. Work originates as files per ADR-001. ### Repo Boundary Rule (ADR-003) This repo owns **S4 Developer Enablement only**. Do not manage: - OS-level concerns → `railiance-infra` (S1) - Kubernetes runtime → `railiance-cluster` (S2) - Platform services → `railiance-platform` (S3) - Application deployments → `railiance-apps` (S5) Reference: `railiance-infra/docs/adr/ADR-003-railiance-5repo-stack-architecture.md` ### Workplan Convention (ADR-001) File location: `workplans/RAIL-EN-WP-NNNN-.md` Prefix: `RAIL-EN` ### SBOM After updating dependencies: ```bash cd ~/the-custodian/state-hub make ingest-sbom REPO=railiance-enablement SCAN=1 REPO_PATH=/home/worsch/railiance-enablement ``` ### Quick Reference `~/the-custodian/state-hub/mcp_server/TOOLS.md`