Vendor the source document into the repo - #2
Merged
Conversation
The README, docs/policy-mapping.md, and CLAUDE.md all cite _Moving Team Communication to Slack_ by section number, but the document itself lived in a personal Obsidian vault. Every § in this repo pointed at something a clone could not open. Add it under docs/ and link it from the three places that name it. The body is verbatim. The trailing note to the author is not part of the article, so it is dropped, but both of its points are substantive and are kept in a provenance header: the nonprofit-pricing/educator-status tension in §5 is unresolved, and clause 1 quoted in §8 is typical language for that policy family rather than confirmed Melrose text. The header also points at policy-mapping.md, which already records where later reading of the FIRST rules corrected §3 and §7. Nothing else in the body is edited. Code cites these sections by number, so the document is a fixed reference, not a page to keep current. Co-Authored-By: Claude Opus 5 <noreply@anthropic.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
1 participant
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.
The README,
docs/policy-mapping.md, andCLAUDE.mdall cite Moving Team Communication to Slack by section number, but the document itself lived in a personal Obsidian vault. Every§in this repo pointed at something a clone could not open.Adds it as
docs/moving-team-communication-to-slack.mdand links it from the three places that name it.CLAUDE.mdpreviously pointed atobsidian/Areas/FRC/...; that path is now the in-repo copy.Two judgment calls
The trailing note to the author is dropped. It is an editorial exchange, not article text. Both of its points are substantive, so they are kept in a provenance header instead:
The body is otherwise verbatim. Code cites these sections by number, so the document is a fixed reference rather than a page to keep current. Where later reading of the FIRST rules corrected §3 and §7 — "Lead Coach" as an access role, Mentor Ready being non-blocking —
policy-mapping.mdalready records it, and the header points there rather than editing the source.Prettier reflowed the §5 cost table. Docs only; no code changes.
🤖 Generated with Claude Code