# SCOPE

## One-liner

Package and operate the `canned-prompts` hosted registry and index on
Railiance, without moving product ownership into an operations repository.

## In Scope

- `declarations/rapp.yaml` — the managed-workload declaration: composition,
  image pin, rollout, smoke and rollback contracts.
- `manifests/` — namespace, external secrets, migration Job, and the runtime
  Deployment, Service, ServiceAccount and NetworkPolicies.
- `tools/smoke.sh` — deployment-level verification, delegating the
  service-level half to `canned-prompts`.
- Rollout, rollback and the network posture.

## Out of Scope

- What a valid prompt package is, what any endpoint means, the schema and its
  migrations, and image publication — all `canned-prompts`.
- PostgreSQL topology, isolation, backups, credential issuance — `rapp-postgres`
  and the platform credential broker.
- Who may publish. The service's identity is a single shared token proving
  "the operator"; per-publisher identity is an open question upstream, and this
  repo must not imply finer control than exists.

## Current State

**Declared.** The image is published and pinned by digest
(`sha256:e0ded3c7fe2548c910445deaa31ec42e84f129a92aa324841e231a53fee1f123`), the manifests parse, and
`readiness_state` is `declared`. Nothing is deployed yet.

One thing blocks a first rollout: the database and its roles do not exist.
`rapp-postgres` has the request as `consumers/canned-prompts.yaml`; minting the
OpenBao credentials is its operator's step, not this repo's.

`workplans/RCP-WP-0002-first-deployment.md` carries the remaining sequence.

## Verification

This repo builds nothing.

```bash
for f in manifests/*.yaml; do python3 -c "import yaml,sys; list(yaml.safe_load_all(open('$f')))"; done
bash -n tools/smoke.sh
NS=canned-prompts ./tools/smoke.sh        # against a live deployment
```

## Getting Oriented

- Intent and boundaries: `INTENT.md`
- The declaration: `declarations/rapp.yaml`
- What the service is: `canned-prompts/service/README.md`
- Deployment guide: `repo-manager/docs/RailianceAppDeploymentGuide.md`