Published

Data Processing Job / Pipeline Run

vr.wm-act-053 · wm-act-053-data-processing-job-pipeline-run

Represent one governed data-processing execution so agents can reconstruct what was requested, authorized, resolved, run, observed, produced and corrected without treating orchestration state as proof of data correctness or absorbing reusable definitions and data assets.

World Models Activities and processes ACT.DATA

Bundle → Layer → Finding → Questions Classifiers What it is Why it exists Distinguishing features What robots and AI may and may not do Moral aspects Owners Links to other meta-models Identity and identifiers Direct properties Recognition Capabilities and actions Hazards and failure modes Standards and interfaces Context of use Sources

Bundle → Layer → Finding → Questions Filled

6 bundles · 12 layers · 24 findings · 72 questions

Run identity, definition, trigger and authority Groups governed execution context for run identity, definition, trigger and authority.

Run root, definition version and parent pipeline

Groups source-qualified execution context for run root, definition version and parent pipeline.

Processing run root identity, namespace, owner, status and lineage head

Records processing run root identity, namespace, owner, status and lineage head as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish processing run root identity, namespace, owner, status and lineage head? identity
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by processing run root identity, namespace, owner, status and lineage head, with which policy and limits? composition
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to processing run root identity, namespace, owner, status and lineage head, and how is it corrected? privacy

Pipeline, job, workflow definition, revision, code location and parent reference

Records pipeline, job, workflow definition, revision, code location and parent reference as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish pipeline, job, workflow definition, revision, code location and parent reference? relationship
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by pipeline, job, workflow definition, revision, code location and parent reference, with which policy and limits? evidence
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to pipeline, job, workflow definition, revision, code location and parent reference, and how is it corrected? lifecycle

Trigger, schedule, request, priority and execution authority

Groups source-qualified execution context for trigger, schedule, request, priority and execution authority.

Trigger kind, event, schedule, manual request, source, correlation and deduplication

Records trigger kind, event, schedule, manual request, source, correlation and deduplication as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish trigger kind, event, schedule, manual request, source, correlation and deduplication? event
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by trigger kind, event, schedule, manual request, source, correlation and deduplication, with which policy and limits? ownership
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to trigger kind, event, schedule, manual request, source, correlation and deduplication, and how is it corrected? quality

Requester, operator, service account, authorization, priority, policy and approval

Records requester, operator, service account, authorization, priority, policy and approval as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish requester, operator, service account, authorization, priority, policy and approval? authority
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by requester, operator, service account, authorization, priority, policy and approval, with which policy and limits? measurement
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to requester, operator, service account, authorization, priority, policy and approval, and how is it corrected? security

Inputs, parameters, code, environment and effective interval Groups governed execution context for inputs, parameters, code, environment and effective interval.

Declared, resolved and consumed inputs, parameters and secrets

Groups source-qualified execution context for declared, resolved and consumed inputs, parameters and secrets.

Declared input, dataset version, partition, schema, contract and availability

Records declared input, dataset version, partition, schema, contract and availability as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish declared input, dataset version, partition, schema, contract and availability? requirement
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by declared input, dataset version, partition, schema, contract and availability, with which policy and limits? exception
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to declared input, dataset version, partition, schema, contract and availability, and how is it corrected? retention

Resolved parameter, configuration, secret reference, consumed value and redaction

Records resolved parameter, configuration, secret reference, consumed value and redaction as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish resolved parameter, configuration, secret reference, consumed value and redaction? security
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by resolved parameter, configuration, secret reference, consumed value and redaction, with which policy and limits? provenance
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to resolved parameter, configuration, secret reference, consumed value and redaction, and how is it corrected? interoperability

Code, package, image, runtime environment and data interval

Groups source-qualified execution context for code, package, image, runtime environment and data interval.

Source revision, build, package, image digest, dependency and entrypoint

Records source revision, build, package, image digest, dependency and entrypoint as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish source revision, build, package, image digest, dependency and entrypoint? provenance
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by source revision, build, package, image digest, dependency and entrypoint, with which policy and limits? process
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to source revision, build, package, image digest, dependency and entrypoint, and how is it corrected? decision

Runtime platform, environment, region, clock, locale, effective data interval and watermark

Records runtime platform, environment, region, clock, locale, effective data interval and watermark as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish runtime platform, environment, region, clock, locale, effective data interval and watermark? temporal
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by runtime platform, environment, region, clock, locale, effective data interval and watermark, with which policy and limits? validation
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to runtime platform, environment, region, clock, locale, effective data interval and watermark, and how is it corrected? state

