Vision
People can direct meaningful lives through relationships, capabilities and resources that endure across compatible systems, with meaningful control over their choices and participation in an open economy.
Me · The individual
For individuals: develop capabilities, make informed choices and turn personal intentions into useful outcomes with control over identity, relationships and memory.
Your own identity, relationships, work and choices. Acting for an organisation or operating an agent requires an explicit permission or mandate.
Try the experienceExplore the design. Account features are in development.
See product evidence and gaps
Individuals · Me
Your network is your net worth: relationships expand what you can know, do and become. Me connects that network to your purposes, knowledge, resources and choices. Learning, care and reciprocity belong here too.
People can direct meaningful lives through relationships, capabilities and resources that endure across compatible systems, with meaningful control over their choices and participation in an open economy.
Give each person a continuing personal interface and Cloud Computer that connects intentions, people, information, resources and commitments, helping them turn intent into useful outcomes on their own terms.
You remain the principal. APU supplies the interface; Agentz coordinates permitted work, Cortex memory and Nexus connections. You can develop your purposes progressively, beginning with an ordinary conversation.
Objectives
The intended personal experience supports the life you choose to build.
Express and revise purposes, priorities, constraints, available time and next actions.
Choose sources, inspect why information appeared, replace ranking methods, compare evidence and revise beliefs.
Maintain uplinks, connections and downlinks; communicate, collaborate, discover opportunities and contribute through the relationship context you permit.
Understand currency, capital positions, reserves, rights and obligations. Compare offers and use appropriate order books and contracts under the applicable authority.
Learn, work, obtain help, organise activities, offer capabilities and exchange value. Delivery, acceptance, payment and a fulfilled need each require their own evidence.
Retain chosen knowledge, sources, commitments, learning and attributed milestones so experience can improve future choices.
Continue across qualified interfaces, agents and providers. Change grants, recover under an implemented policy and leave a service with available permitted records.
A personal case · fictional local example
Relationships expand what you can know, do and become. Nora wants to learn robotics, contribute to a workshop and explore paid work while protecting her reserves.
Follow a published milestone, request an introduction and choose what happens next. Learning, friendship and contribution can be valuable outcomes in their own right.
No introduction requested. No learning or contribution outcome has been reported.
1 · Find a connection

