docs: point this fork at the Launchpad handbook - #61
Merged
Merged
Conversation
Adds LAUNCHPAD.md, a fork-specific orientation file naming where our knowledge about deploying and operating this Buzz environment lives: launchpad-26/handbook, built through issues #4 and #6-#11. It is a NEW file rather than a section in AGENTS.md deliberately. AGENTS.md is maintained by block/buzz and changed as recently as upstream block#5110, so editing it would create a merge conflict on every sync from now on. A file upstream will never touch costs nothing to carry. Records the two things a future reader would otherwise have to rediscover: Why the handbook is a separate repository and stays one. It synthesises five repositories and links each claim back to a pinned commit, so it does not belong inside any one of them. Vendoring it here as a submodule or subtree would mirror content instead of synthesising it - the exact fragmentation the handbook exists to solve - and would break provenance, which assumes the repositories move independently. How the two are connected: through pinned commits and a staleness job at the data layer, through org project #20 at the tracking layer, and through cross-repo closing keywords for issues. Not at the code layer. Also states that new handbook issues belong in the handbook repository, which is private, because this repository is public and content discussion draws on private sources. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Serina Mcfall <serina.mcfall@gmail.com>
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.
Adds
LAUNCHPAD.md— a fork-specific orientation file naming where our knowledge about deploying and operating this Buzz environment lives:launchpad-26/handbook, built through #4 and #6–#11.Why a new file rather than a section in
AGENTS.mdCLAUDE.mdis a symlink toAGENTS.md, which is maintained byblock/buzzand changed as recently as upstream PR block#5110. Editing it would create a merge conflict on every sync from now on. A file upstream will never touch costs nothing to carry.What it records
Two things a future reader would otherwise have to rediscover:
Why the handbook is a separate repository and stays one. It synthesises five repositories and links each claim back to a pinned commit, so it does not belong inside any one of them. Vendoring it here as a submodule or subtree would mirror content instead of synthesising it — the exact fragmentation the handbook exists to solve — and would break provenance, which assumes the repositories move independently. That temptation will come up again; the file says no and says why.
How the two repos are connected:
buzz)Closes launchpad-26/buzz#<n>One convention it sets
New handbook issues are filed in
launchpad-26/handbook, which is private. This repository is public, and once content work starts, issue discussion will draw on private sources.Not included
No credentials, hostnames, keys or rosters — scanned before commit. Nothing here is not already public in #6–#11.