OpenLineage

Generated Evaluation Status

This section is generated from the framework manifest and compatibility report. Do not edit it manually.

• Framework ID: openlineage
• Manifest: docs/external-frameworks/openlineage.json
• Compatibility report: ./reports/openlineage.compatibility.json
• Evidence class: SOURCE_REVIEWED
• Independently reproducible: False
• Comparative-testing claim allowed: False
• Missing reproducibility gates: shared_test_vector, raw_output, timestamp, runtime_configuration, source_version_or_hash, replay_commands, declared_expected_outcome, independent_reproduction
• Evaluation result: COMPATIBILITY_EVIDENCE_ONLY
• Cycle status: FIRST_FRAMEWORK_CYCLE_COMPLETE
• Execution authority claim: False
• Next bounded action: Add executable observations, raw outputs, pinned versions, replay commands, and independent reproduction before making comparative-testing claims.
• Posting source: generated compatibility report
• Generated status is descriptive compatibility evidence only.

Generated Authored Analysis Boundary

This section is generated. Do not edit it manually.

• Framework ID: openlineage
• Framework name: OpenLineage
• Generated sections above this boundary may be rebuilt from registry, manifest, compatibility-report, and result artifacts.
• Authored analysis below this boundary may contain interpretation, notes, and framework-specific discussion.
• Generators must preserve authored analysis unless a future validator explicitly declares a migration path.
• Boundary rule: generated material is descriptive compatibility evidence only and does not create certification, endorsement, adoption, proof, or operational permission.

Generated Transition Mapping

This section is generated from the framework manifest. Do not edit it manually.

Field	Generated Value
framework_identity	OpenLineage
source_reference	https://openlineage.io/
source_version	official project source recorded
allowed_use_boundary	lineage evidence only
claims	dataset, job, and run lineage metadata
non_claims	no truth, legitimacy, or execution authority
input_artifact_type	lineage event
output_artifact_type	lineage reconstruction evidence
actor_or_authority_model	producer identity evidence only
evidence_model	official source plus bounded crosswalk
policy_or_rule_model	lineage event schema
delegation_model	not established
decision_or_result_model	lineage evidence
execution_authority_claim	false
receipt_or_trace_model	lineage event and manifest references
reconstruction_model	events link datasets, jobs, and runs
SPE_overlap	lineage may inform evidence review
StegVerse_ecosystem_overlap	reconstruction and freshness boundary
fail_closed_conditions	missing source, event context, mapping, or authority overclaim

Generated mapping is compatibility evidence only.

Generated Framework Metadata

This section is generated from the external-framework registry. Do not edit it manually.

• Framework ID: openlineage
• Name: OpenLineage
• Registry status: SOURCED-CROSSWALK-PROVISIONAL
• Testbench state: SOURCE_RECORDED_CROSSWALK_PROVISIONAL
• Manifest path: docs/external-frameworks/openlineage.json
• Source reference: https://openlineage.io/
• Metadata boundary: generated metadata is descriptive only; it does not create certification, endorsement, formalism adoption, admissibility proof, or execution authority.

Status

Relationship type: external framework crosswalk
Evidence class: SOURCE_REVIEWED
Page completeness: COMPLETE_WITH_EXTERNAL_GATES
Runtime observation: none attached
Independent reproduction: false
Comparative testing claim allowed: false
Execution authority claim allowed: false
Maintenance owner: admissibility-wiki External Frameworks audit

Official Source

• Project source: https://openlineage.io/
• Source posture: official project documentation captured; no producer, transport, event stream, or consumer fixture is attached.

Framework-Native Scope

OpenLineage is an open standard for collecting metadata about datasets, jobs, and runs across data pipelines. Its event model can describe run state, job identity, dataset inputs and outputs, and extensible facets emitted by participating systems.

Evidence Provenance

