coulomb/railiance-platform
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

CCR-2026-0051: binding confirmed on native evidence, status applied; RPF-WP-0061 follow-up D
All checks were successful
CCR intake gate / gate (push) Successful in 1m10s
Details
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 306568@bnt-lap001
Assistant-Session: 8bdf8150-ea56-41e7-9132-13f04f6b0b91
This commit is contained in:
codex 2026-10-18 12:58:39 +02:00
parent 7e7ca8be51
commit 79fbb4bdb5
2 changed files with 27 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

5
workplans/RPF-WP-0061-self-service-ccr-intake.md
View file

@ -172,6 +172,11 @@ MFA-backed OIDC login so clients can sync themselves; (C) separate Forgejo and
OS identities per agent so `ccr/*` can be restricted. Both stem from the
finding that every workstation agent pushes as Forgejo user `tegwick` with the
key `workstation-automation`.
(D, ops-mason point 5) Self-service teardown: deactivate lifecycle event filed
by the client and applied under ops-mason-construct. Founder to decide whether a
deactivate needs a decision. Until then teardown goes through a platform session.
ops-mason points 1-4 were adopted in 7e7ca8b (`plan_ref`, `render-policy`,
single hub decision, readback before `record-evidence`).
## T05 — Client documentation and first self-service CCR