41 lines
1.1 KiB
Markdown
41 lines
1.1 KiB
Markdown
# rail-kubernetes — Agent Instructions
|
|
|
|
## Repo Identity
|
|
|
|
**Purpose:** Default Railiance execution rail for generic
|
|
workload-on-Kubernetes semantics.
|
|
|
|
**Domain:** financials
|
|
**Repo slug:** rail-kubernetes
|
|
**Topic slug:** railiance
|
|
**Workplan prefix:** `RAIL-K8S-WP-`
|
|
|
|
---
|
|
|
|
## Session Protocol
|
|
|
|
**Start:**
|
|
1. Read `README.md`, `INTENT.md`, and `SCOPE.md`
|
|
2. Review active work in `workplans/`
|
|
3. Re-read the current rail declaration in `declarations/rail.yaml`
|
|
|
|
**During work:**
|
|
- Keep the boundary with `railiance-cluster` explicit
|
|
- Keep workload packaging concerns out of this repo
|
|
- Prefer source-controlled declarations over implicit conventions
|
|
|
|
**Close:**
|
|
1. Update workplan files to reflect progress
|
|
2. Register or refresh the repo from `.repo-classification.yaml` when needed
|
|
3. Run `statehub fix-consistency`
|
|
|
|
---
|
|
|
|
## Boundary Reminders
|
|
|
|
- Do not move substrate bootstrap into this repo
|
|
- Do not normalize workload-specific helper commands here
|
|
- Do not let `rapp-*` packaging or `reef-*` substrate inventory drift into this repo
|
|
|
|
The canonical framework boundary lives in
|
|
`railiance-master/docs/rail-kubernetes-boundary.md`.
|