# reef-railiance — Agent Instructions

## Repo Identity

**Purpose:** Grouped Railiance home reef for substrate-boundary identity and
binding facts.

**Domain:** financials
**Repo slug:** reef-railiance
**Topic slug:** railiance
**Workplan prefix:** `REEF-RAILIANCE-WP-`

---

## Session Protocol

**Start:**
1. Read `README.md`, `INTENT.md`, and `SCOPE.md`
2. Review active work in `workplans/`
3. Re-read the current reef declaration in `declarations/reef.yaml`

**During work:**
- Keep the boundary with `railiance-infra` explicit
- Keep grouped reef membership and topology facts source-backed
- Prefer reef-local declarations over implicit operator memory

**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 generic S1 inventory or provisioning ownership into this repo
- Do not normalize generic rail or platform behavior here
- Do not fall back to one-repo-per-machine duplication for grouped home
  substrate members

The canonical framework boundary lives in
`railiance-master/docs/reef-first-wave-rollout.md` and
`railiance-infra/docs/reef-first-wave-source-map.md`.