From f4863aa7f59283681b945216a8056e723a89a5b0 Mon Sep 17 00:00:00 2001 From: ttngu207 Date: Thu, 17 Sep 2026 15:32:13 -0500 Subject: [PATCH] docs: scope the provenance-compliance claim to platform-managed computation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit "Compliance with industry provenance standards is ensured by the DataJoint Platform" stood unqualified. Ensured overstates it: what an exported account can carry depends on what was captured, and three cases carry less. Data populated outside the platform runs against library defaults, where JobsSettings ships keep_completed, add_job_metadata and version_method all off, so there is no job metadata and no commit identity. Tables declared before add_job_metadata was enabled carry none either, since enabling it does not backfill. And manually entered rows record no attribution at all — who entered a datum and when is not captured today. Rewritten to say the Platform supports compliance for the computation it manages, and that compliance is a property of the deployment rather than of the format. The surrounding claims are unchanged: lineage lives in DataJoint's schema, maps to OpenLineage or W3C PROV, and integrates in both directions when explicitly configured. Raised in review of platform-roadmap#228, whose readiness section documents the three cases. --- src/explanation/comparison-to-provenance-systems.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/src/explanation/comparison-to-provenance-systems.md b/src/explanation/comparison-to-provenance-systems.md index 74b3c13f..7d50fe72 100644 --- a/src/explanation/comparison-to-provenance-systems.md +++ b/src/explanation/comparison-to-provenance-systems.md @@ -74,8 +74,14 @@ This integration is opt-in and configured explicitly; it is not automatic. Interchange in either direction uses the standards the surrounding ecosystem speaks. DataJoint's lineage is expressed in its own schema; where it is exchanged with external governance, audit, and cataloging systems, it maps to industry -lineage and provenance standards such as OpenLineage or W3C PROV. Compliance with -industry provenance standards is ensured by the DataJoint Platform. +lineage and provenance standards such as OpenLineage or W3C PROV. + +The DataJoint Platform supports compliance with industry provenance standards for +the computation it manages. What an exported account can carry depends on what was +captured: platform-managed computation records the code version, the worker, and +timings for every computed row, while data entered or populated outside the +platform carries less. Compliance is a property of the deployment, not of the +format. ## See also