7a55b259bf
Three fenced worker Pods claim Hermes Kanban runs through a coordinator that owns every state transition, with per-ordinal HMAC authority, a mediated broker-only SCM path, and durable per-ordinal workspaces. Content is the reviewed head of PR #18 (689bcb6e) with PR 16's and PR 19's contributions removed: they were merged in only to validate co-existence and are not prerequisites, so this branch no longer carries them as ancestors. Only PR 14 and PR 15 remain, because the broker boundary and the cli_lane_* decomposition are load-bearing for two of the fixed P0 boundaries. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
15 lines
531 B
YAML
15 lines
531 B
YAML
# services/hermes/scm-common/kustomization.yaml
|
|
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
configMapGenerator:
|
|
- name: hermes-scm-boundary-v2
|
|
files:
|
|
- gitea_api.py=scripts/gitea_api.py
|
|
- gitea_api_policy.py=scripts/gitea_api_policy.py
|
|
- scm_broker.py=scripts/scm_broker.py
|
|
- scm_broker_io.py=scripts/scm_broker_io.py
|
|
- scm_broker_server.py=scripts/scm_broker_server.py
|
|
- scm_broker_client.py=scripts/scm_broker_client.py
|
|
options:
|
|
disableNameSuffixHash: true
|