Cooperative Covenant
Version 0.1 · Last reviewed 2026-07-01 · Sandbox draft
Sandbox draft
Working draft. Production version carries counsel review and a signed effective-date footer counter-signed by the founding Members.
At a glance
Terms of Service — plain-language summary
By accepting, you agree to participate in the Future Modern cooperative as a member or partner in good faith. You agree to the tier you were invited under, its associated responsibilities, and the Future Modernist's Code above.
Your account is provisioned to your email address. You are responsible for keeping that address secure. Signing in uses magic links delivered to that address; possession of the address is treated as authorization.
Contributions you make through the cooperative — projects, referrals, governance activity, review — are subject to the reciprocity floor described in the Code. Membership review may follow prolonged inactivity.
You may leave at any time. Future Modern may pause or end membership when the relationship stops being reciprocal, as described in the Sovereignty principle.
Personal data you provide is used to operate your account and match you to relevant opportunities. It is not sold. Data participation (the labor-value dataset) is a separate, optional opt-in below.
This is the same summary shown during the invite acceptance ceremony. The full canonical policy follows below.
What the cooperative is for
$BUILD.Store is a shared professional infrastructure owned and operated by its Members. It exists to make it possible to do serious, well-compensated creative and technical work without surrendering the upside to an employer, a marketplace platform, or a private-equity aggregator. The Covenant is the shared operating agreement that keeps the cooperative worth belonging to.
Governance principle: bicameral, one voice per body
Governance runs in two chambers, both one-person-one-vote inside their own body. Token holdings never weight votes — anti-whale at the governance layer. Partners vote in the Partner body on operational rules (matching, RFP flow, moderator selection, admin approvals, cohort spotlights). Members vote in the Member body on existential rules (treasury, covenant amendments, tier structure changes, direction pivots, admissions) and ratify structural proposals sent up from the Partner body.
Relationships inside project teams and client engagements are hierarchical when the work requires it. Someone owns delivery, someone owns account, someone owns direction. That hierarchy is confined to the engagement. Governance is not for sale, and leadership on one project confers no permanent authority over another.
What every Member commits to
- Deliver work you agreed to. Missing milestones without communication is the number-one trigger for the compliance ladder below.
- Communicate at least weekly. Silence is a signal, and the cooperative reads it. Say you're heads-down, say you're stuck, say you're overextended. Just say something.
- Route through the platform. Client relationships originated through the cooperative stay on the cooperative. Direct-hire circumvention is a covenant violation.
- Give peer review honestly. The MVP score depends on peer input being useful, not polite. Ratings that don't match the work devalue the system for everyone.
- Respect the confidentiality stance. Members see each other. Outsiders see what Members choose to publish. Client-privileged information stays with the engagement.
MVP score. How standing is measured.
Every active Member carries an OVR (0-99) computed from seven sub-ratings: quality, outcomes, reliability, hustle, collaboration, attendance, referrals + BD. Twelve-month rolling window, weighted to recent work. Provisional new Members do not carry a public OVR until they cross the promotion threshold (roughly three completed engagements + two peer reviews received).
Bands: 90+ Champion's Court eligible. 75-89 Promotion eligible. 65-74 Good standing. Below 65 Probation.
Compliance ladder. The penalty mechanic.
Covenant violations produce compliance penalties. Each penalty is -9 OVR for 90 days, stacking. The math is deliberate: three penalties inside 90 days moves a middle-band Member into probation; four moves them toward removal. Real-time impact prevents the pattern where a Member's slow decline is only recognized after a year of accumulated damage.
Penalties are admin-recorded with an arbitration record. The reason text is preserved in the immutable audit log. Rescission by admin is possible and itself audit-logged. A Member facing a penalty they believe is mistaken can invoke the cooperative arbitration process; the formal Arbitration Procedure document lands with the production LLC operating- agreement rewrite (see production-swap-checklist.md §9).
Recognition rails. How excellence is surfaced.
- Future Modernist of the Month: admin editorial pick while the cooperative is small, Member vote once voting Membership is large enough to make the outcome meaningful. Open to Members and Partners; recognition unlocks a public-discovery window for Partners.
- Constellation of [Year]: annual cohort of Members who held Champion's Court standing during the year.
- Champion's Court: standing tier for Members in the top 10% AND at OVR ≥ 90. Refreshes with each daily compute.
- Annual canonization: at the end of every calendar year, each active Member (and any Partner who held a recognition during the year) mints an ERC-721 canonization card with ERC-6551 token-bound account. Tier locks to year-end rarity band.
Cooperative canon starts at zero
The first canonization runs at the end of the cooperative's first full calendar year of operation. No retroactive canon. Members do not receive credit for pre-launch work through the cooperative record, because retroactive minting would invent standing that nobody earned through the system. This is the integrity floor.
How the Covenant changes
The Covenant is existential — hard to reverse, sets the terms every Member signs — so amendments route through the Member body, not the Partner body. Proposed changes are posted at least 30 days before the vote so Members have time to read, discuss, and weigh in. Voting is one-person-one-vote; token holdings do not weight the vote. Sandbox runs admin-only proposal for testing; production runs the real vote.
Exit
Members can exit voluntarily at any time. Contribution record + canonization cards remain. The cooperative record does not retroactively erase what someone contributed. Data subject erasure is available at /profile/data-rights and covers personal data; the financial subset is retained per legal-hold policy documented in the Privacy Policy.