Contribute

You do not need to understand the whole repository before contributing. You do need a task whose boundary matches what you can safely decide.

The repository CONTRIBUTING.md contains the exact human workflow. This section explains how the pieces fit together.

Starter work has a fixed result and little protocol judgment. Contributor-ready work has decided semantics but may still require substantial implementation. Maintainer-guided work still contains an admission, ownership, compatibility, or architecture decision.

Effort does not answer readiness. A small task can be blocked on design; a large slice can be ready to implement.

Before claiming anything, read the Issue, recent comments, assignee, linked pull requests, and Project state when it becomes available. If the outcome, exclusions, implementation authorization, or validation boundary is missing, ask for the task to be shaped first.

• Collaboration model explains what Issues, labels, Projects, milestones, reviews, and Actions each own.
• Deliver a change covers development, acceptance, regression, deployment, and release.
• Contributor Agents explains the composable skill system, capability assessment, and autonomous task selection.
• Agent skill catalog lists every lazy state transition and its role.
• Agent automation separates deployed shadow tasks, manual protocols, and candidate recurring work.
• Prototype authoring covers governed component work in detail.

Questions and early ideas belong in GitHub Discussions. Bounded work belongs in GitHub Issues. Discord is useful for quick coordination, but implementation-changing decisions should be recorded back in the repository.