Graph, tasks, stages, attempts, resources and state Groups governed execution context for graph, tasks, stages, attempts, resources and state.

Task, stage, graph, dependencies, mapping and branching

Groups source-qualified execution context for task, stage, graph, dependencies, mapping and branching.

Task, stage instance, definition binding, dependency, branch, map index and order

Records task, stage instance, definition binding, dependency, branch, map index and order as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish task, stage instance, definition binding, dependency, branch, map index and order? composition
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by task, stage instance, definition binding, dependency, branch, map index and order, with which policy and limits? privacy
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to task, stage instance, definition binding, dependency, branch, map index and order, and how is it corrected? identity

Declared graph, resolved graph, dynamic expansion, condition, skip and block

Records declared graph, resolved graph, dynamic expansion, condition, skip and block as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish declared graph, resolved graph, dynamic expansion, condition, skip and block? process
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by declared graph, resolved graph, dynamic expansion, condition, skip and block, with which policy and limits? lifecycle
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to declared graph, resolved graph, dynamic expansion, condition, skip and block, and how is it corrected? classification

Attempt, dispatch, worker, compute resource and state transitions

Groups source-qualified execution context for attempt, dispatch, worker, compute resource and state transitions.

Task attempt identity, sequence, dispatch, worker, host, container, resource and lease

Records task attempt identity, sequence, dispatch, worker, host, container, resource and lease as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish task attempt identity, sequence, dispatch, worker, host, container, resource and lease? identity
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by task attempt identity, sequence, dispatch, worker, host, container, resource and lease, with which policy and limits? quality
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to task attempt identity, sequence, dispatch, worker, host, container, resource and lease, and how is it corrected? relationship

Requested, queued, started, running, heartbeat, succeeded, failed, cancelled, timed out and unknown

Records requested, queued, started, running, heartbeat, succeeded, failed, cancelled, timed out and unknown as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish requested, queued, started, running, heartbeat, succeeded, failed, cancelled, timed out and unknown? state
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by requested, queued, started, running, heartbeat, succeeded, failed, cancelled, timed out and unknown, with which policy and limits? security
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to requested, queued, started, running, heartbeat, succeeded, failed, cancelled, timed out and unknown, and how is it corrected? authority

Outputs, lineage, validation, quality and observability Groups governed execution context for outputs, lineage, validation, quality and observability.

Declared, materialized, published outputs and lineage

Groups source-qualified execution context for declared, materialized, published outputs and lineage.

Declared output, dataset, artifact, schema, partition, destination and contract

Records declared output, dataset, artifact, schema, partition, destination and contract as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish declared output, dataset, artifact, schema, partition, destination and contract? requirement
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by declared output, dataset, artifact, schema, partition, destination and contract, with which policy and limits? retention
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to declared output, dataset, artifact, schema, partition, destination and contract, and how is it corrected? requirement

Materialized output, version, digest, size, row count, publication, visibility and derivation

Records materialized output, version, digest, size, row count, publication, visibility and derivation as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish materialized output, version, digest, size, row count, publication, visibility and derivation? provenance
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by materialized output, version, digest, size, row count, publication, visibility and derivation, with which policy and limits? interoperability
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to materialized output, version, digest, size, row count, publication, visibility and derivation, and how is it corrected? constraint

Validation, data quality, logs, metrics, traces and evidence

Groups source-qualified execution context for validation, data quality, logs, metrics, traces and evidence.

Schema, contract, reconciliation, quality rule, metric, threshold, result and waiver

Records schema, contract, reconciliation, quality rule, metric, threshold, result and waiver as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish schema, contract, reconciliation, quality rule, metric, threshold, result and waiver? validation
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by schema, contract, reconciliation, quality rule, metric, threshold, result and waiver, with which policy and limits? decision
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to schema, contract, reconciliation, quality rule, metric, threshold, result and waiver, and how is it corrected? event

Log, metric, trace, span, event, evidence source, scope, sampling, integrity and retention

Records log, metric, trace, span, event, evidence source, scope, sampling, integrity and retention as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish log, metric, trace, span, event, evidence source, scope, sampling, integrity and retention? evidence
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by log, metric, trace, span, event, evidence source, scope, sampling, integrity and retention, with which policy and limits? state
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to log, metric, trace, span, event, evidence source, scope, sampling, integrity and retention, and how is it corrected? temporal