No introduction requested.
Permission to request an introduction reveals no private contact details. Reply controls simulate Sam’s decision; they send no message.
2 · Meet in context
Fictional workshop participant · published profile
Robotics, repair and helping newcomers. Public posts and milestones provide context; private contacts have their own permissions.
Workshop induction announced. The schedule is revision 1; review the source before relying on it.
“We welcome people who want to learn and help maintain the workshop.”
The conversation has not opened. This example first waits for the introduction.
Nora’s private contact detail has not been shared.
No account-administration controls belong in another participant’s view. A public profile, private contact entry and chat are different records.
3 · Choose what continues
No note retained.
Closing the conversation keeps only the note Nora chose in this example. Published milestones and any separate agreement keep their own records. The workshop corrects the induction from Tuesday to Thursday. Existing history is preserved; a retained note needs review. Any unsigned paid-work draft is withdrawn for fresh review.Try a source correction
4 · Decide on your terms
Nora has not chosen a next activity.
Outcome controls illustrate an attributed report. A choice, report, independently accepted result and payment are different states.
Qualified alternatives use compatible software, available permitted records and the same grants. Restoring transport or changing provider does not deliver a pending invitation, add permissions or recover a key. This example pauses story actions during an interruption; chosen records and permissions remain unchanged.
Rotation requires the current example key. It retires that version for future actions. Rotation or recovery preserves chosen notes and contact-sharing choices, withdraws an unsigned work draft and requires fresh source review before preparing another.
The illustrative policy assumes a separate recovery credential and verifier were arranged before loss. A real policy must define accepted proof, authorised verifiers, delays, expiry and revocation. None is configured or checked here. Review, cancellation and simulating conditions being met are separate choices.
Public/private keys, separately qualified encryption and distributed infrastructure are the design foundation. This local case generates no keys and performs no cryptographic recovery or mesh communication.
The workshop may need an actuator before it can deliver an inspection service. Its procurement has its own account, authority, exact agreement and acceptance.
Follow Nora’s part in the actuator caseAll state is held in this page’s memory and resets on reload. No real profile, message, grant, note, order, payment or issued receipt is created.
Contributing product strategies
Use the capabilities a task calls for. Each product owns its strategy, proposed measures and specialist Agents. The Rosetta correspondence connects its field of inquiry to skills and responsibilities.
Rosetta agent row · Teleology
Make purpose, acting context, alternatives, disclosure and decisions understandable. Proposed KPI. Decision comprehension: sampled reviews in which the person identifies purpose, recipient, disclosed context, cost and consequence divided by sampled reviews. Measure time to resume a permitted case separately. Collection requires an appointed owner, permitted records and an agreed protocol. Definitions do not start telemetry or appoint anyone. Specialist Agents. Intake guide; Information organiser. Skills and responsibilities. Clarify and present information while keeping a suggestion distinct from acceptance. Capability snapshot: 2026-10-17. Each source keeps its own evidence level. These records do not establish a live service. Representative Flutter source. Representative interface and case source only. A composed case does not establish a released APU interface or accepted signed-in journey. Inspect the dated Flutter inventory and its limits. Repository access may be required. Future integration. APU owner: qualify the actual purpose/review screen, permitted inputs, accessibility and refusal paths on the target devices.Proposed measures and specialist Agents
How this would be measured
Decision comprehension
Time to resume a permitted case
Sources and integration limits
Rosetta agent row · Epistemology
Preserve the sources, dates, uncertainty and corrections behind personal decisions. Proposed KPI. Source coverage among material claims used in sampled recommendations; time for accepted corrections to appear in affected fresh answers. Report unresolved conflicts separately. Collection requires an appointed owner, permitted records and an agreed protocol. Definitions do not start telemetry or appoint anyone. Specialist Agents. Source researcher; Corrections editor. Skills and responsibilities. Research and correct attributable information. A connection or public profile does not establish verified identity or trust. Capability snapshot: 2026-10-17. Each source keeps its own evidence level. These records do not establish a live service. Representative Flutter source. The Flutter case is host/adapter context. Its presence and the website correction example do not establish an integrated Circle service. Inspect the dated Flutter inventory and its limits. Repository access may be required. Future integration. Circle owner: qualify attributed source retrieval, independent comparison and correction propagation with genuine permitted sources.Proposed measures and specialist Agents
How this would be measured
Traceable claims
Correction propagation time
Sources and integration limits
Rosetta agent row · Methodology
Compare uncertain choices concerning time, work, resources and opportunities. Proposed KPI. Forecast performance against a declared baseline on eligible resolved questions, with resolution coverage, unresolved cases and abstentions reported. Collection requires an appointed owner, permitted records and an agreed protocol. Definitions do not start telemetry or appoint anyone. Specialist Agents. Scenario analyst; Forecast researcher. Skills and responsibilities. Make assumptions explicit and keep forecasts advisory. Capability snapshot: 2026-10-17. Each source keeps its own evidence level. These records do not establish a live service. Representative Flutter source. The Flutter case is host context. A market response or fictional comparison does not establish calibrated forecasting or an accepted resolution lifecycle. Inspect the dated Flutter inventory and its limits. Repository access may be required. Future integration. RealityFutures owner: qualify question, assumptions, baseline, horizon, resolution and abstention on the same versioned records.Proposed measures and specialist Agents
How this would be measured
Binary forecast Brier score
Continuous forecast mean absolute error
Resolution coverage
Sources and integration limits
Rosetta agent row · Axiology
Maintain the case, coordinate specialists, retain accepted Cortex memory and supply purpose-limited Nexus context. Proposed KPI. Continuity success among eligible resumptions: required permitted records, provenance, constraints and commitment versions recovered without added access. Track actual scope violations separately from blocked attempts. Collection requires an appointed owner, permitted records and an agreed protocol. Definitions do not start telemetry or appoint anyone. Specialist Agents. Work coordinator; Memory steward; Context curator. Skills and responsibilities. Coordinate permitted work and context. Each assignment receives its allowed view of contacts, conversations and accounts. Capability snapshot: 2026-10-17. Each source keeps its own evidence level. These records do not establish a live service. Representative Flutter source. Source and bounded proofs retain their original limits. Cortex memory and Nexus connections belong to Agentz; website state is not durable or signed-in continuity. Inspect the dated Flutter inventory and its limits. Repository access may be required. Future integration. Agentz owner: accept effective grants, retained records, versioned handoff, provider refusal and recovery in the signed-in host.Proposed measures and specialist Agents
How this would be measured
Permitted continuity
Actual scope violations
Blocked out-of-scope attempts
Sources and integration limits
Rosetta agent row · Cosmology
Prepare commitments, clarify responsibility and acceptance, and review outcomes and remedies. Proposed KPI. Commitment completeness before acceptance; due commitments supported by accepted outcome evidence, with cancellations, disputes and unresolved discrepancies reported separately. Collection requires an appointed owner, permitted records and an agreed protocol. Definitions do not start telemetry or appoint anyone. Specialist Agents. Commitment planner; Evidence reviewer. Skills and responsibilities. Prepare dependable agreements and review their evidence. Qualified insurance requires a named provider and policy. Capability snapshot: 2026-10-17. Each source keeps its own evidence level. These records do not establish a live service. Representative Flutter source. Marketplace source supplies commercial context only. Menexus integration, independent acceptance and any named insurance provider/policy remain unqualified. Inspect the dated Flutter inventory and its limits. Repository access may be required. Future integration. Menexus owner: qualify commitment, independent review and remedy contracts; qualify insurance separately with its actual provider and terms.Proposed measures and specialist Agents
How this would be measured
Commitment completeness
Accepted due outcomes
Unresolved discrepancy age
Sources and integration limits
Rosetta agent row · Ontology
Compare exact offers, use eligible orders and payments, and reconcile authorised effects. Proposed KPI. Effects due for reconciliation linked to their applicable authorised instruction or commitment, confirmed effect and account entry; unmatched records and duplicate effects, including replay and recovery, reported separately. Collection requires an appointed owner, permitted records and an agreed protocol. Definitions do not start telemetry or appoint anyone. Specialist Agents. Offer specialist; Reconciliation specialist. Skills and responsibilities. Compare offers and reconcile records within the applicable authority. Comparison alone does not grant transaction authority. Capability snapshot: 2026-10-17. Each source keeps its own evidence level. These records do not establish a live service. Representative Flutter source. Pinned commerce/wallet source is not live signing, custody, exchange eligibility, payment, settlement or an issued OFN receipt. Inspect the dated Flutter inventory and its limits. Repository access may be required. Future integration. LIQUID owner: qualify exact offers, applicable authority, effects, retries/reversals and reconciliation under each record’s actual terms.Proposed measures and specialist Agents
How this would be measured
Reconciliation coverage
Duplicate economic effects
Sources and integration limits
Rosetta agent row · Theology
Relate financial choices to personal goals, horizons, obligations, liquidity needs and protected reserves. Proposed KPI. Mandate fidelity in reviewed recommendations; sampled decisions in which the person understands material risks, costs, obligations and alternatives. Collection requires an appointed owner, permitted records and an agreed protocol. Definitions do not start telemetry or appoint anyone. Specialist Agents. Mandate researcher; Diligence analyst. Skills and responsibilities. Research using permitted records and a defined mandate. Relationships remain valuable without assigning cash values to the contact graph. Capability snapshot: 2026-10-17. Each source keeps its own evidence level. These records do not establish a live service. Representative Flutter source. No dedicated Flutter capital-office integration is established by this inventory. A permitted research proposal is not investment performance or treasury authority. Inspect the dated Flutter inventory and its limits. Repository access may be required. Future integration. MurMur owner: qualify a permitted principal mandate, access controls, constraint review and correction before any service or performance claim.Proposed measures and specialist Agents
How this would be measured
Mandate fidelity
Capital decision comprehension
Sources and integration limits
These are proposed measures with inspectable collection definitions. Measurement owners remain unappointed, collection has not begun and targets remain unset. An unrecorded result is not a measured zero. Local demonstration. Nora’s fictional personal story has page-local introduction, disclosure, chosen-note, correction and refusal states. Paid work remains an unsigned draft. Inspect the separate local example. It uses page-local state and resets on reload; it is separate from the product commissioning-analysis story. Real contacts, messages, retention, key recovery and cross-device continuation require separately accepted app/service integration. Read the full participant VMOSKA source. Repository access may be required.This participant’s example and integration limits
Specialist Agents describe roles and skills in development. People, models and tools may contribute within an explicit assignment. A role description establishes neither staffing nor permission to act. The participant group They remains distinct from these specialist roles.
Interactive design preview · in development
Try the intended interactions. This is a local illustration, not a working account or service.
One to one · example conversation
A little time, just for you two.
Shall we meet
by the garden?
The intended experience is one-to-one messaging with read notifications and a conversation that leaves the screen when the other person leaves. The planned starting point, Nostr private messages (NIP-17), would encrypt message content but would not give forward secrecy, and relays could still see IP addresses and timing.
Media opens in an immersive view.
A reaction is an invitation, never a hidden recording.
A camera reaction would require the viewer’s separate consent—not hidden capture or an inferred emotion.
No encryption, sending, camera or deletion service runs here. Ending a conversation on screen does not erase copies held by relays, recipients or backups.
Three everyday experiences
One-to-one messages with visible retention choices. Another account opens a conversation with its published identity, links, milestones and posts as sourced context.
Preview messagesPublish to your chosen audience. A post, an attributed milestone and a direct message keep their own visibility and retention rules.
Preview publishingThe intended design lets you inspect sources, see why an item appears and replace the ranking method. Choose chronological, relevance or task-focused views to support your decisions.
Preview your feedThese are interaction designs. Nostr can support portable identity and reduce dependence on one intermediary; individual relays can still reject events. Expiration and deletion requests cannot guarantee erasure of recipient or relay copies. Shared connectivity and its protocol mechanisms are explained in SPECTRE, the proposed common foundation.
Agentz · your Cloud Computer
Move from a question to a bounded task, inspect the proposed work and review its result. Agentz owns continuing work, Cortex memory and Nexus connections. APU supplies the interface across the experience.
A task receives the context and budget you permit. A completed response does not silently become accepted memory or permission for the next action.
Work with a shared organisation in We or explore machine participation in They. You may act for an organisation or operate an agent only with the relevant permissions. Your personal identity, its commitments and an agent’s delegation stay distinct.
Explore AgentzCloud execution, encrypted replicas, recovery and cross-device continuity need their own acceptance evidence. This website does not connect a personal Cloud Computer.

