docs: retire strict_provenance and drop provenance terminology (re-merge of #199)#201
Merged
Merged
Conversation
Re-applies the changes from #199, which was marked merged but never landed on main: #198 and #199 were merged seconds apart, and #199's squash was computed against a stale base (main before #198 propagated), so GitHub could not advance main to it and the retire-provenance changes were silently dropped. This branch re-applies exactly #199's 16-file change set on top of the current main (which now includes #198): deletes provenance.md, adds trace.md, and completes the terminology sweep.
MilagrosMarin
approved these changes
Jul 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Corrective re-merge of #199, which shows as merged but never landed on
main.What happened
#198 and #199 were merged within seconds of each other. #199 (stacked on #198) was squash-merged against a stale base — a snapshot of
mainfrom before #198 had propagated — so its squash commit (652f5cc2) parented a pre-#198 commit. GitHub marked the PR merged but could not fast-forwardmain(already advanced to #198) to it, so the ref never moved. Net result:mainstill hadprovenance.md, notrace.md, and none of the terminology sweep — a merge-race artifact, not a content problem.This PR
Re-applies exactly #199's 16-file change set on top of the current
main(which now includes #198): deletesprovenance.md, addstrace.md, sweeps the terminology across the conceptual pages, and wires the redirect. #198's files (autopopulate.md,computation-model.md) are intentionally not touched — they are already onmain.Content is identical to the approved #199 (reviewed and approved by @MilagrosMarin). The PR-body overclaim about
dj-platform.svgfrom #199 is carried over as corrected: the sole remainingprovenanceoccurrence undersrc/is the platform-architecture label inimages/dj-platform.svg, intentionally kept (it describes the DataJoint platform, which builds provenance capabilities; the framework docs describe the open-source core’s relational workflow model, where "lineage" is apt).Diff: 16 files, +341 / −496 — matches #199 exactly.