Keep community guidance local only when repository-specific #229

Context and request

Repository contributors should use shared organization community defaults without carrying redundant local copies. The user clarified that ordinary repositories keep local files only when repository-specific content is needed. Canonical guidance currently discourages copied defaults while unconditionally requiring a local contribution guide.

Acceptance criteria

• Ordinary repositories inherit shared community defaults and keep local community/contribution files only for genuine repository-specific content or a documented exception.
• Every initiative's public .github repository must contain .github/CONTRIBUTING.md, even if blank. These central repositories remain the source home for their shared defaults; validate source-file presence without requiring copies in each consumer.
• Genuinely repository-specific build/test/contribution guidance is retained and linked to the shared policy rather than removed or copied.
• Organization/repository/README/readiness guidance, matrices, links, and relevant skill/instruction routes are consistent with this scope.
• No fleet file deletion, copy rollout, unrelated legal/ownership configuration change, or release/governance mutation is performed.

Technical decisions

Deliver this as a separate focused standards PR, not a community-file cleanup or an expansion of the Epic/PBI authoring PR. Reconcile the unconditional contribution-guide rule in Repository Standard with Organization Standard's fallback/local-exception boundary. Keep MSXOrg/docs' genuine repository-specific contribution commands. Do not remove repository-local legal terms, CODEOWNERS, agent routes or other non-community defaults merely to deduplicate files.

Implementation plan

• Identify conflicting local-file requirements and existing valid inheritance/local-specific examples before editing.
• Verify expected source-versus-consumer behavior with representative inherited and repository-specific guidance cases.
• Align the canonical rule, required-file matrix and dependent links/instructions without changing unrelated repository baselines.
• Require the initiative contribution source even when blank while preserving conditional consumer-local guides.
• Run existing documentation validation and full review, recording the preserved local-specific behavior and lack of fleet mutation.