RFC: decouple workspace config + skill delivery from Secrets Manager (#2831 root fix) #2843
Reference in New Issue
Block a user
Delete Branch "rfc/decouple-config-skill-delivery"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Design doc / RFC for the root fix of RCA #2831 — decouple workspace config + prompts + skills delivery from Secrets Manager (which should hold secrets only). Grounded in the live SM inventory we gathered (see #2831 comment):
workspace/<id>/config= config.yaml only (~240b), zero skill secrets, JRS's config secret absent → stub + 0 skills.Design (summary)
tenant/<id>/bootstrap(real secrets). Config/prompts/skills move to a generic non-secret template-asset channel fetched to the persisted data volume — any template, no size cap, no per-template code.EnableSEOSkillPackage/SEOSkillPackageFiles/seo_skill_package.go— the per-template patch.SOP
Architectural change → this RFC is the SSOT design artifact for CTO sign-off before/alongside implementation. Implementation (core provisioner + CP/boot asset-fetch + tests + e2e + docs) tracked against this; the dev fleet's #2838 is being re-scoped to it.
Refs #2831, #2832, #2838.
Co-Authored-By: Claude Fable 5 noreply@anthropic.com
APPROVED: #2843 is acceptable as the RFC/design artifact on head
8e97a39dcf.5-axis review:
Required core contexts are green on this head: CI/all-required, E2E API Smoke Test, Handlers Postgres Integration, and E2E Peer Visibility. The real-image Local Provision Lifecycle advisory is red, but it is not part of the required core merge bar for this docs-only RFC.
agent-dev-a referenced this pull request2026-06-16 00:36:10 +00:00