Bring people around a shared vision. Turn one clear need into funded, reviewed work. Keep the result, the credit and the lessons. Then do it again.
MY3YE is the movement building SOS Systems. Our proposed first phase forms the community and the founding economy that can support the work towards the full vision.
Proposed delivery plan
The pages and previews explain the direction. The connected paid loop still needs to be demonstrated. The gates below are requirements, not completed milestones.
01 / How it works
From a need to the next possibility.
A small connected loop is the first operational goal. Explore each handoff, what must be agreed and what evidence travels with it.
Step 01 / 08 · Project lead · Manifest planning
Name the need
Start with a need people understand and a useful result someone will take responsibility for.
Illustrative PiPi commission
For the proposed PiPi pilot: commission a small lore collection that a reader and a focused assistant can use.
What carries forward
Project reference, purpose, owner and intended outcome.
Before the next step
Name the people the result serves and who will maintain it.
Every result should make the next beginning easier.
01 / 08
One connected history
Person → project → funding → task → outcome Consistent references connect the brief, agreement, delivery, review and payment. Sharing progress does not mean publishing someone’s whole identity or private evidence.
02 / The connected pieces
Three small slices. One useful journey.
Build only what the first pilot needs, with shared person, project, funding, task and outcome records. Each project keeps its wider purpose.
in development
Umahn
Keep the person connected.
A personal account for carrying your identity, learning and contributions across the system, with recovery and control over what you share.
Needed for the first loop
A chosen participation identity, a tested continuity or recovery route, permissions and an exportable contribution record.
Current documented scope
The account and participation specification is drafted. Handle Wars runs separately as an SOS naming experiment on Arc Testnet. The integrated Umahn account and participation modules are not open yet.
Keep shared needs, available resources and continuing responsibilities in view. Its intended role maps needs, offers, budgets, dependencies and continuing care.
For Phase One, that can begin as a shared, versioned project brief and dependency board. A complete Manifest platform is not a prerequisite for the first pilot.
Five workstreams, connected by a few essential agreements. This is a proposed dependency board; owners, budgets and dates still need to be set for the pilot.
01To demonstrate
Vision & invitation
Make the whole destination understandable, and give people a useful first step.
Explain Phase One, the wider vision and actual preview status.
Preserve EYE → PiPi → Otto Music with separate opening scopes.
Name an organising contact and verify the introduction handoff.
Start here
Can progress now alongside onboarding and briefs.
Evidence: A new visitor can explain the goal, find a role and prepare an introduction.
Sequence by readiness. Build independent pieces together.
01
Agree the smallest useful pilot
Write the brief and shared record format. Choose the owner, reviewer, participation rules and funding responsibilities.
Vision, onboarding design and founding briefs can progress together.
02
Build the connected slices
Umahn continuity, KOINK project and commitment records, and SideGigs assignment and review can develop in parallel against the same references.
Test with fictional records first. Keep Manifest’s needs and dependencies in a shared brief; its complete platform is not required.
03
Run one bounded paid cycle
After terms, real budget, privacy and review are ready, agree a task, deliver, review, pay and issue the record. Reconcile every handoff.
Prepare the next brief while the first pilot runs. Public release readiness is checked separately.
04
Repeat, recover and challenge
Carry the result into another task or project. Test loss of access, rejected work, disputed credit and an unavailable operator. Publish what worked and what remains.
Improve the interfaces and operations from evidence before expanding scope.
Required before real work
Participation and privacy choices; basic continuity or recovery; a priced brief, acceptance criteria and reviewer; funding, custody and payout responsibility; attribution, corrections and appeals.
Can develop beyond the first loop
A full blockchain network, a token launch and a fully autonomous Otto are not compulsory blockers. Use a disclosed, accountable pilot process while those capabilities develop. Real money still requires a suitable agreed route.
Public openings / Operational capability
EYE → PiPi → Otto Music
The public release path begins with EYE, introducing the movement and declared build funding. PiPi is the first coordination experiment; Otto Music is the second.
Each opening needs its own scope, terms, funding plan and announced date. Dates remain unselected. Public previews can gather a community before the connected service is ready.
The Phase One test is whether the work loop completes and repeats. A token opening alone does not demonstrate that capability.
People can join a clear project, complete agreed work, receive the agreed payment and carry the evidence into another opportunity. These proposed exit criteria need observable proof.
01
Someone can find a real next step.
The invitation names a bounded project, its responsible people and how to join. The introduction handoff is tested; it does not pretend to assign work.
02
The brief and budget are checkable.
Scope, acceptance criteria, permissions and reviewer are agreed. Funding commitments, available money, custody and payout responsibilities are recorded separately.
03
Useful work completes an independent review.
An agreed assignment produces a versioned deliverable. A separate reviewer records acceptance or revisions against the brief, with disclosed conflicts.
04
The agreed payment completes.
Payment evidence reconciles with the task and budget. The contribution receipt records the contributor, source, reviewer and accepted outcome without inventing an impact score.
05
The person and evidence survive the next step.
Test continuity or recovery, selective export and verification by another project. Preserve attribution, permission limits and dispute history through the handoff.
06
The loop works again, including a challenge.
A second task reuses the first result or its records. Exercise a correction or appeal, show unresolved obligations, and publish a permissioned account of the pilot’s limits.
Success is a reviewed, repeatable founding capability with named operators and visible limits. It does not mean the whole economy, autonomous intelligence or physical Tusita is complete.
05 / Keep the full destination in view
A small beginning. A much bigger horizon.
The ambition is peace and prosperity for all beings, through personal sovereignty, local capability and planetary cooperation. Phase One creates the people, work and evidence the later horizons need.
H1
Movement & founding economy
Gather people, support the first useful work and establish the connected loop.
This page’s focus
H2
Portable participation & connected production
Carry chosen records across projects; connect work, learning and resources.
H3
A sustaining economy
Support ongoing services, care and renewal through dependable activity and income.
H4
Distributed intelligence & governance
Develop shared intelligence and accountable decisions with human review and appeal.
H5
Physical Tusita
Apply the model in a place people can build, inhabit and sustain together.
H6
Federation
Let sovereign communities cooperate, share capability and retain local choice.
H7
Planetary cooperation
Coordinate common needs and ecological responsibilities towards peace and prosperity for all beings.
These are development horizons, not dated promises. Each step must earn confidence through use, independent review and continuing care.
The existing participation page lets you review an email draft and send it yourself. Preparing it sends nothing. An introduction is not an account, assignment or funding commitment. No token purchase is needed.