Vision
Organisations can create useful value, honour commitments and renew their shared capabilities while participating through open, replaceable systems.
We · The shared organisation
Organisations.
For organisations: combine capabilities, coordinate commitments and create shared value. DAVs and DACs retain their distinct organisation models and evidenced legal status.
Follow a shared needA 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.
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.
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.
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.
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.
Fulfil and support commitments
Obtain applicable authority before accepting an agreement. Track fulfilment, installation where relevant, inspection, acceptance, payment, cancellation, return and remedies.
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.
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.
An organisational case · fictional local example
From shared purpose
to a useful customer outcome.
The workshop restores its robot so it can offer an inspection service. Follow the distinct responsibilities behind the repair, the customer agreement and the result.
Read the whole case, or try its named actors’ decisions. No real equipment is inspected; all parties, approvals and payments are fictional.
Organisational fixture and obligation review. Actual signing power requires its own supplied mandate. Choosing a view changes the displayed records, never the authority to act. These client-side views demonstrate intended disclosure; they provide no real confidentiality.
The workshop proposes a defined inspection result. Repair, qualification and customer agreement are separate. Purpose-bound context · simulated Each named participant has a separate context grant. Expiry or revocation stops new disclosures; the worker also needs a current grant to submit inspection work. Advancing the shared date can expire other grants too. Existing agreements, delivered reports and debts keep their own records. No copy has been requested for this participant. These controls illustrate a fictional context owner’s decisions. A new grant is a separate record; it supplies no signature or contract approval. The named actors’ case controls below remain a simulator, independently of the selected view.Permission ends. Earlier copies remain.
1 · Shared purpose
People and resources, working towards a useful result.
Nora contributes robotics skills. The workshop coordinates the people, equipment, information and capital behind an inspection service. Membership alone grants no purchasing or customer-contract authority.
- Case
- WORKSHOP-INSPECTION-DEMO
- Revision
- 1
- Simulated date
- 2026-10-21
- Purpose
- The workshop coordinates a defined robotic inspection offering, its delivery, obligations and renewed capability.
- Organisation
- WORKSHOP-DEMO · ordinary fictional organisation; no legal registration asserted
- View scope
- Organisational fixture and obligation review. Actual signing power requires its own supplied mandate.
2 · Restore and qualify capacity
A repaired robot is an input, not a customer promise.
An accepted repair restores equipment. This service still needs a matching provider, robot, protocol, region, job scope, capacity and quality evidence, reviewed for this offer.
- Repair
- Not loaded
- Configuration
- XR-7 revision D with accepted AX-14 revision C installation
- Scope
- One fixture inspection of 20 identified sample parts; a report of measured dimensions, not equipment safety certification
- Capacity
- One reserved workshop session for this job
- Quality criterion
- All 20 measurements and sample identifiers present; fixture tolerance check and report review required
- Required qualification
- WORKSHOP-DEMO · ROBOT-CELL17-01 · INSPECTION-PROTOCOL-1 · WORKSHOP-SITE-17
- Supplied qualification
- WORKSHOP-DEMO · ROBOT-CELL17-01 · INSPECTION-PROTOCOL-1 · WORKSHOP-SITE-17
- Evidence source
- WORKSHOP-INSPECTION-FILE-1 · issued 2026-10-20 · reviewer REVIEWER-DEMO; fictional review only
- Qualification
- INSPECTION-QUALIFICATION-DEMO · version 1; reviewed version none; valid through 2026-11-21; matching evidence needs review
- configuration evidence
- CONFIG-XR7-D-AX14-C · revision 1 · current; required CONFIG-XR7-D-AX14-C
- scope evidence
- SCOPE-INSPECTION-01 · revision 1 · current; required SCOPE-INSPECTION-01
- capacity evidence
- CAPACITY-SESSION-01 · revision 1 · current; required CAPACITY-SESSION-01
- quality evidence
- QUALITY-CHECK-01 · revision 1 · current; required QUALITY-CHECK-01
3 · A distinct customer commitment
Make the offer understandable. Agree its exact terms.
The customer buys a defined inspection result. The workshop retains its robot. Provider and customer approvals refer to this agreement; approval of an actuator purchase approves none of these downstream commitments.
- Provider
- WORKSHOP-DEMO
- Customer
- CUSTOMER-DEMO
- Offering
- INSPECTION-OFFER-DEMO · revision 1 · service / one-off
- Output
- One report covering the 20 identified sample parts under SCOPE-INSPECTION-01.
- Rights
- Customer use of this report for the stated purpose; the workshop retains its robot. No safety certification or robot title transfers.
- Measurement
- One delivered report, explicitly reviewed and accepted against QUALITY-CHECK-01.
- Price and payment
- USD 90.00 all-in fixture price; no further taxes or fees in this example. Payment only after explicit customer acceptance.
- Term, exit and remedy
- One job, no automatic renewal. Cancel before work without charge; a disputed result permits one rework or cancellation without charge; a recorded payment requires a separate full refund record.
- Provider obligations
- Workshop maintains its own robot for this job. No customer insurance product, upgrades or continuing support included.
- Customer agreement
- None; input authority, membership and qualification approve no customer contract.
- Exact approvals
- Provider not supplied; customer not supplied
Before a new customer commitment
- Load and review the accepted repair fixture first. Its acceptance does not qualify an inspection provider.
- The exact qualification and offering requirements need their own review.
Try a changed source or offer
A change can block new work or put remaining obligations into remedy. Historical agreements and effects keep their original records.
4 · Deliver, review and renew
Work performed. Result delivered. Customer accepted?
Performance, delivery and customer acceptance keep separate records. A disputed result needs a remedy. Payment follows this fixture’s explicit post-acceptance terms; renewal remains a new review.
- Work and result
- No work or report recorded.
- Earlier results
- None
- Remedy
- none
- Renewal
- Not started
- Customer invoice
- Not recorded
- Customer payment
- not-paid
- Refund
- not-due
- Customer reconciliation
- open
Review decision history
- Decision history
- 1: purpose · Shared purpose and a bounded inspection offering recorded; no customer agreement exists.
See the five primary value-chain activities
- Inbound logistics
- Receive the documented actuator and the permitted equipment context. Supplier fulfilment and payment keep their own records.
- Operations
- Restore the robot, review its configuration and perform the inspection under the agreed criteria.
- Outbound logistics
- Deliver the versioned inspection report. Delivery alone does not establish customer acceptance.
- Marketing & Sales
- Explain the service, check suitability and agree exact scope, rights, price and responsibilities before committing.
- Service
- Review the outcome, resolve discrepancies and consider maintenance or requalification under separately agreed terms.
These activities are a reference map, not an organisation chart or a mandatory transaction order. Customer terms can be agreed before performing that job. Shared infrastructure, skills, technology and procurement support the whole chain.
Explore the value-chain modelUnderstand the offering spectrum and its seven dimensions
- Subject
- Physical goods may be consumable or durable. A completed service, digital output or bundle defines a different supplied subject.
- Arrangement
- A one-off job or purchase differs from continuing access, capacity or an outcome commitment through XaaS. A durable robot can support either arrangement.
- Rights
- State title, access or result-use rights explicitly. A twin represents its subject; it does not establish ownership.
- Measurement
- Define the unit, quantity, period, coverage and acceptance criteria.
- Price and payment
- Make the all-in price, currency, charges and payment timing understandable.
- Term and exit
- Specify validity, duration, cancellation, data return and remedies.
- Provider obligations
- Name who delivers and which support, maintenance, insurance or upgrades are included, excluded or still unspecified. XaaS adds none automatically.
Inspect the same permitted records as structured data
The human facts above and this JSON use the same allowlisted projection, including an explicit denial with no current records when a grant is invalid. Previously delivered copies are labelled separately. Worker, supplier, customer and steward views omit unrelated personal contacts, notes and reserves. Simulator controls name the fictional actor whose decision they illustrate; the selected view supplies no mandate.
{
"caseId": "WORKSHOP-INSPECTION-DEMO",
"revision": 1,
"simulatedDate": "2026-10-21",
"view": "steward",
"purpose": "The workshop coordinates a defined robotic inspection offering, its delivery, obligations and renewed capability.",
"permission": "Organisational fixture and obligation review. Actual signing power requires its own supplied mandate.",
"status": "The workshop proposes a defined inspection result. Repair, qualification and customer agreement are separate.",
"access": {
"disposition": "permitted",
"reason": "The simulated grant permits this purpose-limited context. It supplies no contract or signing authority.",
"grantId": "CONTEXT-STEWARD-1",
"purpose": "Review workshop coordination and obligations",
"subjectId": "WORKSHOP-STEWARD-DEMO",
"issuedOn": "2026-10-21",
"expiresOn": "2026-10-22"
},
"sections": [
{
"id": "purpose",
"title": "A shared purpose",
"fields": [
{
"label": "Case",
"value": "WORKSHOP-INSPECTION-DEMO"
},
{
"label": "Revision",
"value": "1"
},
{
"label": "Simulated date",
"value": "2026-10-21"
},
{
"label": "Purpose",
"value": "The workshop coordinates a defined robotic inspection offering, its delivery, obligations and renewed capability."
},
{
"label": "Organisation",
"value": "WORKSHOP-DEMO · ordinary fictional organisation; no legal registration asserted"
},
{
"label": "View scope",
"value": "Organisational fixture and obligation review. Actual signing power requires its own supplied mandate."
}
]
},
{
"id": "capacity",
"title": "Restored and qualified capacity",
"fields": [
{
"label": "Repair",
"value": "Not loaded"
},
{
"label": "Configuration",
"value": "XR-7 revision D with accepted AX-14 revision C installation"
},
{
"label": "Scope",
"value": "One fixture inspection of 20 identified sample parts; a report of measured dimensions, not equipment safety certification"
},
{
"label": "Capacity",
"value": "One reserved workshop session for this job"
},
{
"label": "Quality criterion",
"value": "All 20 measurements and sample identifiers present; fixture tolerance check and report review required"
},
{
"label": "Required qualification",
"value": "WORKSHOP-DEMO · ROBOT-CELL17-01 · INSPECTION-PROTOCOL-1 · WORKSHOP-SITE-17"
},
{
"label": "Supplied qualification",
"value": "WORKSHOP-DEMO · ROBOT-CELL17-01 · INSPECTION-PROTOCOL-1 · WORKSHOP-SITE-17"
},
{
"label": "Evidence source",
"value": "WORKSHOP-INSPECTION-FILE-1 · issued 2026-10-20 · reviewer REVIEWER-DEMO; fictional review only"
},
{
"label": "Qualification",
"value": "INSPECTION-QUALIFICATION-DEMO · version 1; reviewed version none; valid through 2026-11-21; matching evidence needs review"
},
{
"label": "configuration evidence",
"value": "CONFIG-XR7-D-AX14-C · revision 1 · current; required CONFIG-XR7-D-AX14-C"
},
{
"label": "scope evidence",
"value": "SCOPE-INSPECTION-01 · revision 1 · current; required SCOPE-INSPECTION-01"
},
{
"label": "capacity evidence",
"value": "CAPACITY-SESSION-01 · revision 1 · current; required CAPACITY-SESSION-01"
},
{
"label": "quality evidence",
"value": "QUALITY-CHECK-01 · revision 1 · current; required QUALITY-CHECK-01"
}
]
},
{
"id": "offer",
"title": "A distinct customer commitment",
"fields": [
{
"label": "Provider",
"value": "WORKSHOP-DEMO"
},
{
"label": "Customer",
"value": "CUSTOMER-DEMO"
},
{
"label": "Offering",
"value": "INSPECTION-OFFER-DEMO · revision 1 · service / one-off"
},
{
"label": "Output",
"value": "One report covering the 20 identified sample parts under SCOPE-INSPECTION-01."
},
{
"label": "Rights",
"value": "Customer use of this report for the stated purpose; the workshop retains its robot. No safety certification or robot title transfers."
},
{
"label": "Measurement",
"value": "One delivered report, explicitly reviewed and accepted against QUALITY-CHECK-01."
},
{
"label": "Price and payment",
"value": "USD 90.00 all-in fixture price; no further taxes or fees in this example. Payment only after explicit customer acceptance."
},
{
"label": "Term, exit and remedy",
"value": "One job, no automatic renewal. Cancel before work without charge; a disputed result permits one rework or cancellation without charge; a recorded payment requires a separate full refund record."
},
{
"label": "Provider obligations",
"value": "Workshop maintains its own robot for this job. No customer insurance product, upgrades or continuing support included."
},
{
"label": "Customer agreement",
"value": "None; input authority, membership and qualification approve no customer contract."
},
{
"label": "Exact approvals",
"value": "Provider not supplied; customer not supplied"
}
]
},
{
"id": "outcome",
"title": "Delivery, obligations and renewal",
"fields": [
{
"label": "Work and result",
"value": "No work or report recorded."
},
{
"label": "Earlier results",
"value": "None"
},
{
"label": "Remedy",
"value": "none"
},
{
"label": "Renewal",
"value": "Not started"
},
{
"label": "Customer invoice",
"value": "Not recorded"
},
{
"label": "Customer payment",
"value": "not-paid"
},
{
"label": "Refund",
"value": "not-due"
},
{
"label": "Customer reconciliation",
"value": "open"
},
{
"label": "Decision history",
"value": "1: purpose · Shared purpose and a bounded inspection offering recorded; no customer agreement exists."
}
]
}
]
}A completed job prompts learning and renewal review. It creates no automatic continuing service, insurance, financing or fresh qualification. No real signature, order, payment, entity or OFN receipt is created here.
Inspect the independent actuator procurement exampleCase state lives only in this page and resets on reload. A link opens an independent demonstration; it does not transfer the current case or recover an account.
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
Present organisational purpose, acting account, responsibilities, proposals and decisions. Proposed KPI. Decision comprehension: sampled reviewers identifying the acting organisation, exact action, applicable approver and unresolved conditions divided by sampled reviews. Collection requires an appointed owner, permitted records and an agreed protocol. Definitions do not start telemetry or appoint anyone. Specialist Agents. Intake guide; Information organiser. Skills and responsibilities. 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. Representative interface and case source only. A composed case does not establish a released APU interface or accepted signed-in journey. Inspect the dated Flutter inventory and its limits. Repository access may be required. Future integration. APU owner: qualify the actual purpose/review screen, permitted inputs, accessibility and refusal paths on the target devices.Proposed measures and specialist Agents
How this would be measured
Organisational decision comprehension
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
Coordinate bounded assignments, Cortex memory and purpose-limited Nexus views 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. Cortex memory and Nexus connections belong to Agentz; website state is not durable or signed-in continuity. Inspect the dated Flutter inventory and its limits. Repository access may be required. Future integration. Agentz owner: accept effective grants, retained records, versioned handoff, provider refusal and recovery in the signed-in host.Proposed measures and specialist Agents
How this would be measured
Accepted work within scope
Actual scope violations
Blocked out-of-scope attempts
Explore Agentz’s AgentsSources and integration limits
Rosetta agent row · Cosmology
Menexus
Define dependable delivery, prevention, acceptance evidence and remedies; add qualified insurance when applicable. Proposed KPI. Sampled commitments with provider, deliverable, acceptance criteria, remedy and applicable approval evidence divided by sampled commitments. Track accepted due outcomes and overdue discrepancies separately. Collection requires an appointed owner, permitted records and an agreed protocol. Definitions do not start telemetry or appoint anyone. Specialist Agents. Commitment planner; Evidence reviewer. Skills and responsibilities. Prepare commitments and review outcomes. A complete evidence packet alone does not prove successful delivery. Capability snapshot: 2026-10-17. Each source keeps its own evidence level. These records do not establish a live service. Representative Flutter source. Marketplace source supplies commercial context only. Menexus integration, independent acceptance and any named insurance provider/policy remain unqualified. Inspect the dated Flutter inventory and its limits. Repository access may be required. Future integration. Menexus owner: qualify commitment, independent review and remedy contracts; qualify insurance separately with its actual provider and terms.Proposed measures and specialist Agents
How this would be measured
Commitment completeness
Accepted due outcomes
Unresolved discrepancy age
Explore Menexus’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 full participant VMOSKA source. Repository access may be required.This participant’s example and integration limits
Specialist Agents describe roles and skills in development. People, models and tools may contribute within an explicit assignment. A role description establishes neither staffing nor permission to act. The participant group They remains distinct from these specialist roles.
Interactive design preview · in development
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: a cleaning visit, 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 owns commerce, exchange, liquidity and payment semantics; the We perspective connects them 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 Menexus contribute when their responsibilities are needed.
Ordinary evidence records and OFN economic receipts have different qualification and issuance requirements.
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 obligationsAsset origination remains with Aureus
Aureus owns the asset-origination explanation. The planned Dragonfly artwork case belongs to that programme: an SPV, investor rights, financing choices, a virtual twin and a display arrangement, each with explicit conditions. Publication of the full case remains unverified.
We explains how participants coordinate and enter relevant markets; it does not take over the originator’s issuance or legal responsibilities.
Explore the Aureus art programmeExternal originator programme. A planned case study is not an available investment or 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.
Agentz Nexus supplies purpose-scoped connections. 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 scoped connectionsAgentz Nexus · 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.
Agentz Cortex retains permitted context; Circle keeps attribution and corrections; LIQUID owns commerce and payment semantics. 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 a maintenance robot with a continuing cleaning 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
Agentz owns Cortex, where source-linked text lifecycle work has local tests.
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.
- MenexusProposed
Prepare for obligations
Menexus owns the proposed preparation of risk responses and commitments.
What the evidence saysMenexus currently owns preparation for obligations and risk responses.
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.