A presence of your own
Carry a recognisable presence between compatible tools. Choose which account you are acting for.
Explore the exampleClose the exampleA design you can explore
Nostr-based identity is a starting point, with key storage, signing and recovery kept explicit. Me is your individual context. You may act for a We organisation or operate agents only under the relevant permissions and mandate; choosing a destination or switching accounts does not grant that authority.
Illustration of the idea, not an app screenshot. The example uses fictional details.
Explore identity and keysIdentity design · fictional example
One identity. Different contexts.
A place to decide what belongs in your life.
A public key identifies an account; a private key can sign for it. Compatible tools may recognise that identity. A key alone does not move every file, permission or relationship.
Key storage, backup and recovery need explicit choices. Losing a key can mean losing access; exposing it can let someone act as you. This preview generates no keys and does not demonstrate recovery.

Thoughts with a direction
Conversations, published milestones and accepted memory have different lifecycles.
Explore the exampleClose the exampleA design you can explore
APU is the interface for reviewing useful context. Agentz owns the Cloud Computer and Cortex memory, with sources, revisions and explicit retention. Closing a conversation does not erase a published milestone, an accepted memory or a transaction record. Replica protection, recovery and cross-device continuity remain separate implementation gates.
Illustration of the idea, not an app screenshot. The example uses fictional details.
Explore Agentz memoryAPU-assisted note design · predefined example
No example note kept yet.
“Let’s meet at the garden’s north gate on Sunday. We still need to choose a time.”
When meaning is unclear, APU should ask. An unresolved question stays unresolved; tidying must not turn a possibility into a fact. These examples stay only in this page’s memory and reset on reload—no AI or note storage is connected.
When your plan needs a product or service
The intended Markets journey starts with your need, budget and constraints. An agent compares exact offers, keeps missing information visible and prepares a proposal for your review. You can ask for a correction, choose another offer or buy nothing.
A common receipt trail would link the exact request, permitted disclosure and any authorised action to the resulting records. An OFN economic receipt would add the payment or settlement record when an economic event occurs. A delivered message, completed action, payment and independently checked outcome remain different states. Sharing a receipt need not disclose your whole personal history.
This is the product design. The local walkthrough creates no purchase, payment, personal record or OFN receipt.
Capability evidence ·
Me is the individual context: personal identity, relationships and controls. An individual may act for an organisation or operate agents only with the relevant permissions. Products keep their own responsibilities. These selected capabilities show where source or local proof exists and where the journey is still a proposal.
Evidence describes source or a bounded test, not a released feature. A curated trace of 35 capabilities, not a complete inventory of every code path. None is live-verified or operating-qualified in this trace.
APU can retrieve attributed material inside a selected case in a local host.
What the evidence saysThe local host calls the pinned APU librarian find/cite path against selected case records.
Still to proveDeterministic local retrieval is narrower than APU search service or live model analysis.
Circle is responsible for comparing claims and carrying corrections into dependent work.
What the evidence saysThe local synthetic case retained corrected records and flagged dependent work for review.
Still to proveThis proves a host correction flow with illustrative inputs, not a released Circle comparison service.
Agentz owns Nexus, the intended boundary for scoped connections and consent.
What the evidence saysExisting Connect repositories and consent UI form source candidates for Nexus connection work.
Still to proveA renamed ownership boundary does not prove independently admitted Nexus grants or cross-product consent.
LIQUID owns wallet and balance work; a wallet screen or repository does not establish custody.
What the evidence saysWallet repositories and balance/backup implementations exist in the company app source.
Still to proveSource presence does not establish custody, balances, key recovery or operating settlement.
MurMur is the proposed home for a personal AI family office and resource mandates.
What the evidence saysThe owner assigns personal resource and mandate work to MurMur; CP-14 is a historical shadow-office proposal.
Still to proveNo connected family-office service or delegated operating mandate is evidenced.
What you can explore today
Explore the design, try fictional interactions, and install this public website for convenient reading. Signing up, sending messages and saving personal notes are not connected here.
Portable identity, meaningful sharing and purpose-linked memory are the direction. Encryption, expiration, recovery and permission enforcement need completion and verification—not just a convincing preview.
Wallet, payment and identity-check work remains subject to its own custody, recovery, eligibility and release evidence. A personal interface does not establish a bank account or verified identity. The same explicit account context and permissions apply when entering a market or operating infrastructure.
Understand your context.
Choose what you share and retain.
Direct the work you want to do.
Context: Me · Individuals.