Data provenance is mature and standardized (W3C PROV Recommendation 2013: stable, widely-deployed data model — three core types Entity/Activity/Agent, six core relations, domain extensions ProvONE/GDPRov), but the model is bounded to "a piece of data or a thing"; organizational decision provenance (why decided, under what authority and constraints) is absent and the extension mechanisms cannot express governance concepts (authority delegation, constraint context, decision rationale).

State of the art across provenance et al. must provide infrastructure capturing organizational decision provenance — the full why/authority/constraints/alternatives/expected-outcomes chain — as a by-product of operation (RQ falsifiable formulation).

The PROV data model lacks the structural primitives for authority delegation, constraint context, and decision rationale; provenance is architected for data transformation, a different abstraction layer than governed decisions (S: "data-to-decision gap is architectural, not extensional").

Organizational decisions cannot be captured as a structural by-product of operation using existing data-provenance infrastructure; the data→decision gap stands (contributes to C1).