1. Pipeline

VendorCite control plane · seed data is fictional. Layout based on the MIT-licensed shadcn/studio admin template.

  • VendorCitecontrol plane
Catalogue
  • Overview
  • Entities
  • Search
  • Watchlists
Intelligence
  • Trust Scores
  • Compare
  • Changes
  • Alerts
  • Market maps
  • Reports
Commercial
  • Data Blocks
  • Marketplace
  • Usage & billing
Operations
  • Review queue
  • Ingest runs
  • Pipeline
  • Data quality
  • Operators
  • Audit

Pipeline runs

0

this tenant has never run the pipeline

Claims written

0

by those runs, across every outcome

Data plane

reachable

http://data-service:8000

Fan-out sweeps

8

every 900s

Data plane
Where /v1/pipeline/run sends a target for retrieval and extraction. A pipeline run fails before it opens a run row when this is unreachable, so a run that wrote nothing because the fetcher was down never appears as a run that found nothing.

Address

http://data-service:8000

from DATA_SERVICE_URL

Reachable

yes

Parser version

bronze-lander/1

Extraction model

not configured

Alert fan-out
The sweep that delivers an alert whose tenant is on delayed data, after the delay has elapsed and with no ingest running.

Interval

900s

Sweeps

8

Last sweep

2026-08-28 21:26:24

0 alert(s) created by it

Alerts created

0

since this process started

Runs by outcome
Counted by the control plane over this tenant's whole run history, not over the page of runs below.
OutcomeRunsClaims writtenLatest started
No pipeline run has ever been recorded for this tenant. Every claim in the catalogue arrived by seed file or by a direct POST to /v1/ingest.
Pipeline runs
The control plane stamps a promotion run pipeline/…; /v1/ingest/runs has no parameter for that, so the pipeline runs are picked out of a page of runs of every kind. The newest 50 were read. That window is full, so an older pipeline run may exist below the cut and is not shown here.
TargetStartedTookFetchedStoredClaimsOutcome
None of the 50 most recent ingest runs came from the pipeline; they were direct writes to /v1/ingest.
What a run produces
Promotion to Gold runs through the review queue, so entitlement, audit and change events sit on one path.

Bronzewritten by Data plane

Raw retrieval. Source payload and retrieval metadata, unnormalised.

Silverwritten by Data plane

Normalised and entity-resolved. Conflicting claims recorded side by side, not collapsed.

Gold

written by Control plane

Human-verified, scored, with an evidence block on every field. The only tier served.

A correction inserts a new claim and marks the previous one superseded. Nothing is updated in place, so what was true on a given date stays reconstructable.