Failure, retry, recovery, backfill, replay and outcome Groups governed execution context for failure, retry, recovery, backfill, replay and outcome.

Error, failure classification, retry, checkpoint and recovery

Groups source-qualified execution context for error, failure classification, retry, checkpoint and recovery.

Error, exception, exit status, failure domain, root cause, evidence and impact

Records error, exception, exit status, failure domain, root cause, evidence and impact as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish error, exception, exit status, failure domain, root cause, evidence and impact? exception
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by error, exception, exit status, failure domain, root cause, evidence and impact, with which policy and limits? identity
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to error, exception, exit status, failure domain, root cause, evidence and impact, and how is it corrected? composition

Retry policy, attempt, backoff, checkpoint, resume, idempotency and side effect

Records retry policy, attempt, backoff, checkpoint, resume, idempotency and side effect as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish retry policy, attempt, backoff, checkpoint, resume, idempotency and side effect? lifecycle
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by retry policy, attempt, backoff, checkpoint, resume, idempotency and side effect, with which policy and limits? classification
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to retry policy, attempt, backoff, checkpoint, resume, idempotency and side effect, and how is it corrected? evidence

Backfill, replay, rerun, cancellation, compensation and outcome

Groups source-qualified execution context for backfill, replay, rerun, cancellation, compensation and outcome.

Backfill, replay, rerun, recovery, predecessor, successor, trigger and data interval

Records backfill, replay, rerun, recovery, predecessor, successor, trigger and data interval as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish backfill, replay, rerun, recovery, predecessor, successor, trigger and data interval? provenance
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by backfill, replay, rerun, recovery, predecessor, successor, trigger and data interval, with which policy and limits? relationship
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to backfill, replay, rerun, recovery, predecessor, successor, trigger and data interval, and how is it corrected? ownership

Cancel, timeout, cleanup, rollback, compensation, partial result, final outcome and closure

Records cancel, timeout, cleanup, rollback, compensation, partial result, final outcome and closure as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish cancel, timeout, cleanup, rollback, compensation, partial result, final outcome and closure? lifecycle
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by cancel, timeout, cleanup, rollback, compensation, partial result, final outcome and closure, with which policy and limits? authority
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to cancel, timeout, cleanup, rollback, compensation, partial result, final outcome and closure, and how is it corrected? measurement

Governance, access, retention, correction and interoperability Groups governed execution context for governance, access, retention, correction and interoperability.

Ownership, access, privacy, retention, legal hold and disposition

Groups source-qualified execution context for ownership, access, privacy, retention, legal hold and disposition.

Owner, steward, operator, subject, purpose, access, redaction, disclosure and audit

Records owner, steward, operator, subject, purpose, access, redaction, disclosure and audit as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish owner, steward, operator, subject, purpose, access, redaction, disclosure and audit? privacy
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by owner, steward, operator, subject, purpose, access, redaction, disclosure and audit, with which policy and limits? requirement
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to owner, steward, operator, subject, purpose, access, redaction, disclosure and audit, and how is it corrected? exception

Retention class, legal hold, tombstone, disposition, cleanup and external record policy

Records retention class, legal hold, tombstone, disposition, cleanup and external record policy as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish retention class, legal hold, tombstone, disposition, cleanup and external record policy? retention
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by retention class, legal hold, tombstone, disposition, cleanup and external record policy, with which policy and limits? constraint
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to retention class, legal hold, tombstone, disposition, cleanup and external record policy, and how is it corrected? provenance

Correction, projection, conformance, loss and agent controls

Groups source-qualified execution context for correction, projection, conformance, loss and agent controls.

Amend, correct, invalidate, supersede, current head, reason, authority and lineage

Records amend, correct, invalidate, supersede, current head, reason, authority and lineage as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish amend, correct, invalidate, supersede, current head, reason, authority and lineage? provenance
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by amend, correct, invalidate, supersede, current head, reason, authority and lineage, with which policy and limits? event
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to amend, correct, invalidate, supersede, current head, reason, authority and lineage, and how is it corrected? process

OpenLineage, PROV, OTel, CloudEvents, CWL, WES, OGC, Airflow, Kubernetes, OCI projection and loss

Records openlineage, prov, otel, cloudevents, cwl, wes, ogc, airflow, kubernetes, oci projection and loss as source-qualified execution context while keeping reusable definitions, datasets, software, infrastructure, telemetry and records in their owning systems.

