What this paper is. The current product direction and the commitments we intend to deliver. Frontends and simulations are available before launch. Token terms, dates and operating capabilities are announced separately; this paper is not an open offering or a claim that the whole system is live.
A world people can help shape.
Good ideas, willing people and useful resources exist everywhere. The difficult part is bringing them together and keeping the result working.
SOS Systems means Sovereign Operating System. It is a system being built to help people coordinate knowledge, work, funding, resources and shared decisions. MY3YE is the movement bringing people into that work. The ambition is peace, abundance and prosperity for all beings, pursued through outcomes people can inspect and improve.
For a person, that can mean finding useful work, carrying a learning history forward or having an AI help with a chosen goal. For a community, it can mean obtaining a shared resource, funding a project and caring for it over time. For a creator, it can mean finding collaborators and retaining credit for what others build upon.
Sovereignty begins with the person. Privacy, basic needs, freedom of choice and a voice must not depend on productivity or the size of a wallet. Greater responsibility over shared systems needs evidence, limits and a way to challenge decisions.
One need. Many ways to contribute.
Begin with something people need. Give that need a plan, then connect it to the people and resources that can fulfil it.
Manifest records the outcome, work packages, dependencies, available resources, funding gaps and continuing obligations. KOINK FUN brings projects and backers together around a published delivery plan. SideGigs turns agreed work into assignments, evidence and review. Bloom connects the skills a task needs to learning and teaching. Umahn is the planned foundation for distinct human participation and scoped reputation. Otto helps carry context and coordinate the next step.
The loop ends with more than a completed task. Record what worked, who contributed, what it cost and what needs care next. That record should help another person or project begin with more knowledge than the first one had.
The initial experiments are deliberately accessible. The Pen will build PiPi’s lore and assistant knowledge. Otto Music will bring people together to create, curate and improve a music platform. Both can create real briefs for writers, artists, reviewers, designers, developers and organisers.
Capital should have a visible job.
A project should explain what it is building, what backing it means and what has to happen before more money is spent.
KOINK FUN is a launchpad for projects and their communities, including technology, culture, education, public goods and physical projects. Project koins are project tokens. Their rights are specific to the published terms of each launch; they are not automatic ownership of every project in SOS Systems.
The multi-asset goal includes ETH, SOL, BTC, USDC, USDT and PIPI as an additional option. Each launch must name the assets, networks, settlement and refund routes it actually supports. Chain-agnostic participation is a direction to deliver, not a claim that every asset works everywhere today.
The milestone design holds project funds for staged release after evidence is reviewed under the declared rules. A real launch needs acceptance criteria, accountable reviewers, conflict handling, a dispute route and clear treatment of unused capital. Funding a build before its product is complete is compatible with this model: the scope, dates and use of funds must be explicit.
Token supply, distribution, fees, custody, liquidity, vesting and any early-backer rewards belong in each launch’s published terms. This paper does not invent those terms or promise returns. Buying a project token does not purchase unrestricted authority over SOS Systems.
Keep the people in the record.
A useful result can depend on a creator, a teacher, a reviewer, a maintainer and work that came years before it.
Contribution records should connect a person’s role to the brief, delivered work, relevant permissions, review and later corrections. Code, research, art, teaching, care, coordination and resources need suitable evidence. Attention alone is not a universal measure of usefulness.
Payment, reputation and governance answer different questions. Payment compensates agreed work. Reputation helps others understand a track record in a specific context. Governance determines who may make a particular shared decision. None should be silently substituted for another.
Umahn’s direction includes scoped ratings and reputation, with independent review, recovery, privacy and appeals. A rating must explain its basis and allow correction; it must not become a score of someone’s worth or a barrier to basic dignity.
Founding work should be documented and assessed under the same rules as later contributions. Prior work, expenses and rights can support a fair compensation proposal, reviewed independently with conflicts disclosed. Recognition does not create a permanent veto or an automatic controlling share.
Give responsibility a path in, and a way out.
A system serving everyone must be able to correct itself, including when a founder, reviewer, institution or AI is wrong.
The governance goal combines broad human participation with responsibility informed by relevant contribution and experience. Decisions need a defined scope, affected people, evidence, reviewers, reasons and a route to appeal. A person should be able to contest an assessment without surrendering unnecessary personal information.
Limits on concentrated influence, conflict rules, reassessment, role expiry and recovery are requirements to develop. Funding a project, owning an agent or arriving early should not give someone unlimited control. Institutions and organisations can contribute through explicit roles; their authority must have boundaries and ways to revoke it.
Earlier papers explored impact decay, capital caps and KOIN, DIME and PENNY mechanics. These remain research, not adopted launch terms. Inflation, rebalancing and reward policies require simulations, independent criticism and an agreed adoption process. A formula cannot establish its own fairness.
Intelligence on your side.
PiPi makes the first encounter inviting. Otto carries the context. People retain authority over the actions that affect them.
PiPi’s first assistant goal is focused: understand an approved, credited collection of lore. The Pen simulation lets people try the write, review, publish and ask loop now. Its responses are local demonstrations, not a live AI service.
The KOINK Terminal is the planned workspace for exploring projects, learning opportunities, contribution needs and financial decisions with PiPi. Otto connections should carry only the context and permissions a person chooses. Public community knowledge and private personal memory have different purposes and access rules.
Capabilities open in stages: reading and explanation, drafts people can inspect, paper experiments, then bounded actions where the necessary controls exist. Real trading and other consequential actions need clear authority, limits, revocation and an inspectable record. Neither an assistant’s confidence nor a simulated result is proof of a good decision.
Preparation for a quantum future means designing for cryptographic change: inventory dependencies, separate keys and permissions, support migration and test recovery. Post-quantum protection is a research and implementation programme, not a blanket promise attached to today’s website.
Own the responsibility, not just the asset.
When a community needs compute, equipment, energy, land or a place to work, acquiring it is part of the system’s job.
Manifest can turn a resource gap into a proposal to buy, lease, borrow or share. Compare alternatives and total costs, identify a budget and accountable owner, and state how delivery will be checked. Record legal ownership, custody, access and operating responsibility separately.
Care belongs in the initial plan: maintenance, insurance where needed, trained operators, renewal, ecological effects and eventual disposal or transfer. A digital record or community vote alone does not establish legal title to physical property.
Tusita explores the whole model in places people could live, work and gather. Panik focuses on a decentralized safety network; Shakrah on everyday wellbeing. Each must establish its own operating readiness. Their communities can form and help with the build before the service or place opens.
Show the vision. Build the story. Make the music.
$EYE → PiPi → Otto Music. Separate openings, connected purpose.
The proposed first launch is EYE, bringing MY3YE’s vision to the world and gathering a community around the build. PiPi follows with the Pen as the first coordination experiment. Otto Music follows as the second, starting from released music and inviting collaborative creation, curation and platform improvement.
Each launch announcement will distinguish its token event, initial product capabilities and later milestones. Frontends and simulations can demonstrate the intended experience before those features are connected to production services. Funding can support that work under a declared plan.
Dates are still to be announced. Leave time between releases for feedback, support and improvements. A meaningful or auspicious opening can celebrate the community; readiness and clear communication determine what is actually offered on that day.
Community stewardship can grow from the experiments. It needs people willing to take responsibility, clear roles and the resources to operate them. A handover is a deliberate milestone, not an assumption that a crowd will run the system automatically.
What will you bring?
A skill. A story. A question that makes the plan better.
Try the first experiment ↗Introduce yourself ↗