Identity and recovery
Personal sign-in, account context and recovery. Organisational access adds roles and permissions; wallet backup is a separate recovery problem.
Explore identity and recoveryReturn to Me · Your life, on your terms Me · The individual Your identity, relationships, knowledge and personal capabilities. Discover, participate and care for the products and services you choose. Your own identity, relationships, work and choices. Acting for an organisation or operating an agent requires an explicit permission or mandate. Explore the design. Account features are in development. Existing app foundations These are uses of shared capabilities. Me follows the individual; We follows the organisation’s value chain; They follows the product and its supply chain. A passive product can have a twin without an agent. Share chosen profile details, links and payment instructions. A business has its own profile. A QR scan or public payment address does not establish identity, consent or settlement. Find people, follow sources, publish and connect. Organisation participation uses its own account context. Relationships do not automatically reveal private records. Agentz owns conversation and assistance; APU organises the stored outline. Personal notes and tasks exist in source. That does not establish a shared business task workspace or an autonomous product agent. Me joins, books and attends. We creates events, offers capacity and manages bookings. Capacity, admission, cancellation, payment and acceptance keep separate records. The app source includes an event QR ticket view. A ticket view alone does not establish admission. Nora’s fictional workshop story illustrates participation; it does not book an event or issue a ticket. Inspect the ticket interface. Manage company context, administrators, responsibilities and scheduled obligations. Membership, verification and approval are distinct; a payroll screen does not prove a completed transfer. We authors products and manages variants, stock and offers. They follows the product, its components, individual units and service history. Me compares and uses an owned unit. Markets explains the commercial terms; the physical-market order exercise is a simulation. OFN owns the independent wallet and economic-receipt standard. Personal, company and permitted product-related records remain distinct. Display currency preferences are not currency issuance; interfaces are not proof of live transfers. The app source includes a booking payment-schedule chooser. A schedule does not establish an executed transfer. Inspect the booking interface. LIQUID explains eligible exchange. Legacy trading, Carbon demo and gold presentation code retain their own qualification; their presence does not make every mode an available financial service. Document, passport and face-verification interfaces support account evidence. They do not prove accepted verification, legal registration or biometric payment acceptance. Personal and organisational use needs clear safety and reporting paths. A policy page or report intake is not proof of enforcement, review or appeal. Help, onboarding and supported platforms serve the whole experience. Tips means educational help, not financial tipping. Retained advertising code needs a disposition, not a promise that advertising is live. The reviewed Flutter source contains 42 feature directories at revision Inspect the pinned Flutter source The seven products contribute across all three views. APU organises the outline and stored records; Agentz provides conversation and contextual assistance. OFN remains an independent wallet and receipt standard. Markets brings the participants, offers and commitments together.Individuals.
The tools in this perspective.
Your profile and OpenQR
Relationships, publishing and discovery
Conversation, notes and tasks
Events and bookings
Business accounts, teams and payroll
Products, configurations and individual units
Wallet views and economic records
Exchange and financial studies
Identity evidence
Safety, reporting and privacy
Onboarding, help and platform support
Source inventory and limits
bb34f4c54733. Source presence is not a released or accepted journey. Product autonomy, end-to-end manufacturing and connected service still need qualification.login, register, reset_password, user_additional_info, keys_vaultapp_user, information_management, open_qr, qr_scanner, profile_visitnetwork_user, nostr, searchai_chat, chat, rag_chat, chat_tasksevents, bookingbusiness, kyb, payrollproducts, servitization, marketplacewallet, receipts, currencyexchange, strategies, trade, carbon_demo, augkyc, passport, face_scanchild_safety, safetytips, walk_through, web, advertisement
Individuals · Me
Your personal place in an open Marketsphere.
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.
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.
Mission
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 organises the stored outline; Agentz coordinates conversation and permitted work; Cortex retains memory and Nexus scopes disclosure. You can develop your purposes progressively, beginning with an ordinary conversation.
Objectives
What Me is designed to make possible
The intended personal experience supports the life you choose to build.
Direct my life
Express and revise purposes, priorities, constraints, available time and next actions.
How this outcome would be evaluated
Contribution measures only. Each retains its declared eligible population and limits; the wider objective is not established by a successful record or review.
APU. Organise personal notes, sources and tasks in an infinite nested outline. Keep stored records distinct from the conversation that helped create them.
- Outline structure fidelity
- Permitted record retrieval
- Revision and undo fidelity
- Portable record export
Evaluation role: APU evaluation owner · Unappointed.
MurMur. Relate financial choices to personal goals, horizons, obligations, liquidity needs and protected reserves.
- Mandate fidelity
Evaluation role: MurMur mandate-review owner · Unappointed.
Targets: Unset. Observations: Not recorded. Product definitions below retain their own populations; website tests do not measure customer outcomes.
Understand what matters
Choose sources, inspect why information appeared, replace ranking methods, compare evidence and revise beliefs.
How this outcome would be evaluated
Contribution measures only. Each retains its declared eligible population and limits; the wider objective is not established by a successful record or review.
Circle. Preserve the sources, dates, uncertainty and corrections behind personal decisions.
- Traceable claims
- Correction propagation time
Evaluation role: Circle evidence owner · Unappointed.
RealityFutures. Compare uncertain choices concerning time, work, resources and opportunities.
- Binary forecast Brier score
- Continuous forecast mean absolute error
- Resolution coverage
Evaluation role: RealityFutures evaluation owner · Unappointed.
Targets: Unset. Observations: Not recorded. Product definitions below retain their own populations; website tests do not measure customer outcomes.
Cultivate my network
Maintain uplinks, connections and downlinks; communicate, collaborate, discover opportunities and contribute through the relationship context you permit.
How this outcome would be evaluated
Contribution measures only. Each retains its declared eligible population and limits; the wider objective is not established by a successful record or review. Scope fidelity does not measure trust or relationship value; any relationship study needs separate consent, questions and evaluation criteria.
Agentz. Provide conversation and contextual assistance; maintain the case, coordinate specialists and retain accepted Cortex memory within purpose-limited context.
- Permitted continuity
- Actual scope violations
Evaluation role: Agentz evaluation owner · Unappointed.
Additional outcome definition
Reviewed relationship disclosures preserving the declared parties, purpose, grant and expiry divided by all eligible disclosures; report blocked and actual excess disclosures separately. This evaluates scope, not trust or relationship value.
A predeclared dated evaluation batch, with sample, versions, criteria and consent recorded before review. Evidence: Pinned original and successor records, effective permissions, declared task criteria and independent outcome review.
Relationship-context evaluator · Unappointed. Proposed evaluation definition; collection not connected.
Targets: Unset. Observations: Not recorded. Product definitions below retain their own populations; website tests do not measure customer outcomes.
Exercise economic agency
Understand currency, capital positions, reserves, rights and obligations. Compare offers and use appropriate order books and contracts under the applicable authority.
How this outcome would be evaluated
Contribution measures only. Each retains its declared eligible population and limits; the wider objective is not established by a successful record or review.
LIQUID. Compare exact offers, use eligible orders and payments, and reconcile authorised effects.
- Reconciliation coverage
- Duplicate economic effects
Evaluation role: LIQUID reconciliation owner · Unappointed.
MurMur. Relate financial choices to personal goals, horizons, obligations, liquidity needs and protected reserves.
- Mandate fidelity
- Capital decision comprehension
Evaluation role: MurMur mandate-review owner · Unappointed.
Targets: Unset. Observations: Not recorded. Product definitions below retain their own populations; website tests do not measure customer outcomes.
Turn intentions into outcomes
Learn, work, obtain help, organise activities, offer capabilities and exchange value. Delivery, acceptance, payment and a fulfilled need each require their own evidence.
How this outcome would be evaluated
Contribution measures only. Each retains its declared eligible population and limits; the wider objective is not established by a successful record or review.
Cortex. Preserve sources, revisions, dependencies and unknowns across the individual Replicator Stack.
- Permitted retrieval fidelity
- Source traceability
- Revision lineage fidelity
- Proposal-state fidelity
Evaluation role: Cortex record-evaluation owner · Unappointed.
Agentz. Provide conversation and contextual assistance; maintain the case, coordinate specialists and retain accepted Cortex memory within purpose-limited context.
- Actual scope violations
- Blocked out-of-scope attempts
Evaluation role: Agentz evaluation owner · Unappointed.
Targets: Unset. Observations: Not recorded. Product definitions below retain their own populations; website tests do not measure customer outcomes.
Accumulate useful capability
Retain chosen knowledge, sources, commitments, learning and attributed milestones so experience can improve future choices.
How this outcome would be evaluated
Contribution measures only. Each retains its declared eligible population and limits; the wider objective is not established by a successful record or review.
APU. Organise personal notes, sources and tasks in an infinite nested outline. Keep stored records distinct from the conversation that helped create them.
- Outline structure fidelity
- Permitted record retrieval
- Revision and undo fidelity
- Portable record export
Evaluation role: APU evaluation owner · Unappointed.
Circle. Preserve the sources, dates, uncertainty and corrections behind personal decisions.
- Correction propagation time
Evaluation role: Circle evidence owner · Unappointed.
Agentz. Provide conversation and contextual assistance; maintain the case, coordinate specialists and retain accepted Cortex memory within purpose-limited context.
- Permitted continuity
Evaluation role: Agentz evaluation owner · Unappointed.
Additional outcome definition
Independently evaluated repeat tasks under a predeclared comparable protocol, keeping baseline, assistance, learning and confounds explicit; no target or claimed improvement before observation. Before collection, declare the task class, eligible population, outcome variable, scoring rule, comparator and aggregation. These protocol decisions remain open.
A predeclared dated evaluation batch, with sample, versions, criteria and consent recorded before review. Evidence: Pinned original and successor records, effective permissions, declared task criteria and independent outcome review.
Independent learning-outcome evaluator · Unappointed. Proposed evaluation definition; collection not connected.
Targets: Unset. Observations: Not recorded. Product definitions below retain their own populations; website tests do not measure customer outcomes.
Preserve continuity and choice
Continue across qualified interfaces, agents and providers. Change grants, recover under an implemented policy and leave a service with available permitted records.
How this outcome would be evaluated
Contribution measures only. Each retains its declared eligible population and limits; the wider objective is not established by a successful record or review.
Agentz. Provide conversation and contextual assistance; maintain the case, coordinate specialists and retain accepted Cortex memory within purpose-limited context.
- Permitted continuity
- Actual scope violations
- Blocked out-of-scope attempts
Evaluation role: Agentz evaluation owner · Unappointed.
Additional outcome definition
Due permitted recovery/replacement/transfer/retirement exercises meeting every pinned required criterion divided by all due exercises; retain failures, missing keys, obligations and unresolved records. Different transition classes remain separate.
A predeclared dated evaluation batch, with sample, versions, criteria and consent recorded before review. Evidence: Pinned original and successor records, effective permissions, declared task criteria and independent outcome review.
Independent transition-outcome evaluator · Unappointed. Proposed evaluation definition; collection not connected.
Targets: Unset. Observations: Not recorded. Product definitions below retain their own populations; website tests do not measure customer outcomes.
A personal case · fictional local example
Your network is your net worth.
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
A milestone leads to an introduction.
- Published source
- Workshop induction · revision 1 · Tuesday, 18:00.
- Why it appeared
- Nora chose the workshop’s public updates and a chronological feed.
- Review
- Current source still needs review.
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
An account opens as a conversation.
Sam
Fictional workshop participant · published profile
Robotics, repair and helping newcomers. Public posts and milestones provide context; private contacts have their own permissions.
Published milestone
Workshop induction announced. The schedule is revision 1; review the source before relying on it.
Published post
“We welcome people who want to learn and help maintain the workshop.”
The conversation has not opened. This example first waits for the introduction.
Private contact sharing
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
Keep useful knowledge deliberately.
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
Learn, contribute or explore work.
- Spending currency
- 250 fictional demo units; this page holds no funds.
- Protected reserve
- 150 of those units remain outside this learning budget.
- Capital and rights
- A capital position has separate ownership, risk and liquidity terms. It is not automatically a spending balance.
Nora has not chosen a next activity.
Outcome controls illustrate an attributed report. A choice, report, independently accepted result and payment are different states.
Try interruptions, key rotation and recovery
Keep availability and key control separate.
- Transport
- Connected in this example.
- Provider
- Example provider 1 · available.
- Key control
- Example key version 1 · available.
- Recovery arrangement
- None. It cannot be arranged after this key is lost.
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.
Rotate an available key
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.
Arrange recovery before a key is lost
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.
When a personal connection becomes shared work
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
Seven products. The parts your purpose needs.
Each product can help in a different way. These examples use Nora’s fictional workshop journey; connected availability varies.
Rosetta agent row · Teleology
APU
Organise the question and what matters. Nora could organise her robotics question, workshop notes and sources in an outline. Organise personal notes, sources and tasks in an infinite nested outline. Keep stored records distinct from the conversation that helped create them. Proposed KPI. Record structure, permitted retrieval, revision/undo and export fidelity in declared audience-specific samples. Decision-review comprehension belongs to Agentz and is measured separately. Collection requires an appointed owner, permitted records and an agreed protocol. Definitions do not start telemetry or appoint anyone. Specialist Agents. Information organiser; Retrieval designer; Record integrity reviewer. 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. The dated inventory allocated conversation to the APU interface; its evidence IDs are retained for traceability. Current responsibility is APU’s nested outline and stored records, while Agentz owns conversation and contextual assistance. These source contracts do not establish a released integration. Inspect the dated Flutter inventory and its limits. Repository access may be required. Future integration. APU owner: qualify outline navigation, stored-record permissions, search, revisions and recovery. Qualify conversational handoff separately with Agentz; package integration remains deferred.See APU’s example, measures and specialist Agents
How this would be measured
Outline structure fidelity
Permitted record retrieval
Revision and undo fidelity
Portable record export
Explore APU’s AgentsSources and integration limits
Rosetta agent row · Epistemology
Circle
Compare sources and notice a change. Nora could compare workshop notices and see that the induction date changed. 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.See Circle’s example, measures and specialist Agents
How this would be measured
Traceable claims
Correction propagation time
Explore Circle’s AgentsSources and integration limits
Rosetta agent row · Methodology
RealityFutures
Explore choices and their uncertainties. Nora could compare assumptions behind learning independently, attending a workshop or exploring paid work. 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.See RealityFutures’s example, measures and specialist Agents
How this would be measured
Binary forecast Brier score
Continuous forecast mean absolute error
Resolution coverage
Explore RealityFutures’s AgentsSources and integration limits
Rosetta agent row · Axiology
Agentz
Prepare next steps using context you choose. With Nora’s selected workshop note, an assistant could help her prepare questions for the organiser. Provide conversation and contextual assistance; maintain the case, coordinate specialists and retain accepted Cortex memory within purpose-limited 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. Agentz uses Cortex memory and shared Nexus disclosure permissions; 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.See Agentz’s example, measures and specialist Agents
How this would be measured
Permitted continuity
Actual scope violations
Blocked out-of-scope attempts
Decision comprehension
Time to resume a permitted case
Explore Agentz’s AgentsSources and integration limits
Rosetta agent row · Cosmology
Cortex
Keep evidence and revisions together. Nora could keep the source, revisions and terms of a proposed workshop task together for review. Preserve sources, revisions, dependencies and unknowns across the individual Replicator Stack. Proposed KPI. Permitted retrieval fidelity, source traceability, revision lineage fidelity and proposal-state fidelity in a declared sample of personal projects and dependencies; include refusals, conflicts, stale records and missing sources. Targets remain unset. Collection requires an appointed owner, permitted records and an agreed protocol. Definitions do not start telemetry or appoint anyone. Specialist Agents. Memory steward; Evidence reviewer. Skills and responsibilities. Keep assertions and proposals distinct from accepted records. Nexus scopes disclosure; later assessment or insurance requires separate qualification. 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.See Cortex’s example, measures and specialist Agents
How this would be measured
Permitted retrieval fidelity
Source traceability
Revision lineage fidelity
Proposal-state fidelity
Explore Cortex’s AgentsSources and integration limits
Rosetta agent row · Ontology
LIQUID
Compare offers and their terms. If Nora needs a part, she could compare offers and their price and delivery terms. 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.See LIQUID’s example, measures and specialist Agents
How this would be measured
Reconciliation coverage
Duplicate economic effects
Explore LIQUID’s AgentsSources and integration limits
Rosetta agent row · Theology
MurMur
Consider choices alongside your goals. Nora could consider a course’s cost alongside her goals, obligations and protected reserve. 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.See MurMur’s example, measures and specialist Agents
How this would be measured
Mandate fidelity
Capital decision comprehension
Explore MurMur’s AgentsSources 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 historical 21 October participant proposal. Repository access may be required. The current objectives above incorporate the 26 October perspective clarification: individuals, organisations, and products with or without an agent. Read the current relationship between the perspectives.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
A little closer to your everyday.
Try the intended interactions. This is a local illustration, not a working account or service.
One-to-one messages
One to one · example conversation
You & Alex
A little time, just for you two.
You · example message
Shall we meet
by the garden?
A fleeting discoveryTimed media · five-second example
Be present.
Leave less behind.
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
Talk. Publish.
Choose what reaches you.
Direct conversations
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 messagesBroadcasts & milestones
Publish to your chosen audience. A post, an attributed milestone and a direct message keep their own visibility and retention rules.
Preview publishingYour feed, your rules
The 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
Direct the work.
Review what carries forward.
One continuing workspace
Move from a question to a bounded task, inspect the proposed work and review its result. Agentz owns conversation and proposed work. Cortex holds source-linked memory; Nexus scopes its disclosure across Skyzai. APU organises stored records; Agentz provides contextual conversation.
A task receives the context and budget you permit. A completed response does not silently become accepted memory or permission for the next action.
A clear handoff when you need more
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
One identity.
Explicit contexts.
Carry a recognisable presence between compatible tools. Choose which account you are acting for.
Explore the exampleClose the example
A presence of your own
One identity. Explicit contexts.
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
You
One identity. Different contexts.
Your own space
Plans, people, things to learn.
A place to decide what belongs in your life.
What “your keys” should mean
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.
Closeness, with boundaries
Share a detail.
Keep the boundary.
A friend may need your number. A supplier may need a delivery address. Neither needs your whole history.
Explore the exampleClose the example
Closeness, with boundaries
Share a detail. Keep the boundary.
A friend may need your number. A supplier may need a delivery address. Neither needs your whole history.
Explore the exampleClose the exampleA design you can explore
Nexus is the shared boundary for purpose-scoped context disclosure, expiry and revocation across Skyzai. The view you grant should remain understandable to you. A connection is not consent to retain every conversation or use your context for another purpose.
Illustration of the idea, not an app screenshot. The example uses fictional details.
Explore Nexus permissionsTry the permission design · fictional details
A detail, not your whole life.
For this example, Alex, Connections and Uplinks are separate audiences. A relationship group is not automatic permission to see your profile.
In the app design, permissions would also depend on actual membership and purpose. Changing a grant limits future access; it cannot recall copies already received.
Thoughts with a direction
Keep what matters.
Know what was kept.
Conversations, published milestones and accepted memory have different lifecycles.
Explore the exampleClose the example
Thoughts with a direction
Keep what matters. Know what was kept.
Conversations, published milestones and accepted memory have different lifecycles.
Explore the exampleClose the exampleA design you can explore
APU organises stored notes and source records. Agentz provides conversation and contextual assistance. Agentz coordinates work in the Cloud Computer and uses Cortex memory. Cortex preserves sources, revisions and explicit retention under shared Nexus permissions. 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 Cortex memoryAgentz conversation to an APU note · predefined example
Walk with Alex this weekend
No example note kept yet.
Conversation · this plan
“Let’s meet at the garden’s north gate on Sunday. We still need to choose a time.”
When meaning is unclear, Agentz should ask before suggesting a note for the APU outline. 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
Take the need to Markets.
Keep your boundaries.
A brief you can inspect
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 record of the handoff
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 ·
The products behind a personal journey
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.botBounded local proof
Find the source
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.
- CircleBounded local proof
Keep corrections visible
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.
- AgentzSource observed
Share for a purpose
Nexus is the shared context-permissions and disclosure layer; existing technical adapters remain separately qualified.
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.
- LIQUIDSource observed
Inspect transaction records
This retained LIQUID wallet-integration record is implementation evidence, not custody. OFN owns the independent wallet and economic-receipt standard; LIQUID handles offers, orders and settlement connections.
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.
- MurMurProposed
Plan personal stewardship
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
A clear direction.
An honest starting point.
This website
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.
The app being built
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.
Also on the roadmap: payments & identity checks
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.
Stay connected. Keep your choices.
Understand your context.
Choose what you share and retain.
Direct the work you want to do.