What they bring
Engineering capacity, repositories or work samples, technical methods, availability, and defined delivery boundaries.
PARTICIPANT 04 / 24
Developers and engineering contributors
Developers contribute scoped technical work whose requirements, review criteria, delivery evidence, and acceptance decision remain explicit.
ServiceStandard review
Typical participants
Smart-contract engineers, frontend and backend developers, AI and data engineers, and open-source contributors.
Smart contract · frontend · backend · open source
WCN role map
- Participant type
- developer
- Primary role
- Service
- Supporting roles
- Project
- Review path
- Standard review
- Phase 1 path
- Eligible to apply for review.
PARTICIPATION FIT
What this participant brings—and what they may seek.
What they may seek
Well-scoped work, dependency clarity, reviewable acceptance criteria, specialist collaboration, and attributable delivery history.
AI + HUMAN CONTROL
AI may prepare. People retain decision authority.
Service Scope Copilot
The workbench describes a bounded assistance pattern for intake, structure, checks, and drafts. It is not proof that a public AI product or integration is live.
Mandatory Human Gate
Architecture conclusions, security impact, production access, and final delivery acceptance.
PUBLIC BOUNDARY
Participation is reviewed, not automatic.
A code contribution is not accepted, deployed, or production-authorized until its own review is complete.
- Eligible to apply for review.
- Architecture conclusions, security impact, production access, and final delivery acceptance.
- These tags name evidence categories for future reviewed work. They do not create public Proof, acceptance, settlement, certification, or endorsement.
Evidence vocabulary: service_proof · technical_proof
Service