net-kingdom/capabilities/playbooks
tegwick 5d5f15df55
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
NK-WP-0056-T14 done: SecurityCaseType oidc-service-client 0.1 (proposed)
Confidential client_credentials service clients: one audience, closed
resource scopes, fixed service subject and tenant, at most 15m; secret minted
in custody, read only by KeyCape (ESO) and the consumer's own bound
Kubernetes-auth role (no Secret copy). First case nk-bind-executor-approval
(approval-engine create/read/consume as service:nk-bind-executor). Capability
net-kingdom.keycape-service-client-registration; keycape-client.py renders
service clients in key-cape's shape (adoption of secrets-engine-approval
reproduces key-cape's record). Acknowledgement memo r1 validated against
informed-decision intake and State Hub dispatcher; hub decision f8044f81.
Test fixture's synthetic signing key is now computed, not a literal (secret
scan generic-api-key).

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 5502@bnt-lap001
Assistant-Session: 68b3b02f-5d0f-4e71-8421-796f62e50196
2026-10-31 21:30:21 +01:00
..
net-kingdom.keycape-client-registration.yaml NK-WP-0048-T09: keycape-client entry point and declaration 2026-10-08 23:03:00 +02:00
net-kingdom.keycape-service-client-registration.yaml NK-WP-0056-T14 done: SecurityCaseType oidc-service-client 0.1 (proposed) 2026-10-31 21:30:21 +01:00
net-kingdom.local-identity.yaml feat(orchestration): compose security scenarios 2026-08-23 12:40:52 +02:00