Which stable identities, execution scope, source-qualified values and explicit unknowns establish openlineage, prov, otel, cloudevents, cwl, wes, ogc, airflow, kubernetes, oci projection and loss? interoperability
Who requests, authorizes, schedules, executes, owns, observes, validates or is affected by openlineage, prov, otel, cloudevents, cwl, wes, ogc, airflow, kubernetes, oci projection and loss, with which policy and limits? temporal
Which scheduled, requested, queued, dispatched, started, heartbeat, completed, observed, ingested and knowledge times apply to openlineage, prov, otel, cloudevents, cwl, wes, ogc, airflow, kubernetes, oci projection and loss, and how is it corrected? validation

Classifiers Filled

Family: World Models
Category: Activities and processes
Entry kind: aggregate
Navigation path: NAV.ACT.DATA
Domain: ACT.DATA
Industry: Cross-industry
Tags: dataprocessingjobpipelinerunact.data

What it is Filled

Owns one processing-run identity; immutable bindings to a parent pipeline or job definition, code, parameters, input versions, environment and effective data interval; trigger and execution authority; task, stage and attempt instances; state events; output materialization and lineage context; validation, quality and telemetry references; failure, retry, recovery, backfill, cancellation and correction lineage. Pipeline, job and workflow definitions, schedules, datasets, data products, schemas, contracts, code, packages, images, configurations, secrets, identities, compute resources, logs, metrics, traces, incidents, provenance, access audits and record masters remain external.

In scope

Run identity and immutable execution bindings; trigger, request and authority; resolved graph, tasks, stages, attempts, resources, state and times
Input consumption and output materialization links; lineage, validation, data quality and observability references; failure, retry, recovery, backfill, correction, access, retention and projections

Out of scope

Creating or changing reusable pipeline, workflow, schedule, dataset, schema, code, package, image, secret, identity, compute, telemetry, incident or records masters
Equating dispatch with start, process exit with correct output, materialization with publication, or success with data quality and downstream acceptance
Autonomous execution, retry, cancellation, production mutation, secret retrieval, destructive cleanup or protected disclosure

Why it exists Filled

Distinguishing features Filled

Records one execution of a data pipeline or job, not the reusable definition held by the Data Pipeline model.
Binds the exact code, parameters, inputs, environment and data interval used, so a run can be reconstructed.
Treats orchestration status as separate from data correctness and publication.
Differs from data lineage, which aggregates relationships across many runs.

What robots and AI may and may not do Filled

Must not

Execute, retry, cancel or backfill a run without explicit delegation.
Publish outputs or mark them correct because the process exited successfully.
Access secrets or protected data used by the run.
Delete outputs or logs that other records depend on.
Mutate production systems as a side effect of recovery.

Only with a human decision

Approving a backfill, replay or rerun that overwrites published data.
Accepting outputs of a failed or partial run for downstream use.
Deleting run outputs under retention or legal hold rules.

May

Record run, task and attempt events from the orchestrator with source and time.
Report failures and propose a retry or rerun for approval.
Link outputs, quality results and telemetry to the run.
Compare two runs and list changed inputs, code or parameters.

Moral aspects Filled

Runs often process personal data, so inputs and outputs need purpose limits and access control.
Silent failures can spread wrong data into decisions that affect people.
Large runs consume energy and compute that should be justified.

Who is affected

Data subjects in the processed data
Downstream data consumers
Operators accountable for the platform

Owners Filled

Steward

Dimension owner and data-processing mandate

Roles

Data processing owner: Own execution purpose, service objectives, risk acceptance and accountable outcome interpretation.
Pipeline or workflow steward: Own reusable definitions, versions, dependencies and approved execution profiles.
Data owner or product steward: Own input and output assets, contracts, access, publication and retention decisions.
Execution operator or orchestrator: Own authorized dispatch, state observation, retry, cancellation and recovery within policy.
Platform and compute steward: Own runtime, capacity, isolation, resource and infrastructure evidence.
Data quality and validation steward: Own rules, metrics, thresholds, results, waivers and qualified acceptance.
Observability and incident steward: Own logs, metrics, traces, alerting, incident links, sampling and evidence integrity.
Security, privacy and records steward: Own identities, secret policy, protected views, disclosure, holds, retention and auditability.

Links to other meta-models Filled

references

WM-DAT-005 Data Pipeline - Bind the candidate parent pipeline and runnable graph without owning definition lifecycle or cascade behavior.
Dataset, data product, schema, contract and source-record models - Resolve declared, consumed, generated and published data identities, versions and contracts without copying their lifecycles.
Software, package, image, configuration, secret, identity and compute models - Resolve immutable execution artifacts, authorization and environment while external systems retain control and sensitive values.
Log, metric, trace, quality, incident, provenance, access-audit and records models - Resolve evidence and governance records without absorbing observability, incident or retention execution.

