6a7009b31c
Drive the cross-card implement->review->repair->re-review chain from inside the pod so unattended runs no longer stall once the first implementation card completes. Today that chain exists only as an external codex-shepherd session; this adds a bounded in-pod poll loop that reads board state via hermes_cli.kanban_db and creates Kanban follow-up cards (subscription lanes only) with no provider/metered path of its own. - kanban_supervisor.py (I/O shell) + supervisor_policy.py (pure state machine): impl-done+PR -> review; review SHIP -> mark impl ready-for-human (never merges/approves/clears WIP); review BLOCK -> bounded repair; repair new commit -> re-review. Fail-closed on unparseable/ambiguous state; per- (parent, head_commit) dedup safe beside the external shepherd; bounded review <->repair cycle count and max concurrent chains. - Deployed as a hardened non-root sidecar (drop ALL caps, read-only rootfs, no runtime-access/credential mount) alongside model-steward; scripts packaged in the coordinator configMapGenerator. - Gated by new kanban.auto_supervise config key (default false, re-read each tick like auto_decompose) so it is inert until the external shepherd retires. - Fix latent goal_max_turns NULL fallback in cli_lane_execution (1 -> documented default 20). - 62 new behavioral tests at 100% line+branch on both modules. Stacks on the merge train (base 5f27e50c). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
titan-iac
Flux-managed Kubernetes desired-state config for bstein.dev.
Canonical source URL:
ssh://git@scm.bstein.dev:2242/atlas/titan-iac.git
Scope
This repo contains cluster configuration consumed by Flux:
- platform/infrastructure manifests
- service manifests and kustomizations
- operational scripts for render/reconcile workflows
Apply model
I use Git + Flux as the source of truth and avoid manual in-cluster edits for durable changes.