Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Use two-tip diffs and audit fleet instances separately
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
When main and staging contain independent promotions or cherry-picks, use the two-tip diff for what is actually new; a three-dot merge-base diff can reclassify already promoted changes. Use cherry equivalence only as supporting history. Audit deployment variables per fleet instance, not only the template, because sync may retain instance-only flags and create an implicit one-instance canary. Make that asymmetry an explicit release decision and validate its dependency path.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review