V1 readiness
3 of 11 items pass
Still open: both co-editor seats filled (fully staffed), coordinator in place, integrated changes published as a numbered ml-draft revision, chapter checked against neighbouring dps for terms, overlaps and conflicts, every must and should is testable or rephrased as guidance, all contributors acknowledged, no release blockers open from the readiness review, v1 candidate revision published before the freeze
Developer and Community Incentives
How do we stop rebuilding the same foundations on every platform?
Developers rebuild the same things repeatedly
Build for the web, not for a landlord.
Developers spend careers reimplementing identity, feeds, and moderation for each silo. Better incentives reward shared infrastructure and portable contributions.
Why this matters
A small team ships a useful community tool, then rewrites it three times for three platforms. Progress stalls while the underlying need never changes.
- Duplicated effort
- API churn
- Talent drained into integration work
- Weak rewards for open primitives
Today's challenges
- Per-platform SDKs
- Unrewarded commons work
- Short-term venture pressure
- Fragmented contributor recognition
Why today's Web struggles
Platforms pay for exclusivity. Shared layers threaten moats, so incentives pull builders toward proprietary stacks instead of common rails.
Platform lock-in
Imagine instead
Developers ship Meta-Layer capabilities once and communities fund the commons that everyone reuses.
- Portable contributor reputation
- Incentives for interoperability work
- Shared primitives instead of endless forks
Build once, run across the Metaweb
Why this matters to everyone
- Developers
Spend time on new value, not re-plumbing silos.
- Funders
Support infrastructure with clear public goods outcomes.
- Communities
Reward maintainers who keep shared tools healthy.
- Startups
Compete on product, not on captive graphs.
Meta-Layer capabilities
- Interoperability
- Reputation
- Micropayments
- Community Governance
- Portable Identity
Real-world examples
- Open source
Sustained maintainer incentives.
- Civic tech
Reusable governance modules.
- Education tools
Shared learning primitives.
- Identity stacks
Build once for many surfaces.
Join the challenge
Choose how you'd like to contribute.