DHCP

Obsidian Tek · DataHub Compliance Posture

Governance evidence,
given an address.

DHCP maps DataHub metadata into a bound, scoreless Supporting Evidence Package and a concise Posture Brief. It preserves exact asset sets, explains their possible relevance, and safely hands reviewed context back to DataHub.

See the workflow View the source

Under three minutes

Watch the evidence path

Watch on YouTube ↗

Demo video is being finalized.

The embed activates when the public YouTube video ID is added to site/assets/site.js.

Evidence-first by design

Catalog context in. Reviewable evidence out.

  1. 01

    Observe

    Read schema-only catalog metadata, ownership, domains, lineage, labels, and structured properties.

  2. 02

    Bind

    Mechanically map observations to narrow, project-authored evidence-profile interpretations.

  3. 03

    Explain

    Optionally use a bounded LangChain agent and DataHub Agent Context Kit for validated narration.

  4. 04

    Hand off

    Route gaps for human review, then apply approved values with independent DataHub read-back.

Synthetic, schema-only showcase

See every layer working together

Choose a subject, then use the arrow keys, swipe, or slide controls. Screenshots contain synthetic metadata only; no row data or secrets.

One deterministic payload

Choose your level of detail

Executive view

Posture Brief

Concise HTML with raw observation counts and profile interpretations.

Open the final brief → Complete view

Evidence Package

Markdown with complete mappings, limitations, and catalog actions.

Open the final package → Machine-readable

Bound JSON

Complete observed and not-observed asset sets with shared provenance.

Open the bound payload → Apache-2.0 code

GitHub

Assessment, profile YAML, safe write-back, demo stack, and tests.

Explore the repository →

Claim boundary

Evidence, not a verdict.

DHCP reports catalog-visible supporting evidence. It is not legal advice, an audit, attestation, certification, readiness rating, or determination of conformity. Missing metadata means “not observed in the selected catalog snapshot,” not proof that a real-world safeguard or process is absent.