## Repo boundary

This repo owns the **read-only, cross-kind configuration map and evidence layer** —
the federated configuration surface registry and its documentation. Its novel core
is the cross-kind surface classification, the layering order, and effective-config
*path* rendering. Everything else is referenced, not owned.

It does **not** own (sister repo → relationship):

- Configuration *vocabulary* / concepts (`info-tech-canon`) — **map, don't redefine**
- Repository *scanning / candidate / approval* machinery (`repo-scoping`) — **reuse**
- *Domain placement & ownership identity* (`domain-tree`) — **reference**
- The *registry schema & federation hub* (`reuse-surface`) — **federate under it**
- *Runtime resolution & control* of feature availability, incl. resolver and kill
  switches (`feature-control`) — **link, never re-derive**
- Repo template bootstrap (`repo-seed`)
- Secret *values* / live config (`railiance-platform` / OpenBao) — reference only
- State Hub graph/identity store (`state-hub`) — contribute config-typed edges
- Deployment and infrastructure execution (`railiance-infra`, `ops-bridge`)

See `docs/ecosystem-boundaries.md` for the full boundary-and-reuse analysis.