Join KineGrant's first six permissionless working groups

[zoahdev]

KineGrant is opening its first six permissionless working groups alongside RFC-0005. You do not need an invitation, employment relationship, token, payment, or prior KineGrant experience.

Pick one bounded first contribution

• Protocol & interoperability — review RFC-0005 or reproduce one RFC test.
• Implementations & hardware — gate one ROS 2, ESP32, OPC UA, or Matter action; valid-once must pass and replay/expiry/scope must fail.
• Security — attempt five permission-boundary attacks and disclose responsibly.
• Documentation & translation — reproduce the quickstart on a clean machine and remove one blocker.
• Deployments & user research — interview one robot operator about action authorization and publish an anonymized problem record with consent.
• Governance & community operations — submit a concrete membership, election, recall, quorum, or anti-Sybil test case.

How to join now

Comment with:

1. the working group;
2. the bounded result you will attempt;
3. your expected two-week window;
4. any equipment, access, or reviewer you need; and
5. conflicts of interest (none is fine).

Two participants may declare a working group active by agreeing on a public work location, initial deliverable, maintainers, and sunset/review date. No founder permission is required. Outputs still follow normal security review and RFC rules.

Contributor protections

• Contributions are public and credited under Apache-2.0.
• Credentials are non-financial and non-transferable.
• Volunteer work does not imply future employment or payment.
• Do not test hazardous machinery without operator authorization and safety controls.
• Sensitive vulnerabilities go through private GitHub Security Advisories.

English and Chinese onboarding documents are included in PR #298. Until that PR is accepted, this issue is a public invitation to collaborate, not a claim that the proposed governance rules are already in force.