# TechFabric Radar

> Governed mission control for running data and ML workloads on Databricks.

Role: Workload observability
Databricks surfaces: Databricks Jobs, Lakebase, Unity Catalog, Temporal
Status: Domain module, policies, state machines, and org-scoped projections are implemented, with a Temporal intervention worker and a Databricks effector.
Documentation: https://radar.techfabric.com
Canonical: https://www.techfabric.com/accelerators/radar

---

## The problem

Monitoring tells you a job failed. It rarely tells you whether that breach matters, who is allowed to intervene, or what was actually done about it last time. The intervention itself usually happens in a terminal, unlogged.

## How it works

Monitors carry declared service level objectives. When reality breaches one, Radar triages the anomaly and makes every intervention a governed action with a policy check and an audit record. Telemetry ingest is deliberately append-only and stays outside the governed pipeline; only state transitions pass through it.

## What it changes for you

Someone is watching your live workloads, and every intervention is on the record. Declared SLOs replace tribal knowledge about what healthy looks like, and a two in the morning fix becomes a governed action with an audit trail.

## Questions

### How is this different from the monitoring we already have?

Monitoring tells you a job failed. Radar carries declared service level objectives per workload, so it can tell you whether the breach matters, who is allowed to intervene, and what was actually done about it last time. If you are not sure the workspace is worth that yet, the Databricks Health Check at /databricks/health-check is the two-week way in.

### What does a governed intervention mean in practice?

Restarting a job or rerouting a pipeline runs as a policy-checked action with an audit record, executed as a durable workflow. A fix at two in the morning stops being an untracked click in a terminal.

### Does it ingest all our telemetry?

Telemetry ingest is deliberately append-only and stays outside the governed pipeline. Only state transitions pass through it, which keeps the audit trail meaningful instead of drowning in events.