aligned

OpenLineage 1.53, PROV, OTel 1.60, CloudEvents 1.0.2, CWL 1.2, WES 1.1, OGC Processes 1.0, Airflow, Kubernetes Job, OCI Image and OpenAPI 3.1 - Project version-pinned lineage, telemetry, event, workflow, execution-service, orchestration, container and API views with scope and information-loss declarations.

neighbor

WM-DAT-005 Data Pipeline - The candidate incoming CONTAINS relation may bind this execution to a parent pipeline and runnable graph. This aggregate cannot own, edit or cascade-delete the reusable pipeline definition.
Dataset, data product, schema and data contract models - External masters own data identity, content, schema, contract, publication and lifecycle. The run stores resolved version, partition, digest, role and source-qualified consumption or generation links.
Software, package, image, configuration, secret and compute models - External masters own artifacts, sensitive values and infrastructure lifecycle. The run binds immutable revisions, digests, entrypoints, secret references, resource observations and environment snapshots.
Logs, metrics, traces, quality results and incidents - Observability and quality systems own evidence content and lifecycle. The run records typed links, scope, sampling, times, integrity and bounded interpretations.
Run, task, stage, attempt and retry - The aggregate owns one run and its execution membership. Each task or stage instance and attempt has independent identity, sequence, environment, state events and outcome; retry never overwrites failure.
OpenLineage, PROV, OTel, CloudEvents, CWL, WES, OGC Processes, Airflow, Kubernetes and OCI - These are versioned lineage, telemetry, event, workflow, API, orchestrator and runtime projections with different scopes. No mapping is assumed lossless or universally applicable.

parent

WM-DAT-005

What else AI and robots need to interact with it Filled

Sources Filled

PROV-DM: The PROV Data Model - World Wide Web Consortium
PROV-O: The PROV Ontology - World Wide Web Consortium
Data Catalog Vocabulary Version 3 - World Wide Web Consortium
Data on the Web Best Practices: Data Quality Vocabulary - World Wide Web Consortium
OpenLineage Object Model - OpenLineage Project
OpenTelemetry Specification - Cloud Native Computing Foundation OpenTelemetry Project
CloudEvents Specification - Cloud Native Computing Foundation
Common Workflow Language Workflow Description - Common Workflow Language Project
Workflow Execution Service API - Global Alliance for Genomics and Health
OGC API - Processes - Part 1: Core - Open Geospatial Consortium
Tasks - Apache Software Foundation
Jobs - Cloud Native Computing Foundation Kubernetes Project
OCI Image Format Specification - Open Container Initiative
Security and Privacy Controls for Information Systems and Organizations - National Institute of Standards and Technology
Regulation (EU) 2016/679 General Data Protection Regulation - European Union
Date and Time on the Internet: Timestamps - Internet Engineering Task Force
OpenAPI Specification 3.1.1 - OpenAPI Initiative

Open questions

Approve or reject candidate containment by WM-DAT-005 and register any data, software, compute, telemetry, incident and records relations.
Create execution profiles for batch, streaming, event-driven, scientific, geospatial, machine-learning, ETL, ELT and transactional workloads.
Test release-pinned interoperability mappings with conformance, round-trip and information-loss evidence.
Validate authorization, secret handling, resource, retry, side-effect, quality, observability, cleanup, privacy and retention policies for each deployment.
Obtain supplemental independent external review and resolve any material challenge before canonical promotion.
Claude and Grok each timed out on one bounded attempt; no independent external result was admitted.
The only relation-ledger edge is candidate incoming WM-DAT-005 CONTAINS WM-ACT-053; it is not treated as approved composition or cascade authority.
Batch, streaming, event, scientific, geospatial, machine-learning, ETL, ELT and transaction-processing executions require domain and runtime profiles.
OpenLineage, OTel, Airflow, Kubernetes, OCI, WES and OGC materials have different technical or sector scopes and require release-pinned validation.

Machine files

Card as JSON Specification AGENTS.md Source Card backlog vercy.card/1

Provenance

world-models research · reviewable-draft

Built from: models/wm-act-053-data-processing-job-pipeline-run/spec.yaml, ver-cy/world-models/card-supplements/wm-act-053-data-processing-job-pipeline-run.json