docs(governance): record DIRTY-drift lesson + mark scratchnode/002 shipping#501
Merged
Conversation
…ipping Operational lesson from today's loop run: reviewable PRs left open against hot files (home-v5.html, events.ts, honesty spec) go DIRTY as the daily loop squash-merges past them. #469 had to be rebuilt fresh as #500. Rule: land or rebase hot-file PRs within one working day; serialize >=2 PRs on the same hot file (strict:true makes the 'behind main' ping-pong explicit). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
|
Demo: walkthrough of the surfaces this PR changed is available as a workflow artifact ( |
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.
What
Records an operational lesson in
goals/GOVERNANCE.md(new append-only Operational lessons section) from today's loop run, and updatesgoals/scratchnode/002status to reflect it shipped via #500.The lesson
While the daily small-loop shipped ~10 changes to
public/proto/home-v5.html, two reviewable PRs left open against it — #469 (host public-write) and the type-scale work (#499) — both went DIRTY/CONFLICTING. Squash-merges rewrote their base; each intervening ship widened the gap. #469 had to be rebuilt fresh on current main as #500.Rule codified: land or rebase any PR touching a hot file (
home-v5.html,convex/events.ts, honesty spec, ScratchNode e2e specs) within one working day; if human-gated, rebase onto main daily + re-run the oracle until it lands, or close + re-cut from main. Serialize ≥2 PRs on the same hot file —strict: truemakes the 'behind main' ping-pong explicit (both #499 and #500 went BEHIND the instant #496 merged).Docs-only. LOW risk.
🤖 Generated with Claude Code