{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-act-053","code":"wm-act-053-data-processing-job-pipeline-run","url":"https://ver.cy/models/wm-act-053-data-processing-job-pipeline-run/","name":"Data Processing Job / Pipeline Run","alternateNames":[],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Activities and processes","entryKind":"aggregate","plane":"","domain":["ACT.DATA"],"industry":["Cross-industry"],"navPath":"NAV.ACT.DATA","tags":["data","processing","job","pipeline","run","act.data"],"facets":{}},"whatItIs":"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.","purpose":"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.","scope":{"in":["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":["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"],"boundaries":[{"neighbor":"WM-DAT-005 Data Pipeline","distinction":"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."},{"neighbor":"Dataset, data product, schema and data contract models","distinction":"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."},{"neighbor":"Software, package, image, configuration, secret and compute models","distinction":"External masters own artifacts, sensitive values and infrastructure lifecycle. The run binds immutable revisions, digests, entrypoints, secret references, resource observations and environment snapshots."},{"neighbor":"Logs, metrics, traces, quality results and incidents","distinction":"Observability and quality systems own evidence content and lifecycle. The run records typed links, scope, sampling, times, integrity and bounded interpretations."},{"neighbor":"Run, task, stage, attempt and retry","distinction":"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."},{"neighbor":"OpenLineage, PROV, OTel, CloudEvents, CWL, WES, OGC Processes, Airflow, Kubernetes and OCI","distinction":"These are versioned lineage, telemetry, event, workflow, API, orchestrator and runtime projections with different scopes. No mapping is assumed lossless or universally applicable."}]},"distinguishingFeatures":["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."],"structure":{"bundles":[{"id":"run-identity-definition-trigger-and-authority","name":"Run identity, definition, trigger and authority","description":"Groups governed execution context for run identity, definition, trigger and authority.","layers":[{"id":"run-root-definition-version-and-parent-pipeline","name":"Run root, definition version and parent pipeline","description":"Groups source-qualified execution context for run root, definition version and parent pipeline.","findings":[{"id":"processing-run-root-identity-namespace-owner-status-and-lineage-head","name":"Processing run root identity, namespace, owner, status and lineage head","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish processing run root identity, namespace, owner, status and lineage head?","id":"processing-run-root-identity-namespace-owner-status-and-lineage-head-q01","kind":"identity"},{"text":"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?","id":"processing-run-root-identity-namespace-owner-status-and-lineage-head-q02","kind":"composition"},{"text":"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?","id":"processing-run-root-identity-namespace-owner-status-and-lineage-head-q03","kind":"privacy"}]},{"id":"pipeline-job-workflow-definition-revision-code-location-and-parent-reference","name":"Pipeline, job, workflow definition, revision, code location and parent reference","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish pipeline, job, workflow definition, revision, code location and parent reference?","id":"pipeline-job-workflow-definition-revision-code-location-and-parent-reference-q01","kind":"relationship"},{"text":"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?","id":"pipeline-job-workflow-definition-revision-code-location-and-parent-reference-q02","kind":"evidence"},{"text":"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?","id":"pipeline-job-workflow-definition-revision-code-location-and-parent-reference-q03","kind":"lifecycle"}]}]},{"id":"trigger-schedule-request-priority-and-execution-authority","name":"Trigger, schedule, request, priority and execution authority","description":"Groups source-qualified execution context for trigger, schedule, request, priority and execution authority.","findings":[{"id":"trigger-kind-event-schedule-manual-request-source-correlation-and-deduplication","name":"Trigger kind, event, schedule, manual request, source, correlation and deduplication","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish trigger kind, event, schedule, manual request, source, correlation and deduplication?","id":"trigger-kind-event-schedule-manual-request-source-correlation-and-deduplication-q01","kind":"event"},{"text":"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?","id":"trigger-kind-event-schedule-manual-request-source-correlation-and-deduplication-q02","kind":"ownership"},{"text":"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?","id":"trigger-kind-event-schedule-manual-request-source-correlation-and-deduplication-q03","kind":"quality"}]},{"id":"requester-operator-service-account-authorization-priority-policy-and-approval","name":"Requester, operator, service account, authorization, priority, policy and approval","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish requester, operator, service account, authorization, priority, policy and approval?","id":"requester-operator-service-account-authorization-priority-policy-and-approval-q01","kind":"authority"},{"text":"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?","id":"requester-operator-service-account-authorization-priority-policy-and-approval-q02","kind":"measurement"},{"text":"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?","id":"requester-operator-service-account-authorization-priority-policy-and-approval-q03","kind":"security"}]}]}]},{"id":"inputs-parameters-code-environment-and-effective-interval","name":"Inputs, parameters, code, environment and effective interval","description":"Groups governed execution context for inputs, parameters, code, environment and effective interval.","layers":[{"id":"declared-resolved-and-consumed-inputs-parameters-and-secrets","name":"Declared, resolved and consumed inputs, parameters and secrets","description":"Groups source-qualified execution context for declared, resolved and consumed inputs, parameters and secrets.","findings":[{"id":"declared-input-dataset-version-partition-schema-contract-and-availability","name":"Declared input, dataset version, partition, schema, contract and availability","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish declared input, dataset version, partition, schema, contract and availability?","id":"declared-input-dataset-version-partition-schema-contract-and-availability-q01","kind":"requirement"},{"text":"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?","id":"declared-input-dataset-version-partition-schema-contract-and-availability-q02","kind":"exception"},{"text":"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?","id":"declared-input-dataset-version-partition-schema-contract-and-availability-q03","kind":"retention"}]},{"id":"resolved-parameter-configuration-secret-reference-consumed-value-and-redaction","name":"Resolved parameter, configuration, secret reference, consumed value and redaction","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish resolved parameter, configuration, secret reference, consumed value and redaction?","id":"resolved-parameter-configuration-secret-reference-consumed-value-and-redaction-q01","kind":"security"},{"text":"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?","id":"resolved-parameter-configuration-secret-reference-consumed-value-and-redaction-q02","kind":"provenance"},{"text":"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?","id":"resolved-parameter-configuration-secret-reference-consumed-value-and-redaction-q03","kind":"interoperability"}]}]},{"id":"code-package-image-runtime-environment-and-data-interval","name":"Code, package, image, runtime environment and data interval","description":"Groups source-qualified execution context for code, package, image, runtime environment and data interval.","findings":[{"id":"source-revision-build-package-image-digest-dependency-and-entrypoint","name":"Source revision, build, package, image digest, dependency and entrypoint","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish source revision, build, package, image digest, dependency and entrypoint?","id":"source-revision-build-package-image-digest-dependency-and-entrypoint-q01","kind":"provenance"},{"text":"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?","id":"source-revision-build-package-image-digest-dependency-and-entrypoint-q02","kind":"process"},{"text":"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?","id":"source-revision-build-package-image-digest-dependency-and-entrypoint-q03","kind":"decision"}]},{"id":"runtime-platform-environment-region-clock-locale-effective-data-interval-and-watermark","name":"Runtime platform, environment, region, clock, locale, effective data interval and watermark","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish runtime platform, environment, region, clock, locale, effective data interval and watermark?","id":"runtime-platform-environment-region-clock-locale-effective-data-interval-and-watermark-q01","kind":"temporal"},{"text":"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?","id":"runtime-platform-environment-region-clock-locale-effective-data-interval-and-watermark-q02","kind":"validation"},{"text":"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?","id":"runtime-platform-environment-region-clock-locale-effective-data-interval-and-watermark-q03","kind":"state"}]}]}]},{"id":"graph-tasks-stages-attempts-resources-and-state","name":"Graph, tasks, stages, attempts, resources and state","description":"Groups governed execution context for graph, tasks, stages, attempts, resources and state.","layers":[{"id":"task-stage-graph-dependencies-mapping-and-branching","name":"Task, stage, graph, dependencies, mapping and branching","description":"Groups source-qualified execution context for task, stage, graph, dependencies, mapping and branching.","findings":[{"id":"task-stage-instance-definition-binding-dependency-branch-map-index-and-order","name":"Task, stage instance, definition binding, dependency, branch, map index and order","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish task, stage instance, definition binding, dependency, branch, map index and order?","id":"task-stage-instance-definition-binding-dependency-branch-map-index-and-order-q01","kind":"composition"},{"text":"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?","id":"task-stage-instance-definition-binding-dependency-branch-map-index-and-order-q02","kind":"privacy"},{"text":"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?","id":"task-stage-instance-definition-binding-dependency-branch-map-index-and-order-q03","kind":"identity"}]},{"id":"declared-graph-resolved-graph-dynamic-expansion-condition-skip-and-block","name":"Declared graph, resolved graph, dynamic expansion, condition, skip and block","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish declared graph, resolved graph, dynamic expansion, condition, skip and block?","id":"declared-graph-resolved-graph-dynamic-expansion-condition-skip-and-block-q01","kind":"process"},{"text":"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?","id":"declared-graph-resolved-graph-dynamic-expansion-condition-skip-and-block-q02","kind":"lifecycle"},{"text":"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?","id":"declared-graph-resolved-graph-dynamic-expansion-condition-skip-and-block-q03","kind":"classification"}]}]},{"id":"attempt-dispatch-worker-compute-resource-and-state-transitions","name":"Attempt, dispatch, worker, compute resource and state transitions","description":"Groups source-qualified execution context for attempt, dispatch, worker, compute resource and state transitions.","findings":[{"id":"task-attempt-identity-sequence-dispatch-worker-host-container-resource-and-lease","name":"Task attempt identity, sequence, dispatch, worker, host, container, resource and lease","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish task attempt identity, sequence, dispatch, worker, host, container, resource and lease?","id":"task-attempt-identity-sequence-dispatch-worker-host-container-resource-and-lease-q01","kind":"identity"},{"text":"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?","id":"task-attempt-identity-sequence-dispatch-worker-host-container-resource-and-lease-q02","kind":"quality"},{"text":"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?","id":"task-attempt-identity-sequence-dispatch-worker-host-container-resource-and-lease-q03","kind":"relationship"}]},{"id":"requested-queued-started-running-heartbeat-succeeded-failed-cancelled-timed-out-and-unknown","name":"Requested, queued, started, running, heartbeat, succeeded, failed, cancelled, timed out and unknown","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish requested, queued, started, running, heartbeat, succeeded, failed, cancelled, timed out and unknown?","id":"requested-queued-started-running-heartbeat-succeeded-failed-cancelled-timed-out-and-unknown-q01","kind":"state"},{"text":"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?","id":"requested-queued-started-running-heartbeat-succeeded-failed-cancelled-timed-out-and-unknown-q02","kind":"security"},{"text":"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?","id":"requested-queued-started-running-heartbeat-succeeded-failed-cancelled-timed-out-and-unknown-q03","kind":"authority"}]}]}]},{"id":"outputs-lineage-validation-quality-and-observability","name":"Outputs, lineage, validation, quality and observability","description":"Groups governed execution context for outputs, lineage, validation, quality and observability.","layers":[{"id":"declared-materialized-published-outputs-and-lineage","name":"Declared, materialized, published outputs and lineage","description":"Groups source-qualified execution context for declared, materialized, published outputs and lineage.","findings":[{"id":"declared-output-dataset-artifact-schema-partition-destination-and-contract","name":"Declared output, dataset, artifact, schema, partition, destination and contract","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish declared output, dataset, artifact, schema, partition, destination and contract?","id":"declared-output-dataset-artifact-schema-partition-destination-and-contract-q01","kind":"requirement"},{"text":"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?","id":"declared-output-dataset-artifact-schema-partition-destination-and-contract-q02","kind":"retention"},{"text":"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?","id":"declared-output-dataset-artifact-schema-partition-destination-and-contract-q03","kind":"requirement"}]},{"id":"materialized-output-version-digest-size-row-count-publication-visibility-and-derivation","name":"Materialized output, version, digest, size, row count, publication, visibility and derivation","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish materialized output, version, digest, size, row count, publication, visibility and derivation?","id":"materialized-output-version-digest-size-row-count-publication-visibility-and-derivation-q01","kind":"provenance"},{"text":"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?","id":"materialized-output-version-digest-size-row-count-publication-visibility-and-derivation-q02","kind":"interoperability"},{"text":"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?","id":"materialized-output-version-digest-size-row-count-publication-visibility-and-derivation-q03","kind":"constraint"}]}]},{"id":"validation-data-quality-logs-metrics-traces-and-evidence","name":"Validation, data quality, logs, metrics, traces and evidence","description":"Groups source-qualified execution context for validation, data quality, logs, metrics, traces and evidence.","findings":[{"id":"schema-contract-reconciliation-quality-rule-metric-threshold-result-and-waiver","name":"Schema, contract, reconciliation, quality rule, metric, threshold, result and waiver","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish schema, contract, reconciliation, quality rule, metric, threshold, result and waiver?","id":"schema-contract-reconciliation-quality-rule-metric-threshold-result-and-waiver-q01","kind":"validation"},{"text":"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?","id":"schema-contract-reconciliation-quality-rule-metric-threshold-result-and-waiver-q02","kind":"decision"},{"text":"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?","id":"schema-contract-reconciliation-quality-rule-metric-threshold-result-and-waiver-q03","kind":"event"}]},{"id":"log-metric-trace-span-event-evidence-source-scope-sampling-integrity-and-retention","name":"Log, metric, trace, span, event, evidence source, scope, sampling, integrity and retention","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish log, metric, trace, span, event, evidence source, scope, sampling, integrity and retention?","id":"log-metric-trace-span-event-evidence-source-scope-sampling-integrity-and-retention-q01","kind":"evidence"},{"text":"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?","id":"log-metric-trace-span-event-evidence-source-scope-sampling-integrity-and-retention-q02","kind":"state"},{"text":"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?","id":"log-metric-trace-span-event-evidence-source-scope-sampling-integrity-and-retention-q03","kind":"temporal"}]}]}]},{"id":"failure-retry-recovery-backfill-replay-and-outcome","name":"Failure, retry, recovery, backfill, replay and outcome","description":"Groups governed execution context for failure, retry, recovery, backfill, replay and outcome.","layers":[{"id":"error-failure-classification-retry-checkpoint-and-recovery","name":"Error, failure classification, retry, checkpoint and recovery","description":"Groups source-qualified execution context for error, failure classification, retry, checkpoint and recovery.","findings":[{"id":"error-exception-exit-status-failure-domain-root-cause-evidence-and-impact","name":"Error, exception, exit status, failure domain, root cause, evidence and impact","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish error, exception, exit status, failure domain, root cause, evidence and impact?","id":"error-exception-exit-status-failure-domain-root-cause-evidence-and-impact-q01","kind":"exception"},{"text":"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?","id":"error-exception-exit-status-failure-domain-root-cause-evidence-and-impact-q02","kind":"identity"},{"text":"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?","id":"error-exception-exit-status-failure-domain-root-cause-evidence-and-impact-q03","kind":"composition"}]},{"id":"retry-policy-attempt-backoff-checkpoint-resume-idempotency-and-side-effect","name":"Retry policy, attempt, backoff, checkpoint, resume, idempotency and side effect","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish retry policy, attempt, backoff, checkpoint, resume, idempotency and side effect?","id":"retry-policy-attempt-backoff-checkpoint-resume-idempotency-and-side-effect-q01","kind":"lifecycle"},{"text":"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?","id":"retry-policy-attempt-backoff-checkpoint-resume-idempotency-and-side-effect-q02","kind":"classification"},{"text":"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?","id":"retry-policy-attempt-backoff-checkpoint-resume-idempotency-and-side-effect-q03","kind":"evidence"}]}]},{"id":"backfill-replay-rerun-cancellation-compensation-and-outcome","name":"Backfill, replay, rerun, cancellation, compensation and outcome","description":"Groups source-qualified execution context for backfill, replay, rerun, cancellation, compensation and outcome.","findings":[{"id":"backfill-replay-rerun-recovery-predecessor-successor-trigger-and-data-interval","name":"Backfill, replay, rerun, recovery, predecessor, successor, trigger and data interval","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish backfill, replay, rerun, recovery, predecessor, successor, trigger and data interval?","id":"backfill-replay-rerun-recovery-predecessor-successor-trigger-and-data-interval-q01","kind":"provenance"},{"text":"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?","id":"backfill-replay-rerun-recovery-predecessor-successor-trigger-and-data-interval-q02","kind":"relationship"},{"text":"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?","id":"backfill-replay-rerun-recovery-predecessor-successor-trigger-and-data-interval-q03","kind":"ownership"}]},{"id":"cancel-timeout-cleanup-rollback-compensation-partial-result-final-outcome-and-closure","name":"Cancel, timeout, cleanup, rollback, compensation, partial result, final outcome and closure","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish cancel, timeout, cleanup, rollback, compensation, partial result, final outcome and closure?","id":"cancel-timeout-cleanup-rollback-compensation-partial-result-final-outcome-and-closure-q01","kind":"lifecycle"},{"text":"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?","id":"cancel-timeout-cleanup-rollback-compensation-partial-result-final-outcome-and-closure-q02","kind":"authority"},{"text":"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?","id":"cancel-timeout-cleanup-rollback-compensation-partial-result-final-outcome-and-closure-q03","kind":"measurement"}]}]}]},{"id":"governance-access-retention-correction-and-interoperability","name":"Governance, access, retention, correction and interoperability","description":"Groups governed execution context for governance, access, retention, correction and interoperability.","layers":[{"id":"ownership-access-privacy-retention-legal-hold-and-disposition","name":"Ownership, access, privacy, retention, legal hold and disposition","description":"Groups source-qualified execution context for ownership, access, privacy, retention, legal hold and disposition.","findings":[{"id":"owner-steward-operator-subject-purpose-access-redaction-disclosure-and-audit","name":"Owner, steward, operator, subject, purpose, access, redaction, disclosure and audit","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish owner, steward, operator, subject, purpose, access, redaction, disclosure and audit?","id":"owner-steward-operator-subject-purpose-access-redaction-disclosure-and-audit-q01","kind":"privacy"},{"text":"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?","id":"owner-steward-operator-subject-purpose-access-redaction-disclosure-and-audit-q02","kind":"requirement"},{"text":"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?","id":"owner-steward-operator-subject-purpose-access-redaction-disclosure-and-audit-q03","kind":"exception"}]},{"id":"retention-class-legal-hold-tombstone-disposition-cleanup-and-external-record-policy","name":"Retention class, legal hold, tombstone, disposition, cleanup and external record policy","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish retention class, legal hold, tombstone, disposition, cleanup and external record policy?","id":"retention-class-legal-hold-tombstone-disposition-cleanup-and-external-record-policy-q01","kind":"retention"},{"text":"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?","id":"retention-class-legal-hold-tombstone-disposition-cleanup-and-external-record-policy-q02","kind":"constraint"},{"text":"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?","id":"retention-class-legal-hold-tombstone-disposition-cleanup-and-external-record-policy-q03","kind":"provenance"}]}]},{"id":"correction-projection-conformance-loss-and-agent-controls","name":"Correction, projection, conformance, loss and agent controls","description":"Groups source-qualified execution context for correction, projection, conformance, loss and agent controls.","findings":[{"id":"amend-correct-invalidate-supersede-current-head-reason-authority-and-lineage","name":"Amend, correct, invalidate, supersede, current head, reason, authority and lineage","description":"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.","questions":[{"text":"Which stable identities, execution scope, source-qualified values and explicit unknowns establish amend, correct, invalidate, supersede, current head, reason, authority and lineage?","id":"amend-correct-invalidate-supersede-current-head-reason-authority-and-lineage-q01","kind":"provenance"},{"text":"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?","id":"amend-correct-invalidate-supersede-current-head-reason-authority-and-lineage-q02","kind":"event"},{"text":"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?","id":"amend-correct-invalidate-supersede-current-head-reason-authority-and-lineage-q03","kind":"process"}]},{"id":"openlineage-prov-otel-cloudevents-cwl-wes-ogc-airflow-kubernetes-oci-projection-and-loss","name":"OpenLineage, PROV, OTel, CloudEvents, CWL, WES, OGC, Airflow, Kubernetes, OCI projection and loss","description":"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.","questions":[{"text":"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?","id":"openlineage-prov-otel-cloudevents-cwl-wes-ogc-airflow-kubernetes-oci-projection-and-loss-q01","kind":"interoperability"},{"text":"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?","id":"openlineage-prov-otel-cloudevents-cwl-wes-ogc-airflow-kubernetes-oci-projection-and-loss-q02","kind":"temporal"},{"text":"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?","id":"openlineage-prov-otel-cloudevents-cwl-wes-ogc-airflow-kubernetes-oci-projection-and-loss-q03","kind":"validation"}]}]}]}]},"agentConduct":{"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."],"mustNot":["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."],"requiresHuman":["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."]},"ethics":{"considerations":["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."],"affectedParties":["Data subjects in the processed data","Downstream data consumers","Operators accountable for the platform"]},"owners":{"steward":"Dimension owner and data-processing mandate","roles":[{"name":"Data processing owner","responsibilities":["Own execution purpose, service objectives, risk acceptance and accountable outcome interpretation."]},{"name":"Pipeline or workflow steward","responsibilities":["Own reusable definitions, versions, dependencies and approved execution profiles."]},{"name":"Data owner or product steward","responsibilities":["Own input and output assets, contracts, access, publication and retention decisions."]},{"name":"Execution operator or orchestrator","responsibilities":["Own authorized dispatch, state observation, retry, cancellation and recovery within policy."]},{"name":"Platform and compute steward","responsibilities":["Own runtime, capacity, isolation, resource and infrastructure evidence."]},{"name":"Data quality and validation steward","responsibilities":["Own rules, metrics, thresholds, results, waivers and qualified acceptance."]},{"name":"Observability and incident steward","responsibilities":["Own logs, metrics, traces, alerting, incident links, sampling and evidence integrity."]},{"name":"Security, privacy and records steward","responsibilities":["Own identities, secret policy, protected views, disclosure, holds, retention and auditability."]}],"masterSystems":[]},"relations":[{"target":"WM-DAT-005 Data Pipeline","type":"references","note":"Bind the candidate parent pipeline and runnable graph without owning definition lifecycle or cascade behavior."},{"target":"Dataset, data product, schema, contract and source-record models","type":"references","note":"Resolve declared, consumed, generated and published data identities, versions and contracts without copying their lifecycles."},{"target":"Software, package, image, configuration, secret, identity and compute models","type":"references","note":"Resolve immutable execution artifacts, authorization and environment while external systems retain control and sensitive values."},{"target":"Log, metric, trace, quality, incident, provenance, access-audit and records models","type":"references","note":"Resolve evidence and governance records without absorbing observability, incident or retention execution."},{"target":"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","type":"aligned","note":"Project version-pinned lineage, telemetry, event, workflow, execution-service, orchestration, container and API views with scope and information-loss declarations."},{"target":"WM-DAT-005 Data Pipeline","type":"neighbor","note":"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."},{"target":"Dataset, data product, schema and data contract models","type":"neighbor","note":"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."},{"target":"Software, package, image, configuration, secret and compute models","type":"neighbor","note":"External masters own artifacts, sensitive values and infrastructure lifecycle. The run binds immutable revisions, digests, entrypoints, secret references, resource observations and environment snapshots."},{"target":"Logs, metrics, traces, quality results and incidents","type":"neighbor","note":"Observability and quality systems own evidence content and lifecycle. The run records typed links, scope, sampling, times, integrity and bounded interpretations."},{"target":"Run, task, stage, attempt and retry","type":"neighbor","note":"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."},{"target":"OpenLineage, PROV, OTel, CloudEvents, CWL, WES, OGC Processes, Airflow, Kubernetes and OCI","type":"neighbor","note":"These are versioned lineage, telemetry, event, workflow, API, orchestrator and runtime projections with different scopes. No mapping is assumed lossless or universally applicable."},{"target":"WM-DAT-005","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier for each run, task, attempt, binding, materialization, validation or execution event, qualified by owning execution system and record kind.","Governed globally resolvable processing-run IRI.","Dimension UUID or ULID when neither preceding identifier exists."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A run names its pipeline or job definition version, a trigger, a data interval, start and end times and a state.","Often confused with the pipeline definition, a schedule entry, a log stream or a dataset version."]},"capabilities":{"applicability":"required","items":["Register processing run: Governed operation to register processing run without autonomous execution, production mutation, secret access or mutation of external masters.","Resolve definition, inputs and environment: Governed operation to resolve definition, inputs and environment without autonomous execution, production mutation, secret access or mutation of external masters.","Authorize and dispatch: Governed operation to authorize and dispatch without autonomous execution, production mutation, secret access or mutation of external masters.","Record task and attempt events: Governed operation to record task and attempt events without autonomous execution, production mutation, secret access or mutation of external masters.","Record input consumption and output materialization: Governed operation to record input consumption and output materialization without autonomous execution, production mutation, secret access or mutation of external masters.","Record validation, quality and observability: Governed operation to record validation, quality and observability without autonomous execution, production mutation, secret access or mutation of external masters.","Record failure and retry: Governed operation to record failure and retry without autonomous execution, production mutation, secret access or mutation of external masters.","Cancel, recover, resume or compensate: Governed operation to cancel, recover, resume or compensate without autonomous execution, production mutation, secret access or mutation of external masters.","Backfill, replay, rerun and close: Governed operation to backfill, replay, rerun and close without autonomous execution, production mutation, secret access or mutation of external masters.","Correct, project, retain, disclose and audit: Governed operation to correct, project, retain, disclose and audit without autonomous execution, production mutation, secret access or mutation of external masters."]},"hazards":{"applicability":"required","items":["Duplicate outputs from a non-idempotent retry.","Partial outputs published as complete.","Wrong data interval processed after a backfill.","Secret leakage through logs."]},"interfaces":{"applicability":"required","items":["OpenLineage run and job events.","W3C PROV-O and PROV-DM.","OpenTelemetry traces, metrics and logs.","CNCF CloudEvents.","Common Workflow Language (CWL) and GA4GH Workflow Execution Service (WES).","OGC API - Processes - Part 1: Core.","OCI image specification for execution environments."]},"context":{"applicability":"required","items":["Execution authority, data protection, cross-border processing, audit, retention and incident response depend on jurisdiction, organization and data classification.","GDPR is a European Union legal profile, and NIST controls require deployment-specific tailoring.","Orchestrator states, retry behavior, task identity, container semantics, quality rules, telemetry schemas and API behavior require versioned profiles."]}},"sources":[{"title":"PROV-DM: The PROV Data Model","url":"https://www.w3.org/TR/prov-dm/","note":"World Wide Web Consortium"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"Data Catalog Vocabulary Version 3","url":"https://www.w3.org/TR/vocab-dcat-3/","note":"World Wide Web Consortium"},{"title":"Data on the Web Best Practices: Data Quality Vocabulary","url":"https://www.w3.org/TR/vocab-dqv/","note":"World Wide Web Consortium"},{"title":"OpenLineage Object Model","url":"https://openlineage.io/docs/spec/object-model/","note":"OpenLineage Project"},{"title":"OpenTelemetry Specification","url":"https://opentelemetry.io/docs/specs/otel/","note":"Cloud Native Computing Foundation OpenTelemetry Project"},{"title":"CloudEvents Specification","url":"https://github.com/cloudevents/spec/tree/ce@v1.0.2","note":"Cloud Native Computing Foundation"},{"title":"Common Workflow Language Workflow Description","url":"https://www.commonwl.org/v1.2/Workflow.html","note":"Common Workflow Language Project"},{"title":"Workflow Execution Service API","url":"https://ga4gh.github.io/workflow-execution-service-schemas/","note":"Global Alliance for Genomics and Health"},{"title":"OGC API - Processes - Part 1: Core","url":"https://docs.ogc.org/is/18-062r2/18-062r2.html","note":"Open Geospatial Consortium"},{"title":"Tasks","url":"https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/tasks.html","note":"Apache Software Foundation"},{"title":"Jobs","url":"https://kubernetes.io/docs/concepts/workloads/controllers/job/","note":"Cloud Native Computing Foundation Kubernetes Project"},{"title":"OCI Image Format Specification","url":"https://github.com/opencontainers/image-spec/tree/v1.1.1","note":"Open Container Initiative"},{"title":"Security and Privacy Controls for Information Systems and Organizations","url":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","note":"National Institute of Standards and Technology"},{"title":"Regulation (EU) 2016/679 General Data Protection Regulation","url":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","note":"European Union"},{"title":"Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/info/rfc3339/","note":"Internet Engineering Task Force"},{"title":"OpenAPI Specification 3.1.1","url":"https://spec.openapis.org/oas/v3.1.1.html","note":"OpenAPI Initiative"}],"openQuestions":["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."],"resources":{"spec":"/models/wm-act-053-data-processing-job-pipeline-run/spec.yaml","agents":"/models/wm-act-053-data-processing-job-pipeline-run/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/publications/wm-act-053-data-processing-job-pipeline-run"},"provenance":{"origin":"world-models research","builtFrom":["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"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-06T10:56:43Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}