4e3be5f7e4
Some checks failed
Tests / Declarative: Post Actions testing.tests.test_repo_structure.test_knowledge_service_mirror_matches_source failed
Five corrections to how the monitor explains itself, plus code-demo support. The authorization is now described as what it is: a match between an action Ariadne already has code to perform, an action id Hermes is permitted to request, and the action Hermes actually recommended. Hermes cannot add to that registry, and the recommendation proceeds only because it names something already in it. The editorial line about pull requests is gone. The repair now reads as a change rather than a value: the field said unhealthy when the build failed and says healthy because Ariadne just patched it. The rebuild stage says plainly that the operational branch is complete and that neither the human-required response nor the optional source proposal is entered, rather than leaving the reader to infer it from silence. Inspectable outputs states that on the chart it is the 'records and artifacts' edge out of the whole response box, not out of one branch - every path ends there. The layout makes it look like it belongs to the proposal path alone. follows hermes-code-demo, which takes the proposal branch: the stages now read as a patch proposal and a pull request instead of being mislabelled an escalation. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
titan-iac
Flux-managed Kubernetes desired-state config for bstein.dev.
Canonical source URL:
ssh://git@scm.bstein.dev:2242/bstein/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.