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
Toward a production deployment as rapp-canned-prompts on railiance01.
A rapp repo packages a deployable its ownership_repo already produces —
rapp.yaml pins upstream_components.version to a container digest.
canned-prompts has no deployable: a CLI with no HTTP surface, no image, no
database. A rapp pointing at nothing is a stub that tells the fleet's tooling a
deployment exists when none does. So the service comes first, and
rapp-canned-prompts is created once there is a digest to pin.
Decisions recorded: hosted registry plus index as the v1 surface, the service
living in canned-prompts so rapp.yaml gets ownership_repo: canned-prompts (the
sbom-nexus shape), and deployment as a platform service whose data is
nevertheless tenant-keyed from the first migration per
business-app-service-contract section 1.3 — cheap now, a rewrite later.
Stack matches state-hub and sbom-nexus: FastAPI, SQLAlchemy, Alembic,
PostgreSQL. The deployment guide additionally requires unauthenticated
/healthz and /readyz.
INTENT's deliberate boundary still holds: the service hosts packages and does
not become an agent runtime. reference/ stays untouched and dependency-light as
the format's conformance witness.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Bjefh8NUiEiahN4JLwoSKM
EOF
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 388925@bnt-lap001
Assistant-Session: 3507023f-e0fd-4a1e-9d90-a0d4217d1502
