Configure
Settings
Connection state and the audit target this console reports on.
Connection
DataHub
- State
- read-only demo, no catalog connected
- Server
not set- Detail
- This deployment is read-only and connects to no catalog. Every audit shown was produced against a live DataHub Core 1.5.0.6 instance.
- Latency
- -
- Write-back
- unavailable
Nothing is misconfigured here. Run the console locally against your own DataHub and this card fills in, the status turns green, and write-back becomes available.
Audit target
What this console audits
- Name
credit_default- Scenario
scenarios/credit_default/scenario.json- Transformation
examples/leaky_feature.sql- Remediation
examples/remediation.sql- Post-outcome table
payment_events_after_decision- Target URN
- not bound
- Synthetic data
- yes
Change the target with hindsight serve --audit path/to/audit.json, or set
HINDSIGHT_AUDIT. When Target URN is bound, Hindsight refuses to
publish this verdict to any other asset — writing evidence onto something it does not
describe would put false findings in your catalog.
Safety
Operating boundaries
- Dry-run by default. Nothing is written to the catalog without explicit approval.
- Every write is re-read. A write that cannot be read back is treated as a failure.
- No authentication. This console can write to your catalog. It binds to loopback by default; put it behind an authenticating proxy before exposing it.
- An LLM cannot promote a verdict. Only deterministic evidence reaches
confirmed.