Rek is Wild HQ’s founder and current team lead. That responsibility does not turn every preference into policy, replace a required community vote, or make every task wait for Rek.
Roles describe work and access:
| Role | Responsibility | Authority boundary |
|---|---|---|
| Task owner | Carries the next action and keeps the Wildbase Work record honest. | May choose implementation details inside the accepted scope; does not assign other volunteers. |
| Reviewer | Checks behaviour, risk, clarity, and evidence. | Approval counts only when the reviewer has repository review permission and enough context; authors do not approve their own work. |
| Maintainer | Keeps a repository or service operable and can merge or manage its protected settings. | Access is limited to the maintained system and remains subject to review and governance rules. |
| Release owner | Carries one named release or rollback. | May act only in the named environment and release window recorded on the task. |
| Incident lead | Keeps an active incident’s next decision, evidence, and communication clear. | Coordinates the response; does not gain permanent rank or unrelated access. |
| Moderator | Applies product moderation powers granted by the server or pack. | Client controls are affordances, not authority; the server must enforce every action. |
| Team lead | Keeps direction, access gaps, and unresolved responsibility visible. | Does not receive extra ballots or override the handbook by title alone. |
One person may carry several roles on a small task, but separation still matters where it provides a real safeguard. A code author cannot supply the required independent PR approval. A person targeted by a moderation action cannot be its only reviewer when another authorised moderator is available.
Name the role on the work
A role begins when it is accepted and recorded, not when somebody is mentioned in Discord. For a normal task, naming the task owner is enough. For production, migration, moderation, spending, or incident work, also name the person carrying that authority and the environment or budget it covers.
If no authorised person is named, prepare the change, evidence, or runbook and mark the protected action as blocked. Do not infer authority from title, online presence, old access, or who answered fastest.
Wild HQ does not currently publish a complete repository-and-service owner directory. The onboarding or work task must therefore name its current reviewer, access granter, release owner, or operator when one is required. Finding an old username in Git history is not a substitute.
Hand roles back
When work pauses or finishes, update the task, transfer any required context, and remove access that no longer has a purpose. Leaving a role is not leaving the community, and keeping unnecessary access is not continuity.