Evidence class	Current evidence	Status	Missing fields
Official framework source	Project documentation	present	pinned specification or source snapshot hash
Implementation source	No producer or consumer selected	missing	release, configuration, commit
Observed behavior	No lineage event capture	missing	event payloads, transport, timestamps, consumer output
Reproduced behavior	No independent replay	missing	event stream, commands, environment, second result
StegVerse analysis	Bounded crosswalk	present	common event fixture

Relationship to Admissibility

OpenLineage asks: What datasets, jobs, and runs were connected and reported across the pipeline?
StegVerse Admissibility asks: Is the reconstructed evidence sufficient and does the current actor hold authority to bind this consequence?

Lineage events can strengthen reconstruction and freshness review by linking data, jobs, and run events. They do not independently establish truth, legitimacy, current authority, or admissibility.

Execution Authority Boundary

lineage visibility != governance authority
reported origin != verified truth
run relationship != current delegation
event completeness != permission to bind consequence

Observation Boundary

Pinned producer: none
Pinned consumer: none
Event schema/version: none
Captured event stream: none
Raw consumer output: none
Timestamp and transport configuration: none
Independent replay: none

No lineage-capture, reconstruction, or interoperability result is claimed.

StegVerse Analysis

Criterion	Current result
Identity	Job, run, and dataset identifiers may be represented, but actor identity may remain external.
Authority	Emission or consumption of lineage events does not create execution authority.
Policy	Event acceptance, retention, trust, and freshness policy must be explicit.
Delegation	Lineage relationships do not prove delegated authority.
Evidence	Events may strengthen reconstruction if complete, authentic, ordered, and retained.
Replayability	Requires pinned schema, event stream, producer/consumer versions, and transport configuration.
Reconstructability	Depends on event completeness, ordering, identifiers, custody, and facet interpretation.
Commit-time validity	Must be evaluated independently from lineage state.
Failure behavior	Missing, duplicate, reordered, stale, or unverifiable events must not be treated as complete truth.

Commit-Time Interoperability Contract

transition_id
run_id
job_namespace
job_name
event_type
event_time
input_dataset_ids
output_dataset_ids
facet_digests
producer_identity
schema_version
event_digest
custody_reference
freshness_state
policy_reference
delegation_reference
requested_action
target_system

Failure Classes

Failure class	Applies	Notes
Semantic equivalence divergence	yes	Recorded lineage may be mistaken for causal proof.
Stale evidence	yes	Events can lag behind current pipeline state.
Replay divergence	yes	Different ordering, schema handling, or facets may alter reconstruction.
Recoverability loss	yes	Missing event segments can make the chain incomplete.
Source-claim mismatch	yes	Producer-reported events may exceed what was independently verified.
Evidence-class confusion	yes	Source review must not be described as observed lineage behavior.

Machine-Readable Companions

• Manifest: docs/external-frameworks/openlineage.json
• Compatibility report: docs/external-frameworks/reports/openlineage.compatibility.json
• Registry: docs/external-frameworks/index.json
• Canonical inventory: static/external-frameworks/canonical-union-inventory.v1.json

Validation Completion Criteria

pin one producer, transport, and consumer
publish a bounded lineage event fixture
capture raw emitted and consumed events with timestamps
publish ordering, custody, expected result, and replay commands
complete an independent replay
route reconstructed lineage evidence into a Commitment Candidate

Non-Claims

OpenLineage is not a StegVerse canonical formalism. Lineage visibility and recorded origin are not truth, legitimacy, current authority, transition admissibility, certification, or general compatibility.

Challenge Path

A challenge must identify the run, job, dataset, event or facet, disputed relationship, supporting evidence, and requested correction. Reported lineage receives only the standing supported by reconstructable custody and provenance.

Next Safe Build Target

Publish one pinned producer-to-consumer event fixture with raw events, ordering and custody evidence, immutable hashes, replay instructions, and an independent replay.

This page reflects a bounded admissibility packet. Publication does not create standing.