Build With Us
How to get involved.
Mastermind City is at the proposal stage. Every person who engages now is shaping the foundation. This page maps every pathway — from curious reader to founding node.
From Proposal to Reality
The 90-Day Pilot Framework.
The pilot framework takes a group of committed people from first conversation to a live, operating node with a signed charter, assigned roles, and a functioning OS instance — in three months.
Month 1
Orientation & Alignment
Ground everyone in the concepts. Identify who genuinely wants to build together. Surface assumptions and differences early.
- Work through the core documents as a group
- Each person writes a one-page vision of what they want to build
- Map the group's skills, resources, and constraints honestly
- Identify which node type best fits the group's intent
- Surface and name any major concerns or blockers
- End with a decision: continue to Month 2, or part ways respectfully
Month 2
Design & Stress-Test
Design the specific node. Stress-test the assumptions. Make the model concrete enough to commit to.
- Draft the node's charter and purpose statement
- Assign provisional roles — live with them for a month
- Simulate a full 30-day cycle on paper before running one live
- Identify the node's economic model and resource requirements
- Stress-test: what happens if one member leaves? If revenue drops?
- Draft federation participation intent (or standalone decision)
Month 3
Genesis & First Cycle
Stand up the OS. Run the genesis process. Complete and document the first live cycle.
- Install the OS and run the node formation wizard
- Sign the charter — all members, witnessed
- Generate node cryptographic identity
- Run the first Opening Council
- Execute the first 30-day cycle fully
- Submit the first cycle record to the pilot federation
Your Entry Point
Choose your pathway.
Not everyone comes to this the same way. Select the path that most closely matches where you are and what you want to contribute.
The Observer
You're intrigued by the concept but not ready to commit. You want to understand it deeply before deciding if it's for you. This is the most common entry point — and a legitimate one. Premature commitment to something you don't fully understand is how communities fail.
The Observer pathway gives you structured ways to learn, ask questions, and watch pilot nodes in action — without any obligation to join or build.
Now
Read the full spec
Work through all the core documents. Take notes on what's unclear or unconvincing.
Next
Submit feedback
Use the form below to share your questions, objections, or ideas. Everything gets read and considered.
Optional
Join the observer network
Receive updates on pilot node formation, OS development milestones, and open calls for input.
If ready
Upgrade to Member or Founder
When you're ready to commit, there are clear pathways forward. No pressure timeline.
The Node Member
You want to be part of a node — contributing, participating in the cycle, holding a role — but you're not looking to be the person who founds it. You're a builder, a maker, a craftsperson, or a community member who functions best as part of an already-forming group.
Node Members are the majority of any healthy community. The OS is designed for people who don't want to think about governance — just show up, contribute, and trust the structure to handle the coordination.
Step 1
Understand the role structure
Read the How It Works and Charter pages. Know what every role involves before joining a node.
Step 2
Express your interest
Use the form below to tell us what kind of node you want to be part of, and what you bring.
Step 3
Match to a forming node
We'll connect you with Founders who are forming nodes that match your node type preference and skill set.
Step 4
Month 1: Orientation
Join the node's Month 1 orientation. This is a mutual evaluation — you're assessing them as much as they're assessing you.
Step 5
Charter Signing
If Month 1 produces genuine alignment, sign the charter. You're a founding member of a live node.
The Node Founder
You have a vision for a specific community — a place, a practice, a business, or a project — and you want to use the Mastermind City OS as its organizational backbone. You're not just joining something; you're building it.
Node Founders go through the full 90-Day Pilot Framework. This is the most demanding pathway, but also the most generative. Founders who go through this process produce the documentation and patterns that improve the OS for everyone who comes after them.
Before you start
Find your core three
Identify three people who understand the concept and are genuinely interested in building together. Quality matters far more than speed here.
Month 1
Orientation & Alignment
Full group works through the spec, surfaces their individual visions, identifies node type, maps constraints.
Month 2
Design & Stress-Test
Draft the charter, simulate a cycle, stress-test the model, decide on federation participation.
Month 3
Genesis
Install the OS, sign the charter, generate node identity, run the first live cycle.
Ongoing
Pilot feedback loop
Pilot nodes submit structured feedback to the OS development team after every cycle. You're co-building the system in real time.
The OS Builder
You're a developer, designer, or technical architect who wants to help build the actual software. The OS needs to exist as real, working code — a downloadable Tauri application, a suite of smart contracts, a P2P communication layer.
This is open-source work with a genuine philosophical mission. The codebase will be public. Contributions are attributed on-chain. The software should be as well-crafted as the idea it serves.
Now
Read the technical spec
The DAO & Records and Technology pages describe the full architecture. Form a view on what you'd approach differently.
Next
Engage on GitHub
The repo is live. Open issues, propose architecture decisions, or contribute to the spec documents directly.
Phase 1
Node OS core
The first build target: a working Tauri app that handles the cycle, roles, decisions, and contribution ledger. Offline-first.
Phase 2
Smart contracts
Node registry, contribution proof anchoring, and the treasury contract on Base. Auditability is a design requirement, not an afterthought.
The Federation Architect
You have expertise in legal structures, cooperative finance, DAO governance, or distributed organization design. You want to help design the federation layer — the rules, the treasury mechanics, the inter-node protocols, and the legal wrappers that make the network durable and defensible.
This work is upstream of the first nodes. The federation layer needs to be designed before it's needed — because retrofitting governance onto a running network is far harder than designing it correctly from the start.
First
Engage on the DAO design
The Blockchain & DAO page presents the current architecture. It's a starting point, not a finished design. Your critique is valuable.
Next
Legal wrapper design
The federation needs a legal entity in at least one jurisdiction. Wyoming DAO LLC, Swiss foundation, or a Marshall Islands structure are the leading candidates.
Phase 2
Treasury mechanics
Design the contribution weighting formula, the distribution schedule, and the capital access criteria that make federation membership materially valuable.
Phase 3
Inter-node protocols
Labor exchange, capital sharing, dispute resolution, and the node admission standards that maintain the quality of the network without gatekeeping its character.
Get In Touch
Express your interest.
This form is not an application. There's nothing to be accepted into yet. It's a way of putting yourself on the map — letting us know who you are, what you're interested in building, and how you might fit into the emerging network.
Everyone who submits gets a personal response. Not a form email. If what you're describing is something we think could work, we'll start a real conversation.