| Node | Kind | State | Records | Tools | ms |
|---|---|---|---|---|---|
| intake | transform | passed | 1 | 0 | |
| map_terrain | agent | passed | 1 | 13 | 1316348 |
| hypothesize | agent | passed | 3 | 0 | 255219 |
| gather_witnesses | agent | passed | 3 | 27 | 3916493 |
| witness_gate | gate | passed | 1 | 0 | |
| adjudicate | agent | passed | 1 | 0 | 244544 |
| citation_gate | gate | passed | 1 | 0 | |
| propose_remediation | agent | passed | 1 | 1 | 199490 |
| human_approval write | human | passed | 1 | 0 | |
| write_back write | tool | passed | 1 | 0 | |
| report | transform | passed | 1 | 0 |
| id | Claim | Source | Supports | Refutes |
|---|---|---|---|---|
| e1 | In DataHub the dataset witnessgraph.marts.nightly_orders_snapshot declares no freshness/staleness assertion: its entity record contains only health INCIDENTS=PASS and relatedDocuments total 0, with no assertion, threshold, or evaluation-window field. | datahub_assertion urn:li:dataset:(urn:li:dataPlatform:dbt,witnessgraph.marts.nightly_orders_snap |
- | h1 |
| e2 | The tag urn:li:tag:root-cause:freshness_window_too_wide exists as a bare catalog entity (properties.name 'root-cause:freshness_window_too_wide') but is not attached to nightly_orders_snapshot — neither the dataset's assertion record nor its schema record lists any globalTags referencing it. | datahub_assertion urn:li:tag:root-cause:freshness_window_too_wide |
- | h1 |
| e3 | The writing job nightly_snapshot_job's only DataHub health signal is INCIDENTS=PASS, which is job-incident health rather than a freshness/staleness verdict, so 'PASS' here does not represent a freshness check evaluating the table as fresh. | datahub_assertion urn:li:dataJob:(urn:li:dataFlow:(airflow,witnessgraph,PROD),nightly_snapshot_j |
- | - |
| e4 | datahub.schema for nightly_orders_snapshot returns zero schema fields (totalFields 0) and an entity record with no globalTags and no assertion, independently corroborating that no freshness column, check, or too-wide-window instrument is registered on the dataset. | datahub_schema urn:li:dataset:(urn:li:dataPlatform:dbt,witnessgraph.marts.nightly_orders_snap |
- | h1 |
| e21 | The metric_definition_history table contains exactly one row (metric 'active_users_daily', version 1, day 1) and no row that defines or redefines any freshness metric for nightly_orders_snapshot within days 1-36. | warehouse_query warehouse://MTI-004/metric_definition_history |
- | h3 |
| e22 | The DataHub record for witnessgraph.marts.nightly_orders_snapshot declares no freshness assertion/check; its only freshness-related statement is the static description 'Refreshed every 24 hours' and its health shows only INCIDENTS=PASS. | datahub_assertion urn:li:dataset:(urn:li:dataPlatform:dbt,witnessgraph.marts.nightly_orders_snap |
- | h3 |
| e23 | In nightly_orders_snapshot, written_at_day equals day in every one of the 27 returned rows (days 1-18 present, then only even days 20-36), so the load/run-write column and the business-day column are numerically identical. | warehouse_query warehouse://MTI-004/nightly_orders_snapshot |
- | h3 |
| e24 | nightly_orders_snapshot is a table carrying a written_at_day column commented 'which run wrote this row', an INTEGER day marker (not a CURRENT_TIMESTAMP-populated column). | warehouse_query warehouse://MTI-004/nightly_orders_snapshot |
h3 | - |
| e25 | release_deploy_log's only in-window entries are product-feature deploys (quick_reorder day 12, price_alerts day 20); neither is a change to the freshness metric definition. | warehouse_query warehouse://MTI-004/release_deploy_log |
- | h3 |
| e26 | schema_migration_log's only entry is a CREATE INDEX on orders(customer_code) at day 2, with no freshness/metric definition change recorded in the window. | warehouse_query warehouse://MTI-004/schema_migration_log |
- | h3 |
| e11 | The ingest_job_runs table records only run_id, job, day, status (ok|missing), and rows_written, with no completion-timestamp, duration, or end-time column. | warehouse_query urn:li:dataJob:(urn:li:dataFlow:(airflow,witnessgraph,PROD),nightly_snapshot_j |
- | h2 |
| e12 | nightly_snapshot_job's recorded run status is 'ok' for days 1-18 and then alternates 'missing' on every odd day 19-35 and 'ok' on every even day 20-36. | warehouse_query urn:li:dataJob:(urn:li:dataFlow:(airflow,witnessgraph,PROD),nightly_snapshot_j |
- | h2 |
| e13 | nightly_orders_snapshot has a row for every day 1-18 and every even day 20-36 but no row for any odd day 19-35, and every existing row has written_at_day equal to its day. | warehouse_query urn:li:dataset:(urn:li:dataPlatform:dbt,witnessgraph.marts.nightly_orders_snap |
- | h2 |
| e14 | The DataHub record for nightly_orders_snapshot returns only health INCIDENTS=PASS and description 'Nightly snapshot of orders. Refreshed every 24 hours', with no freshness/staleness assertion object or threshold present. | datahub_assertion urn:li:dataset:(urn:li:dataPlatform:dbt,witnessgraph.marts.nightly_orders_snap |
h1 | h2 |
| e15 | DataHub records zero downstream consumers for nightly_orders_snapshot (DOWNSTREAM lineage total = 0). | datahub_lineage urn:li:dataset:(urn:li:dataPlatform:dbt,witnessgraph.marts.nightly_orders_snap |
- | h2 |
| e16 | metric_definition_history contains a single row (version 1, day 1, active_users_daily) and no freshness-metric edit for nightly_orders_snapshot within days 1-36. | warehouse_query urn:li:dataset:(urn:li:dataPlatform:dbt,witnessgraph.marts.nightly_orders_snap |
- | h3 |
This page is built from the run ledger alone. It never reads the agent's own summary of what it did.