coulomb/rapp-canned-prompts
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Publish the image, pin it by digest, and request the database

Browse source 
RCP-WP-0002-T01 done. Published
forgejo.coulomb.social/coulomb/canned-prompts:0.1.0 and pinned
sha256:e0ded3c7fe25... in declarations/rapp.yaml and both manifests.

Pinned by digest rather than tag: a tag can be moved, and
live-image-digest-match would then pass against something that is no longer
what this repo reviewed. Verified after the push by fetching the manifest back
by digest rather than trusting the push output.

readiness_state draft -> declared. Not deployed, so not `deployed`.

T02 requested rather than performed. rapp-postgres now carries
consumers/canned-prompts.yaml against its documented PostgresConsumer shape,
and its agent has the request. `make provision-consumers`, which mints the
OpenBao credentials, was deliberately not run: credential issuance belongs to
that repo's operator, and running it from the consuming side would take a
decision that is not this repo's, however available the script is.

T03 and T04 move to wait behind it.

Also corrected a check of my own: I briefly read the cluster list as lacking
platform-pg-2 and suspected the manifests targeted a host that does not exist.
That was my own truncated output. platform-pg-2 is present and healthy, and the
postgres-client label matches what sbom-nexus actually carries in the cluster
rather than only what its repo says.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Bjefh8NUiEiahN4JLwoSKM

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 388925@bnt-lap001
Assistant-Session: 3507023f-e0fd-4a1e-9d90-a0d4217d1502
This commit is contained in:
tegwick 2026-09-07 08:43:35 +02:00
parent f6f7390651
commit 8dc6257d93
5 changed files with 52 additions and 29 deletions
Download patch file Download diff file Expand all files Collapse all files

15
SCOPE.md
View file

@ -27,16 +27,15 @@ Railiance, without moving product ownership into an operations repository.
## Current State
**Draft.** The package is written and its manifests parse, but nothing is
deployed and `readiness_state` is `draft`. Two things block a first rollout,
both operator actions rather than authoring ones:
**Declared.** The image is published and pinned by digest
(`sha256:e0ded3c7fe2548c910445deaa31ec42e84f129a92aa324841e231a53fee1f123`), the manifests parse, and
`readiness_state` is `declared`. Nothing is deployed yet.
- the image has never been published, so no registry digest exists to pin
(`declarations/rapp.yaml` says `pending-publication` rather than carrying a
placeholder that could be mistaken for something deployable);
- database roles and OpenBao credentials are not provisioned.
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 both.
`workplans/RCP-WP-0002-first-deployment.md` carries the remaining sequence.
## Verification