Consolidate to one repository, and rename the masthead art - #4
Merged
Conversation
Development happened in a private repository; this one was created from an orphan-root commit carrying a curated subset, with an exclude list naming what stayed behind and a guard script to catch anything merged here first from being silently reverted by the next release. That arrangement is ending: this repository becomes the only one. Everything worth keeping therefore has to arrive before the private one goes away. Seventeen paths existed nowhere else; these eleven are the ones with lasting value: - the five diagram pairs (apply semantics, destructive utilities, mode lifecycle, pipeline, pipeline branching) - scripts/gen-olaf-diagrams.py, which generates them They were withheld because no published document referenced them — never because a check objected. The exclude list said so in as many words: "None of these are excluded for safety — the release scanner reports no finding against any of them." The generator does not produce the four diagram pairs already published here, so nothing shipped was ever at risk of becoming unregenerable; these five simply had no copy outside one laptop. The exclude list and the mirror-back guard are deliberately NOT brought over. Both exist to manage two repositories that cannot merge into each other. With one repository there is no subtraction to describe and no drift to guard against, and carrying them would leave instructions for a process that no longer runs. Masthead art renamed olaf-lockup-* to olaf-banner-*. The bytes were replaced in the previous change but the filenames were not, and GitHub serves README images through a cache keyed on URL — so every viewer kept getting the previous image from an unchanged address. A new name is the only thing that reliably invalidates that. It also describes the file better: this is a banner. README, brand guidelines, the asset README and PROVENANCE all follow the rename, and every recorded hash was re-verified against the file on disk.
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
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.
Why
Development happened in a private repository. This one was created from an orphan-root commit carrying a curated subset, with
public-tree-exclude.txtnaming what stayed behind andsync-from-public.pyguarding against the next release silently reverting anything merged here first.That arrangement is ending — this repository becomes the only one. Everything worth keeping has to arrive before the private one is deleted.
What comes over
Seventeen paths existed nowhere else. These eleven have lasting value:
scripts/gen-olaf-diagrams.py— the generator that produces themThey were withheld because no published document referenced them, never because a check objected. The exclude list said so in as many words:
Verified before bringing them: the generator does not produce the four diagram pairs already published here, so nothing shipped was ever at risk of becoming unregenerable. These five simply had no copy outside one laptop.
What deliberately does not come over
public-tree-exclude.txtandsync-from-public.py. Both exist to manage two repositories that cannot merge into each other — the orphan root meansmainand this repo share no ancestry. With one repository there is no subtraction to describe and no drift to guard against, and carrying them would leave instructions for a process that no longer runs.Masthead rename
olaf-lockup-*→olaf-banner-*.The bytes were replaced in #3 but the filenames were not, and GitHub serves README images through a cache keyed on URL — so viewers kept getting the previous image from an unchanged address. A new name is the only thing that reliably invalidates it. It also describes the file better: this is a banner.
README.md,docs/brand-guidelines.md,assets/brand/README.mdandPROVENANCE.mdall follow the rename, and every recorded hash was re-verified against the file on disk.Verification
scripts/lint.shpytestcheck_public_release.py tree .olaf-lockupremainingThe pinned Gitleaks scan needs a container runtime and runs in CI.