ADR-003: Adoption of GitHub Flow for Collaboration

Context

The repository serves as a centralized documentation hub for both human team members and AI agents. We need a workflow that ensures the stability of the main branch while allowing parallel contributions without complex merge conflicts.

Decision

We adopt the GitHub Flow as the standard collaboration mechanism:

1. Everything in the main branch is deployable/stable.
2. All new work happens in Feature Branches (feat/, fix/, docs/).
3. Feedback and reviews occur via Pull Requests.
4. Merges to main are performed via Squash and Merge.

Consequences

• Positive: Clean commit history, enforced review cycles, and risk mitigation for AI-generated changes.
• Negative: Adds overhead (branch management + PRs) compared to direct pushes, but this is necessary for governance.