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 We · The organisation We · The shared organisation Start with a business profile people can find and the information they need. Explore how an organisation can then make, deliver, support and improve its offerings. A shared organisation or DAV, presented as a DAC when registered as a legal person in a national jurisdiction. Registration, membership and authority require their own evidence; this preview forms no organisation. OpenQR business pilot · proposed At a trade fair, a visitor could scan an exhibitor’s OpenQR code to open the public profile the business has chosen to share: its name, logo, contacts and links, with chosen locations on a globe. The proposed pilot would use APU to organise permitted company information and Agentz to help answer questions in supported languages, with contact details and a named person for human follow-up. Profile QR and scanning components exist in Flutter source. The hosted scan-to-assistance journey, guest access, human handoff, location display and language support still need qualification. Later, approved product knowledge can support exact offers and continuing care in Skyzai Markets. This retained teaching case uses its original cleaning-robot artwork. Its records are separate from the industrial workshop and Markets examples. The maker’s perspective A household wants a cleaner home. A company brings together the people, parts, knowledge and service that make its cleaning robot useful. Follow a fictional maker from its first configuration to delivery, repair and improvement. The intended connected experience combines existing app features with integrations still to qualify. 01 · Organise The company wants to make home care easier. Its designers, suppliers and service partners need a shared understanding of what they are promising. Start with an organisation profile. Set responsibilities, bring the team together and keep customer work connected to the product it concerns. Working together. APU helps clarify the brief. Agentz coordinates permitted work, Cortex records and scoped connections. An invited colleague can contribute without being allowed to buy parts or accept a customer contract. The existing company selector enters an existing business context. That account switch does not establish legal registration, ownership or signing authority; permissions remain separately enforced. Source-backed feature explanation. A rendered app capture is not qualified in this website pass; the scene above is a concept illustration. Business profiles, links, QR, products, posts, events and booking approvals support shared work in the app source. Personal APU notes and tasks remain bound to the individual; a shared company task workspace is not established. Payroll schedules are feature-gated, and workforce code does not establish an accessible HR workflow. Events separate registration and admission from ticket checkout. Business creation, legal registration, membership, account access and signing authority require their own evidence. 02 · Define A customer chooses a cleaning robot with a manipulator arm. The maker must know which base, arm, cleaning tools and service terms belong to that configuration. Build a product record with variants, specifications, media and supporting documents. The intended virtual twin connects those records to components, revisions and the individual robot. Working together. Circle compares attributed evidence. Cortex keeps source-linked product knowledge; Agentz assists within permitted context. LIQUID makes the offer and its rights explicit. An attractive model cannot prove an actuator fits. Unknown dimensions, revisions or safety evidence must remain unresolved. The review component presents product category, title, stock, description and attributes. Product authoring is limited by source to a non-web platform and the matching business account. Web purchase controls vary by account; buyer access still needs qualification. A 3D file is not evidence of qualified AR, VR or a complete engineering twin. Source-backed feature explanation. A rendered app capture is not qualified in this website pass; the scene above is a concept illustration. 03 · Source and make The maker needs qualified components and a realistic production plan, rather than another disconnected supplier spreadsheet. Connect suppliers, stock, locations and tasks to the accepted configuration. Reserve existing stock when it matches. For a made-to-order robot, agree the configuration, price, lead time and payment before production begins. Working together. Agentz coordinates assignments. Circle preserves supplier evidence. RealityFutures tests capacity and demand assumptions. Unavailable stock or an incompatible component pauses the plan. A supplier’s new statement does not silently revise an accepted customer promise. This is an existing catalogue tile, not the inventory-management screen. Stock and location code exists separately; automatic supplier competition and just-in-time factory dispatch remain integration work. Source-backed feature explanation. A rendered app capture is not qualified in this website pass; the scene above is a concept illustration. 04 · Reach customers A household customer discovers what the robot can do through a demonstration, a recommendation or product content in a feed. Permitted twin assets and sourced specifications can support AI-generated content. People and agents can recommend the product using disclosed affiliate links, carrying attribution into an eligible sale. Working together. Circle checks the account and its sources. Agentz coordinates permitted content work. Nudge connects marketing to the commerce records. A sign-up alone earns nothing. Repeat-purchase and upstream rewards must share the agreed funded pool; campaign rules and reversals remain explicit. 05 · Sell and fulfil The household wants its chosen robot, at understandable total cost, with a credible delivery date and a responsible provider. The intended order book matches eligible bids and maker offers for exact terms. Existing stock can ship from the most suitable eligible location, considering configuration, cost and delivery time—not distance alone. Working together. LIQUID owns the exchange and commercial records. Agentz coordinates the work. Cortex retains responsibilities, evidence and remedy history; Nexus scopes access. A failed delivery opens recovery under the accepted terms. An order match or dispatch scan is not proof that the customer received and accepted the robot. The booking-history source presents records, not a live order-book execution. Existing Flutter marketplace matching is a separately labelled local simulation. Source-backed feature explanation. A rendered app capture is not qualified in this website pass; the scene above is a concept illustration. 06 · Continue the care Months later, the robot detects a possible wrist-actuator fault. Its household owner needs a useful response, not another explanation of which robot they own. Use permitted manuals, configuration and service history to investigate. The robot stops the affected action, checks compatible parts and service availability, then prepares an order or booking within its allowed scope. Working together. Agentz coordinates assistance through permitted Cortex knowledge. Circle supports source correction. Cortex supplies evidence for later assessment and protection; Nexus scopes disclosure; LIQUID supplies the applicable order and payment records. Rejected expenditure, unavailable parts or a disputed repair stays visible. Warranty, insurance, replacement and upgrade apply only when the accepted agreement provides them. The shared-case widget has an isolated local example. Its records are independent of this robot story; it establishes neither a deployed support service nor permission to spend. Source-backed feature explanation. A rendered app capture is not qualified in this website pass; the scene above is a concept illustration. 07 · Account and improve The company needs to understand what it owes, what it delivered and which improvements would make the next robot more useful. Connect orders, service work and economic records without treating them as the same evidence. Review costs, outstanding obligations and recurring faults. Feed accepted corrections into future designs and offers. Working together. OFN explains receipt-driven bookkeeping, accounting and controlling. Circle supports correction; RealityFutures compares scenarios. MurMur can inform an owner’s or investor’s separately permitted capital research. A missing receipt is a reconciliation question. It does not prove that an obligation disappeared. Research is not a guarantee of financing or an authority to move treasury funds. The existing organisation-example account is synthetic and independent of this manufacturer. Displayed balances are not operating results, licensed bank accounts or issued economic receipts. Source-backed feature explanation. A rendered app capture is not qualified in this website pass; the scene above is a concept illustration. The customer chooses how to obtain help at home. The maker remains responsible for its offer. The robot can investigate and prepare work within a bounded permission. A supplier or service partner fulfils its own commitment. This maker story is a concept, not a transaction demonstration. The Me, They and Markets pages retain their own independent local examples. No account, robot order, payment, insurance policy or OFN receipt is created here. An independent local example The existing workshop example retains its own inspection robot, actors, approvals and accounting. It is separate from the cleaning-robot maker story above. 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. An organisation can bring people together around an event, plan capacity and review registrations. Registration, approval and admission are separate steps. This website does not create events or issue tickets. Inspect the event source · Inspect the booking source. The app modules are evidence of source, not a qualified end-to-end service. 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. 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.Build something useful.
Keep its promise.
Make your business
easy to find.Historical household-maker illustration
One robot.
A whole business.Coordinate the teamMake and deliverSupport and improveA team with a shared purpose.
The maker’s intended workflow
When the plan needs to pause
Explore the app feature
Inspect this feature’s pinned Flutter sourceBusiness-account entry
Explore shared workEveryday tools for a shared account
One product everyone can understand.
The maker’s intended workflow
When the plan needs to pause
Explore product twinsExplore the app feature
Inspect this feature’s pinned Flutter sourceProduct review
The right parts. The right configuration.
The maker’s intended workflow
When the plan needs to pause
Compare production and fulfilment routesExplore the app feature
Inspect this feature’s pinned Flutter sourceProduct catalogue component
Let useful product knowledge travel.
The maker’s intended workflow
Explore recommendations and rewardsWhen the plan needs to pause
An exact order. A robot delivered.
The maker’s intended workflow
When the plan needs to pause
Explore orders and deliveryExplore the app feature
Inspect this feature’s pinned Flutter sourceBooking history
The relationship continues after delivery.
The maker’s intended workflow
When the plan needs to pause
Explore continuing serviceExplore the app feature
Inspect this feature’s pinned Flutter sourceShared case workspace
Learn from the whole working life.
The maker’s intended workflow
When the plan needs to pause
Explore wallet views and receiptsExplore the app feature
Inspect this feature’s pinned Flutter sourceInspect the example account dataOrganisation financial example
The same economy.
Different responsibilities.Inside a workshop’s
customer commitment.The tools in this perspective.
Your profile and OpenQR
Relationships, publishing and discovery
Conversation, notes and tasks
Events and bookings
How organisations use events
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
Organisations · We
Turn shared purpose into lasting value.
An organisation combines people, machines, resources and capital into a value chain that can outlast one task. Useful delivery, honoured obligations and renewed capacity are the intended results.
Vision
Organisations can create useful value, honour commitments and renew their shared capabilities while participating through open, replaceable systems.
Mission
Help people and machines turn shared purpose, resources, responsibilities and capital into dependable offerings, accountable exchange and sustainable organisational capability.
We includes ordinary organisations and DAVs. In this model, a DAV is presented as a DAC when its national legal-person registration is evidenced. Governance, membership, ownership, administration and authority for an exact act remain distinct.
Objectives
What We is designed to make possible
The intended organisational experience connects purpose to delivery and continuing capability.
Constitute and govern the shared purpose
Make purpose, participants, rights, responsibilities and decision rules understandable, with actual legal status and acting authority separately evidenced.
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. Record integrity and commitment completeness do not establish governance legitimacy or quality.
APU. Organise permitted organisational records and responsibilities in an outline. Shared business task integration remains separate from the existing personal notes implementation.
- Outline structure fidelity
- Permitted record retrieval
- Revision and undo fidelity
- Portable record export
Evaluation role: APU evaluation owner · Unappointed.
Cortex. Preserve sources, revisions, dependencies and unknowns across the organisation’s primary and supporting value-chain activities.
- Permitted retrieval fidelity
- Source traceability
- Revision lineage fidelity
- Proposal-state fidelity
Evaluation role: Cortex record-evaluation owner · Unappointed.
Targets: Unset. Observations: Not recorded. Product definitions below retain their own populations; website tests do not measure customer outcomes.
Coordinate the value chain
Connect inbound logistics, operations, outbound logistics, marketing and sales, and service. Assign context and responsibility to the work that needs them.
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 organisational conversation and contextual assistance; coordinate bounded assignments and permitted Cortex memory across the value chain.
- Accepted work within scope
- Actual scope violations
- Blocked out-of-scope attempts
Evaluation role: Agentz evaluation owner · Unappointed.
Circle. Keep supplier claims, specifications, customer statements and operational evidence attributable and correctable.
- Traceable claims
- Correction propagation time
Evaluation role: Circle evidence owner · Unappointed.
Targets: Unset. Observations: Not recorded. Product definitions below retain their own populations; website tests do not measure customer outcomes.
Create understandable offerings
Specify the product or service, revision, capacity, condition, pricing, delivery, acceptance and support. Consumable goods and services, durable products, digital outputs and bundles retain their own terms; XaaS describes an arrangement.
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. Offering comprehension needs a declared reader study; source and commitment completeness are supporting checks.
Circle. Keep supplier claims, specifications, customer statements and operational evidence attributable and correctable.
- Traceable claims
Evaluation role: Circle evidence owner · Unappointed.
Cortex. Preserve sources, revisions, dependencies and unknowns across the organisation’s primary and supporting value-chain activities.
- Permitted retrieval fidelity
- Source traceability
- Revision lineage fidelity
- Proposal-state fidelity
Evaluation role: Cortex record-evaluation owner · Unappointed.
Targets: Unset. Observations: Not recorded. Product definitions below retain their own populations; website tests do not measure customer outcomes.
Fulfil and support commitments
Obtain applicable authority before accepting an agreement. Track fulfilment, installation where relevant, inspection, acceptance, payment, cancellation, return and remedies.
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 organisation’s primary and supporting value-chain activities.
- Permitted retrieval fidelity
- Source traceability
- Revision lineage fidelity
- Proposal-state fidelity
Evaluation role: Cortex record-evaluation owner · Unappointed.
LIQUID. Support exact offers, orders, eligible exchange, payment terms and reconciliation.
- Reconciliation coverage
- Duplicate economic effects
Evaluation role: LIQUID reconciliation owner · Unappointed.
Targets: Unset. Observations: Not recorded. Product definitions below retain their own populations; website tests do not measure customer outcomes.
Understand obligations and finance continuity
Reconcile commitments, invoices, usage, payments, refunds, costs and rights. Prepare qualified financing while keeping equity, debt, collateral and currency governed by their actual terms.
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. Support exact offers, orders, eligible exchange, payment terms and reconciliation.
- Reconciliation coverage
- Duplicate economic effects
Evaluation role: LIQUID reconciliation owner · Unappointed.
MurMur. Support separately permitted owner or investor capital research concerning disclosed organisational opportunities and risks.
- 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.
Learn, renew and remain resilient
Preserve permitted operational knowledge, correct future decisions, improve processes, maintain resources and replace compatible workers or providers without losing accountability.
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 organisational conversation and contextual assistance; coordinate bounded assignments and permitted Cortex memory across the value chain.
- Accepted work within scope
Evaluation role: Agentz evaluation owner · Unappointed.
Circle. Keep supplier claims, specifications, customer statements and operational evidence attributable and correctable.
- Correction propagation time
Evaluation role: Circle evidence owner · Unappointed.
MurMur. Support separately permitted owner or investor capital research concerning disclosed organisational opportunities and risks.
- Capital research correction fidelity
Evaluation role: MurMur mandate-review 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.
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.
Contributing product strategies
Seven products. The parts your purpose needs.
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
APU
Organise permitted organisational records and responsibilities in an outline. Shared business task integration remains separate from the existing personal notes implementation. 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. Make the organisational context understandable. Workspace access does not appoint an approver. 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.Proposed 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
Keep supplier claims, specifications, customer statements and operational evidence attributable and correctable. Proposed KPI. Material claims with an identified source, revision and freshness assessment divided by sampled material claims; accepted-correction propagation into affected new comparisons. 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. Preserve sources, uncertainty and private-source access boundaries. 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
Explore Circle’s AgentsSources and integration limits
Rosetta agent row · Methodology
RealityFutures
Compare demand, capacity, repair, replacement, leasing and service alternatives. Proposed KPI. Forecast performance by question class against its declared baseline and horizon. Preserve unresolved assumptions and abstentions; keep incompatible units in separate measures. 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. Compare scenarios with explicit assumptions. A scenario preference does not authorise a commitment. 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
Explore RealityFutures’s AgentsSources and integration limits
Rosetta agent row · Axiology
Agentz
Provide organisational conversation and contextual assistance; coordinate bounded assignments and permitted Cortex memory across the value chain. Proposed KPI. Eligible due assignments with independently accepted delivery completed within exact grants divided by eligible due assignments; review coverage, due-but-undelivered and cancelled work, scope violations, stale-context incidents and continuity failures reported separately. 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 work and permitted operational knowledge. A task grant and a purchasing mandate remain distinct. 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.Proposed measures and specialist Agents
How this would be measured
Accepted work within scope
Actual scope violations
Blocked out-of-scope attempts
Organisational decision comprehension
Explore Agentz’s AgentsSources and integration limits
Rosetta agent row · Cosmology
Cortex
Preserve sources, revisions, dependencies and unknowns across the organisation’s primary and supporting value-chain activities. Proposed KPI. Permitted retrieval fidelity, source traceability, revision lineage fidelity and proposal-state fidelity in a declared sample of organisational work and responsibilities; 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.Proposed 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
Support exact offers, orders, eligible exchange, payment terms and reconciliation. Proposed KPI. Reviewed transactions due for reconciliation whose applicable commitment, invoice or trade confirmation, confirmed effect or payment and refund or reversal records match divided by reviewed transactions due for reconciliation; unmatched and duplicate effects 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. Support exchange and reconcile its records. Physical orders and financial instruments retain different contracts. 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
Explore LIQUID’s AgentsSources and integration limits
Rosetta agent row · Theology
MurMur
Support separately permitted owner or investor capital research concerning disclosed organisational opportunities and risks. Proposed KPI. Mandate fidelity among reviewed recommendations, preserving objectives, horizons, liquidity needs, reserves and constraints; correction fidelity reported separately. 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. Carry permitted owner or investor research. General corporate treasury retains its own responsibility; MurMur remains a personal capital-office product. 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 research correction fidelity
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. The fictional workshop case separates accepted repair, matching service qualification, exact customer agreement, work, delivery, acceptance and accounting. Purpose-bound context grants and historical copies remain separate from authority. Inspect the separate local example. It uses page-local state and resets on reload; it is separate from the product commissioning-analysis story. The actual app/service must separately qualify identity, effective grants, work provenance, retained records, fulfilment and accounting. This page-local case issues no real agreement, payment or receipt. 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
From a product to a relationship.
A fictional product demonstrates how parts, service and offers could connect. It creates no working account, offer or agreement.
Product & parts
Interactive concept · fictional hardware
One actuator. A world of parts.
Explore a linear actuator driven by a brushless motor, separate its modules, then select a part.
Linear actuator LA-02 / version 2Assembled schematic
Illustrative geometry—not manufacturer CAD, a fit approval or verified specifications.
Selected module · demonstration
Brushless motor
BLM-28-R1 / version 1
Converts controlled electrical input into rotary motion.
Compatibility: not verified
Winding, KV, voltage and current limits, cooling, mounting and shaft interface need version-specific evidence.
Choose a maker and preview the request, or see how service would keep the selected module as context.
Local demonstration only. Every maker, module and part code above is fictional. No catalogue, stock, fit approval, live AI, order or payment is connected. A production twin needs validated product data—not an AI-generated guess at internal parts.
Create and deliver
The value chain
behind the offer.
Coordinate shared work, deliver useful offerings, understand what happened and prepare to finance growth. Porter’s primary activities provide the operating map: inbound logistics, operations, outbound logistics, marketing and sales, and service. A particular transaction uses the activities it needs.
Organise the work
Connect suppliers, teams, events, product information and responsibilities around a shared objective. Policy-controlled accounts would support the organisation’s actual rules: a competent sole decision-maker, multiple approvers or explicitly delegated limits. Access to the workspace does not itself grant signing power.
Keep the source with the record
Products and services, their twins, offers, agreements, fulfilment and payments each keep a distinct identity and lifecycle. A twin represents an asset or service; it does not itself establish ownership. Shared records help the team reconcile commitments and costs without rebuilding the story at every handoff.
Discover and use
A completed service.
Continuing access.
A product to own.
Consumable services, XaaS and durable products give customers familiar ways to understand an offer. The underlying model keeps what is supplied, what rights the customer receives and how it is measured and paid separately configurable.
Consumable service
One defined unit of work: an industrial inspection or inference job, with explicit scope and acceptance.
XaaS
Continuing access, capacity or an outcome commitment. The same machine may support many service arrangements.
Durable product
An enduring asset supplied under defined ownership, delivery, warranty and subsequent service terms.
Consumable goods, digital outputs and bundles remain supported. XaaS describes an arrangement, so a durable robot can also be supplied through Robotics-as-a-Service.
Inspect the offer spectrumOne commercial journey
Exact terms.
Visible responsibility.
Compare what is actually offered
The buyer needs a responsible provider, exact item or service scope, price, availability, eligibility and support terms. LIQUID is intended to support offers, payment terms, exchange and settlement; OFN’s independent receipt and accounting standards describe economic effects. The We perspective connects these to shared work.
An agent may prepare a comparison. Account access or a recommendation does not authorise spending. Physical-product orders and financial instruments can share compatible infrastructure while retaining different contracts: delivery and warranty terms for an actuator, ownership rights and settlement conditions for equity.
Follow delivery and continuing service
Keep the agreement, execution, delivery, acceptance, payment and any dispute distinct. Maintenance, upgrades, warranty and support follow the offer’s actual terms. Circle, ReFu, Agentz and Cortex contribute when their responsibilities are needed.
Ordinary evidence records and OFN economic receipts have different qualification and issuance requirements.
Planned storefront checkout: NFC and palm payment
A physical shop could connect the same product offer to NFC tap-to-pay or an opt-in palm-payment service, where a qualified payment provider and compatible terminal support it. A customer would see the amount and approve payment; another supported payment method would remain available.
An NFC tag that opens a product’s twin is a separate interaction from taking a payment. A specialist provider would manage biometric enrolment and matching; raw palm data would not enter the product’s knowledge base or assistant context. Provider support, consent, security, payment completion and refunds remain to qualify. This website does not capture biometrics or take payments.
Own and finance
Shared assets.
Explicit rights.
Organisations and governance
A DAV is the shared venture model. When registered as a legal person in a national jurisdiction, it is presented as a DAC. That registration and the governing documents must be evidenced; using the website or adding a DAC label does not create legal personhood. Membership, account administration, beneficial ownership and signing power remain separate.
Opening a workspace does not form an entity, issue equity or create a creditor’s claim. Investment and debt need named issuers, defined rights, terms and the applicable admission requirements.
Explore ownership and obligationsBroader origination is directed to LIQUID; specified Aureus programmes remain separate
The design assigns broader origination to LIQUID. Aureus retains specified gold, credit, land/SPV and Swiss AG programmes. Earlier Dragonfly artwork material remains a historical programme reference; it does not establish current origination ownership, an available investment or an operational transfer.
We explains how participants coordinate and enter relevant markets; it does not take over the originator’s issuance or legal responsibilities.
View the historical Aureus art programmeHistorical external programme. This reference is not an available investment or evidence of a completed artwork project.
SoResFi · organisational finance and connected exchange
Rights in We. Exchange through LIQUID.
We explains the organisation’s issuance, ownership, investor rights, bonds and asset financing. The proposed DAV model’s 100-unit equity denominator and optional debt instruments still need defined rights, precision, issuer terms and admission evidence. A currency balance does not itself establish project equity.
The LIQUID DEX is the intended application for eligible equity and bond exchange, including orders, liquidity and settlement. Issuance does not automatically make an instrument tradable: issuer restrictions, investor eligibility, custody, supported protocols and operating exchange admission must be satisfied. Liquidity and execution are not guaranteed.
Shared SPECTRE infrastructure and SKY/ZAI protocol mechanics support all three participant groups. They explains machine participation in that shared foundation. A DAC may operate agents, rent infrastructure or operate a node under the relevant permissions. Those roles do not replace its legal or investor obligations.
Design explanation. No company, equity, bond, loan, trading venue or financial service is created or offered by this preview.
Membership, access and authority are separate responsibilities.
Clear roles.
Explicit commitments.
Nexus provides shared, purpose-scoped disclosure permissions. Participants receive the context their role needs; approval of an exact commercial or organisational act requires the relevant recognised authority. An assistant can prepare a proposal without becoming the signer.
Explore Nexus permissionsShared Nexus permissions · intended design
Receive the context the role needs.
A supplier, customer, colleague or machine receives an explicit view for an explicit purpose. A company’s role permissions do not expose the participant’s unrelated personal notes or contacts.
A twin, offer, agreement and fulfilment record each tell a different part of the story.
Follow the work.
Keep its sources.
Cortex retains permitted context through shared Nexus permissions; Circle keeps attribution and corrections. LIQUID is intended to support payment terms, exchange and settlement; OFN’s independent receipt and accounting standards describe economic effects. Delivery, customer acceptance and settlement remain separate states. Organisational governance, issuance, investor rights and asset financing belong in We, with the legal person and national jurisdiction stated explicitly. LIQUID owns the DEX, orders, liquidity and settlement application; SPECTRE explains the shared protocol and monetary mechanics.
Explore product and service recordsShared decision · fictional preview
Buy a robot or subscribe to the outcome?
assistant proposal
An assistant compares purchasing an industrial inspection robot with a continuing inspection service. Price, operating responsibility and support terms are visible; no offer has been accepted.
Local demonstration only. Acting-account access, permission to review and authority to bind a commitment are separate.
Capability evidence ·
The products behind shared work
We is the shared organisation, including the DAV venture model and its DAC presentation when registered as a legal person in a national jurisdiction. Participation or a workspace does not create that legal status or authority. These selected capabilities retain their product owners and separate delivery, payment and acceptance states.
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
Order the material
APU has a locally tested ordering contract for explicit criteria and ties.
What the evidence saysA standalone pure Dart ordering package and two fixture hosts demonstrate explicit criteria and tie handling.
Still to proveSynthetic reuse is not production extraction, independent-team adoption or the full APU interface.
- CircleBounded local proof
Review a correction
Circle keeps attribution and disagreement attached to a shared claim.
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.
- ReFuBounded local proof
Inspect an outlook
ReFu can surface an attributed market observation; the outcome still needs resolution.
What the evidence saysA local browser read a real public ReFu market response and retained its status and attribution.
Still to proveA price/status observation is not a verified forecast, tradable market, current outcome or service acceptance.
- AgentzBounded local proof
Keep bounded context
The retained Agentz carrier has local tests for Cortex source-linked text lifecycle work; current product presentation does not move that source.
What the evidence saysA dependency-free Dart package and two synthetic Flutter hosts exercise deterministic routing and text lifecycle.
Still to proveNo real model, provider quota, production extraction or independent-team adoption is proven.
- LIQUIDSource observed
Specify an offer
LIQUID contains catalog, booking and order source for a future commerce journey.
What the evidence saysCurrent Flutter source includes product listings, booking repositories and marketplace order-book builders.
Still to proveCode inventory is not an accepted commerce or order lifecycle; availability, settlement and release are unverified.
- Menexus historical assurance modelProposed
Prepare for obligations
The historical Menexus preparation model concerns commitments and risk responses; it is not a context-permission capability.
What the evidence saysThe 17 October source assigns preparation for obligations and risk responses to the product then named Menexus. This dated evidence is not the current Cortex workspace or shared Nexus permission model.
Still to proveNo qualified contract, operator or delivered ensurance service is established.
What you can explore today
Designed for real responsibilities.
Markets, governance, financing, shared wallets and provider commitments remain at different stages of development. National-jurisdiction registration, issuer terms, title, custody and authority require their own evidence. A DAV or DAC label does not automatically create legal personhood. Ordinary participation does not automatically require a node, a DAV or the SKY/ZAI financial model.
The examples use fictional details and reset locally. No account, order, contract, signature, payment or OFN receipt is created here.
Build together. Keep value working.
Make the offer understandable.
Keep the commitments traceable.