ab16b5ca6b
reset restores only what the demo itself creates: the fixture ConfigMap, the demo repository's open repair pull requests and their branches. Real service repositories are deliberately untouched - those issues are genuine triage records, and deleting them to tidy a demo would destroy the evidence the system exists to produce. monitor streams the flow in the stages of mermaid/TestAutomation.mmd, so a second terminal can be followed against the chart: Detect and gather, Hermes analysis, Ariadne policy gates, Ariadne response, Inspectable outputs. Each stage prints the evidence that moved it, since the claim the chart makes is that every step is answerable from data rather than asserted. Read-only. 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.