Territory Grounder · Field guide
Connect signals before granting effects
Reviewed 2026-11-02. Governed remediation is implemented. Fresh installs start in Shadow: read-only, with no actuation targets. Three repairs demonstrated in an isolated lab; broad production effectiveness is still being evaluated.
This is a setup map, not a blanket compatibility certification. Implemented means source is present in the reviewed snapshot. Reference means an adapter intended for portability, with no production validation claimed here. Validate credentials, supported operations and failure behavior against your own deployment.
On a small screen, scroll sideways to see every column.
| Connection | Direction / capability | Evidence level | Setup reference |
|---|---|---|---|
| LibreNMS, Alertmanager, CrowdSec | Receive alerts; read configured sources | Implemented | Ingest adapters |
| NetBox, Proxmox, vSphere, Slurpit | Read inventory and relationships | Implemented | CMDB adapters |
| Prometheus, OpenObserve, host diagnostics | Read metrics, logs and host evidence | Implemented | Observability adapters |
| SSH | Read diagnostics; scoped service/container effects | Implemented; service repair shown in lab | Effect setup |
| Proxmox | Read state; governed VM effects | Implemented; link and VM recovery shown in lab | Proxmox effect adapter |
| Kubernetes | Typed cluster operations through the actuation boundary | Implemented; no broad deployment claim here | Kubernetes adapter |
| Matrix, Mattermost, Twilio | Send notifications; configured approval/escalation flows | Implemented; behavior varies by channel | Notifier adapters |
| YouTrack | Read and update incident records | Implemented | Tracker adapter |
| Jira, GitHub Issues, ServiceNow | Issue/incident adapter interfaces | Reference | Tracker adapters |
| Slack, Teams, email | Notification interfaces | Reference | Notifier adapters |
| OpenAI-compatible gateway / LiteLLM | Send model inputs and receive completions | Implemented; endpoint and model dependent | Model adapters |
Setup order
- Start the local Shadow evaluation.
- Configure a model gateway and its provider budget. Local and remote models have different resource and data requirements.
- Add one alert source and read-only inventory/telemetry credentials. Confirm that objects resolve correctly and a real alert is investigated.
- Review the exact effect adapter, explicit target allowlists and independent verification signal before considering actuation.
The connector inventory provides the founding design and reference classifications. The operator quickstart explains the separate authorization, effect and runtime gates. Integration names alone do not grant write access.