Contribute

Contribution to fxyz is structured through the membership system and the holacracy-based organizational model. Rather than an open-source contribution flow, fxyz operates as an invitation-based network where members participate through roles, circles, and governance.

Membership Tiers

Every contributor begins as an Observer and advances through the membership tiers based on their participation, contributions, and standing within the network. Each tier unlocks deeper access to circles, governance, and operational responsibility.

For details on the membership model and how advancement works, see the Membership guide.

Types of Contribution

Development

Members with technical roles contribute to the platform through their assigned circles. The technical stack includes:

• Frontend: React, Next.js, TypeScript
• Backend: Node.js, GraphQL
• Blockchain: Solana (Token-2022)
• Database: Neo4j Graph Database

Knowledge and Research

The network maintains a knowledge graph and research corpus. Members contribute through documentation, analysis, and synthesis of research material relevant to the network's mission.

Governance

Governance is a core contribution pathway, not a secondary activity:

• Proposals: Submit ideas for network improvements through the governance process
• Voting: Participate in decisions through the DAO ratification system
• Circles: Join holacracy circles aligned with your skills and interests
• Tensions: Surface and process organizational tensions through the integrative decision-making process

See the Circles and Governance guide for how governance participation works in practice.

Community

• Help onboard new members through circles
• Participate in governance discussions
• Contribute to the network's collective knowledge base

How Work Is Organized

Work within fxyz follows a GTD-inspired task system integrated with the holacracy structure:

• Projects are multi-step outcomes owned by a role within a circle
• Actions are concrete next steps assigned to a role, with context tags (e.g., @computer, @calls) and priority levels
• Members see their projects and actions across all their role assignments in the Tasks surface

Code Standards

Members contributing code follow these conventions:

• TypeScript throughout
• Biome for linting and formatting (not ESLint/Prettier)
• Conventional commit messages: feat:, fix:, docs:, refactor:, test:
• Unit tests for new features

Recognition

Contribution is recognized through the network's scoring system, which factors into governance weight and tier advancement. The CES (Contribution Evaluation System) production function combines multiple domains of participation into a unified score.

Contact

• Website: fxyz.network
• X: @fxyznetwork