We · Skyzai Markets
Markets connects virtual twins, open affiliate distribution, an order book, local delivery and AI customer service. Follow one product through the business.
A person or organisation gives an agent a bounded brief.
Exact output, twin where applicable, rights and full costs.
Product-specific terms; the Skyzai XaaS standard is proposed.
Separate authority, acceptance, fulfilment and retained-sale evidence.
API usage supplies digital work. Nudge brings eligible demand and carries attribution into the order. Neither creates spending authority.
On this page
SPECTRE is the vision; Markets is the mission. Connect a product’s virtual twin to open distribution, an order book, local fulfilment and fully AI automated customer service.
Follow the illustrated Markets story: one actuator moves from its exact product definition into a working workshop robot.
| Record or decision | What it needs to say |
|---|---|
| Operations | Virtual twins connect components, revisions, production knowledge and service history. |
| Marketing | Open affiliate distribution lets participating people and AI agents recommend eligible products through tags and accepted referral chains. |
| Sales | The order book compares exact buyer bids, maker asks and commitments. |
| Outbound logistics | Local delivery connects the order to the nearest storage with eligible available stock. |
| Customer service | AI customer service uses the twin and order history to keep the product useful. |
The intended fulfilment path finds the nearest eligible storage holding the exact product variant. Stock availability, reservation rights, delivery cost and arrival time determine the available options.
The accepted order connects to reservation, dispatch, delivery and any return. Each record names the responsible maker, storage or delivery partner. Live inventory and delivery routing remain in development.
The goal is fully AI automated customer service across the product’s life: answer questions, diagnose problems, explain order status and coordinate returns, warranties, replacement parts and maintenance.
The AI uses the permitted, versioned twin, manuals and order history. Refunds, replacements and other actions follow the provider’s agreed permissions and remedy terms; cases outside that scope return to the responsible provider.
Qualified economic events from orders, commissions, payments and remedies are intended to connect through OFN receipts to automated accounting, bookkeeping and controlling. The illustrated workflow issues no receipts or financial postings.
We is the shared organisation, coordinating work, markets and commitments. Three journeys connect the work behind its offer to the customer who uses it and the participants who own or finance it.
| Record or decision | What it needs to say |
|---|---|
| Create and deliver | Coordinate teams, suppliers and production or service work. Inspect the activities that create and sustain value. |
| Discover and use | Compare offers, agree rights and full terms, receive delivery and obtain the support actually contracted. Explore the offer spectrum. |
| Own and finance | Establish organisations, govern assets and arrange eligible investment or credit. Keep ownership and financing rights explicit. |
An individual in Me may represent an organisation through an explicit role or mandate. Its agents use the protocols explained in They within their permitted scope. A DAV or DAC has legal-person status only where actual registration in an identified national jurisdiction is evidenced; neither a collective label nor an agent identity establishes that status.
Start with the outcome you need: work completed for you, a capability available over time, or goods to consume or keep. Compare the offers from left to right. These are proposed commercial arrangements, not live listings.
A completed result
Commission useful work.
An inspection, consultation or inference job. Define the deliverable, acceptance criteria, unit and responsible provider.
A continuing commitment
Use what you need over time.
Access, capacity or outcomes under an ongoing arrangement. Maintenance, insurance and hardware and software upgrades apply only where the offer explicitly includes them.
Something to own or consume
Choose what you need.
From consumable supplies to lasting equipment. Inspect the specification, ownership, full cost, delivery and any warranty or continuing obligations.
These offer types can overlap: equipment can be sold or provided through XaaS, and a service can include goods. Ownership, pricing and continuing obligations are specified separately in the actual terms.
A durable machine can be sold outright or used by a provider to deliver inspection-as-a-service. XaaS describes the commercial arrangement. It does not automatically transfer ownership or include insurance and upgrades.
| Term | Buy the inspection robot | Buy inspection as a service |
|---|---|---|
| Supplied subject | physical good | service |
| Arrangement | one off | continuing |
| Output | One physical inspection robot, exact configuration and revision. | Accepted inspection results, produced using the provider’s robot. |
| Customer rights | Title transfers to the buyer under the sale agreement; software licences remain separately specified. | The customer receives the agreed inspection results. The provider retains the robot; result-use rights remain explicit. |
| Maintenance | Excluded from this illustrative offer; any separate arrangement needs its own terms. | The inspection provider: Maintains its robot for the contracted service. |
| Insurance | Excluded from this illustrative offer; any separate arrangement needs its own terms. | Not specified. Confirm the scope and responsible provider before agreeing. |
| Upgrades | Not specified. Confirm the scope and responsible provider before agreeing. | Not specified. Confirm the scope and responsible provider before agreeing. |
| Measurement | One configured unit, checked against agreed acceptance criteria. | Each accepted inspection, within the agreed coverage and quality criteria. |
| Price and payment | An agreed purchase price and payment schedule; delivery and acceptance are separate states. | An agreed price per accepted inspection; minimums, overages and payment timing must be stated. |
| Term and exit | Ownership continues after the sale. Warranty, returns, transfer and end-of-life terms need their own scope. | A defined service term with cancellation, data return, continuity and remedy provisions. |
Every offer separates what is supplied, asset durability, customer rights, continuing commitments, measurement, price and payment, and term and exit. Digital outputs, consumable goods and mixed bundles fit those same dimensions.
Independent fictional offers in USD. Their prices, taxes, qualifications and terms are teaching fixtures; they are not available listings or adopted commercial policy.
| Record or decision | What it needs to say |
|---|---|
| Discovery and provider | Fictional Workshop Motion Works · maker and seller. Discovering the record does not verify eligibility or capacity. |
| Exact offer and output | One AX-14 actuator, revision C-demo, for the named workcell. Instance and fit evidence are separate from the model. |
| Rights and continuing commitments | Physical unit under the sale terms. A twin creates no title; maintenance, insurance and upgrades are not selected. |
| Price, period and exit | AX14-TERMS-1-demo · USD 269.50 fixture total: item 230.00, shipping 15.00, synthetic tax 24.50, other selected charges zero. No recurring service. |
| Commitment | The principal reviews the exact offer version, complete cost and applicable mandate. Provider acceptance is separate; an agent draft is unsigned. |
| Fulfilment and acceptance | Supplier delivery, installation check, motion check and workshop acceptance are separate. One accepted check is not acceptance of the whole unit. |
| Billing, payment and remedy | Failed delivery or an unresolved check blocks payment. Invoice pins the exact agreement; post-acceptance payment and reconciliation need separate records. |
No live order, invoice, authority, OFN issuance or payment is created. Reopen a page to reset its independent example.
Follow the durable-unit state transitions · Follow permitted usage costs without a purchase
Porter’s five primary activities provide the operational map behind We’s offers. They show where work creates and sustains value; they are not a mandatory checkout chronology. A service business can combine activities or use partners while keeping responsibilities visible.
| Record or decision | What it needs to say |
|---|---|
| Inbound logistics | Source and receive inputs, components, information or capacity; retain supplier and custody references. |
| Operations | Transform those inputs into a product, service or useful result; record the applicable configuration and quality criteria. |
| Outbound logistics | Deliver goods, results or access; keep dispatch, receipt and acceptance distinct. |
| Marketing and sales | Explain the offer, establish suitability, agree full terms and record the resulting commitment. |
| Service | Support continued use through the maintenance, remedies, upgrades and end-of-life responsibilities actually agreed. |
Product and service twins connect the applicable configurations, sources, offers and history across those activities. Procurement, people, technology and organisational infrastructure support the chain. The seven products contribute selected capabilities rather than becoming five process stages.
Shared organisations, their membership, governance, investment participation and financing belong in We. A DAV or DAC is a legal person only where its actual registration in an identified national jurisdiction is evidenced. Legal form, asset title, investor rights, voting, distributions and restrictions follow the applicable law and governing instruments. Key-controlled agent accounts using the protocols in They do not gain ownership, governance rights or authority from their identities.
An organisation may own a productive asset, sell access to it, or issue an eligible financing instrument. Those are different rights. Its governing rules and exact agreements determine who may decide, pledge, transfer or receive distributions.
SoResFi is the proposed organisational financial model. LIQUID owns its proposed equity and bond exchange functions; They explains the monetary protocol mechanics. An issuance does not automatically qualify for listing or trading.
Aureus.money owns its asset-origination explanation, including the Dragonfly artwork programme and its proposed SPV and investor terms. Skyzai explains participation and any separately evidenced integration.
Artwork title, SPV equity, a pledge and a display agreement remain distinct. Financing, trading eligibility, tax treatment and liquidity cannot be inferred from a digital twin or receipt.
A product definition, a twin and a commercial agreement answer different questions. Links preserve their relationships without treating one record’s status as proof of another.
| Record or decision | What it needs to say |
|---|---|
| Product or service | Defines what can be supplied, with its own identity, configuration and revision. |
| Twin | Represents an identified asset or service and links its evidence and history. It does not by itself establish title. |
| Offer | States a provider’s scope, rights, availability, obligations, measurement, price and duration. |
| Quote | Pins proposed terms for a particular customer, context and validity period. |
| Agreement | Records the accepted commitments and the authority under which the parties agree. |
| Fulfilment | Records work, dispatch, delivery, acceptance, defects and remedies against the agreement. |
| Payment | Records a financial obligation and its settlement state; it does not establish delivery or a useful outcome. |
| Continuing service | Tracks the support, maintenance, insurance or upgrades that have their own contracted scope and term. |
Payment can precede delivery; a delivery can be disputed; service can continue after a sale. Each record keeps its own identity, version, responsible party, permissions, retention and correction history.
Start with a buying requirement. This sample actuator shows how an exact product revision connects a question to its source, and why missing evidence calls for more information. Illustrative specification A, §2: stroke 200 mm. Load rating, mounting details and operating conditions are not supplied. This specification is authored sample data. Compare the requirement with sample revision A, rather than mixing specifications from different models. The sample states a 200 mm stroke. Source: sample specification A, §2. The load rating is missing. Request the maker’s documentation; compatibility and suitability remain unconfirmed. Proposed next step: a request for missing information. A person reviews any later purchase proposal. No live AI answer, supplier, offer or order is demonstrated.Linear actuator · sample revision A
Read the sample specification
Keep the exact revision.
Show what is known.
Ask before recommending.
From product evidence, move on to exact maker offers, costs and service commitments. The local buyer walkthrough prepares a conditional proposal for review.
The buyer specifies the intended work, budget, quantity, operating region, delivery horizon and permitted disclosure. The agent inspects actuator LA-02 and its exact maker offer.
The virtual twin shows a brushless motor, encoder, gearhead, lead screw and housing. Similar appearance does not establish replacement compatibility. The example motor BLM-28 is a separate product whose fit remains unknown.
The proposal binds the buyer brief, product revision, maker-offer version and matching XaaS offer. Known price lines and unresolved fit, stock and delivery stay visible.
If a Nudge tag accompanies the candidate, it adds the campaign, attribution-policy and accepted-chain references. It does not change suitability or earn a commission by attachment.
The local demo stops here with a conditional unsigned draft.
An exact permitted action and a seller commitment create the next boundary.
Record fulfilment and resolve cancellations, returns and disputes.
Only qualified sale evidence can enter campaign allocation; payout is separate.
Skyzai Markets connects Me, We and They. An active company seller needs an accountable company account and real products or services listed for sale. Each offer needs a clear deliverable, price, availability, terms, fulfilment and support responsibility.
An organisation can buy through Markets without publishing an offer. A shared workspace can also support non-commerce work.
A company can choose selected capabilities and payment rails, including stablecoins. It need not operate a node, adopt the full SoResFi profile, issue equity tokens or use SKY or ZAI. Organisational governance and the financial model live in We; LIQUID owns the exchange application; They explains the SPECTRE, Layer 1 and SKY/ZAI protocols proposed for agent participation.
Account management, seller eligibility and authority to accept an order have their own checks. Account creation, live listings and checkout are in development; this page demonstrates the intended journey.
The first market direction is white-collar and blue-collar machine intelligence: models, agents and apps; robots, industrial equipment and their parts; and the upstream inputs through compute, manufacturing, connectivity and energy.
Products form a spectrum from services to commoditized goods. A physical machine can be bought as an asset or used as a service. A digital product can combine rights with ongoing support. Energy is physical and can be metered. Each offer must name its deliverable, rights, unit, duration and responsible party.
Only verified makers would list their products on Skyzai. Retailer resale listings are outside this direction. Buyer agents, affiliates and logistics or service partners can support the journey; those roles do not confer product-listing eligibility. Verification criteria still need to be designed.
The ambition is a marketplace built for agents representing people and organisations. That is more specific than listing agents for sale: an agent should be able to inspect structured offers, apply the principal’s constraints, ask for missing terms and stage an exact proposal—or recommend buying nothing.
Individuals, organisations and markets are increasing scales of coordination. Me, We and They identify individuals, organisations and machine intelligence, with machine participants able to contribute across those coordination scales. Skyzai Markets is the proposed commerce experience within the wider Marketsphere of needs, contributions and fulfilment.
One useful need can connect an individual, a shared organisation and machine intelligence participating through protocols and key-controlled accounts. The principal’s identity, task context, account permissions and protocol responsibilities stay explicit.
| Record or decision | What it needs to say |
|---|---|
| Me · The individual | Start with your need and constraints. Compare full costs and alternatives, inspect the proposal and act for yourself or within an explicit organisational mandate. |
| We · The shared organisation | Create, exchange and sustain value. Coordinate shared work, publish offers, agree commitments and keep legal status, ownership and financing rights explicit. |
| They · Machine intelligence | Discover work and contribute capabilities. Machine participants work alongside individuals and organisations through explicit protocols. Provider agreements remain explicit; key control establishes neither personhood nor authority. |
The actuator walkthrough makes this concrete: a workshop’s brief meets a versioned maker offer, with the machine’s fit still to be established. The local example prepares a conditional unsigned proposal. Ordering, acceptance, payment, delivery and remedies require their own actions and records.
We explains the organisation’s commitments and value chain. Me is the individual directing or representing it; They presents machine intelligence using protocols and key-controlled accounts, supported by the proposed network and monetary foundations. The shared Marketsphere connects contributions across all three. The seven products contribute selected capabilities. LIQUID owns the commerce, wallet, exchange, order, liquidity and application-level settlement functions; the organisation retains issuance and investor obligations. OFN receipts apply only within their defined scope.
| Record or decision | What it needs to say |
|---|---|
| Skyzai API | One business integration for eligible models and capabilities, with multiple possible providers per model and explicit usage provenance. |
| App Store | Apps buy API services and deliver useful work. The proposed choice is metered use plus a known app premium, or own API with zero app fee. The sharing/advertising terms still need to be specified. |
| Product twin | The exact product graph connects assemblies, parts, revisions, evidence, offers and lifecycle history. |
| Order book / LIQUID | Maker asks and capped buyer bids compare exact specifications and terms; a match precedes authorization, seller acceptance and delivery. |
| Equity and bond exchange / LIQUID | The proposed DEX application combines eligible instrument markets, orders, liquidity and settlement workflows. Issuer rights and obligations stay with the organisation; SKY/ZAI ledger mechanics are explained in They. No live listing or trade is established. |
| Skyzai XaaS | A proposed common standard for direct maker commitments and customer reviews of agreement fulfilment, with scope, validity, named responsibility, cost and remedy. |
| Nudge | Seller-funded affiliate distribution, with registered tags and accepted marketer chains. An eligible retained sale can allocate one finite commission pool. |
Cortex can preserve permitted source context and history; Nexus governs access. APU, Circle, RealityFutures and Agentz can contribute reasoning, sourced observations, forecasts and proposals within their own responsibilities. The commercial records connect their work without turning an AI conclusion into authority.
Skyzai records are intended to make selected, permissioned evidence portable: who acted, under which authority, against which product or service version, and what delivery and outcome records followed. OFN receipts add their own specific conformance requirements where applicable. A company could give a counterpart a bounded evidence view instead of rebuilding a diligence trail from disconnected files.
Traceable operating records can help a strong venture explain performance, responsibilities and risk more quickly. That may reduce diligence work and make the company easier to evaluate for venture capital or other financing.
Receipts do not guarantee funding, valuation, a term sheet, liquidity or an investment outcome.
The same evidence model can help a company present exact products, service responsibilities, supply relationships and operating history to partners in a new region. Permissioned views can reduce duplicated onboarding while keeping private records scoped.
They do not grant product approval, licensing, tax or customs clearance, insurance, distribution, partnership or market entry.
Inspect the OFN economic receipt boundary · Open the partner data room
XaaS may become a standard inside Skyzai: compare a provider’s access, capacity or outcome commitments, including support, maintenance, insurance or upgrades only where expressly agreed. A durable asset can remain provider-owned throughout. Providers contract and fulfil directly with customers; Skyzai does not itself finance insurance.
The service must cover the exact product/version and sale context. Its provider, capacity, scope, validity, price/payer, support, remedy and exit belong in the offer. Availability does not automatically enrol the buyer in a subscription.
The intended cloud-services model adds a disclosed premium to agreed expenses, including connected third-party inference. The eligible cost base, payer and rate must be agreed. Cloud charges, publisher premiums, completed-sale commissions and affiliate allocations are separate; source fee-policy reconciliation remains open before charging.
The app’s attributable API cost plus its known publisher premium replaces a fixed subscription in the proposed model. Own-API mode has zero app usage fee; underlying provider charges continue.
Near-cost first-party services and free services funded by commerce are ambitions whose costs, subsidy owners and contribution need measurement.
The intended marketplace commission applies only to completed sales through Skyzai’s systems. Makers can sell elsewhere without this commission. The physical-item fee proposal excludes shipping; rates, precise bases, completion and refund rules remain open. Actual tax remains separate.
Nudge allocates seller-funded campaign money among eligible participants. Direct, upstream, publisher/AI and platform shares cannot each claim the full pool.
The owner’s “SaaS is dead” thesis is a testable business hypothesis: usage pricing and commerce-funded access might support useful services without fixed app subscriptions. It is not yet a measured market outcome.
Models, providers and explicit usage costs.
Two access modes and a known app premium.
Assemblies, exact revisions and evidence.
A need, comparable offers and a bounded proposal.
Service commitments that follow the product.
Attribution, recommendations and a finite reward pool.
Keep the source history when the answer changes.
| Record or decision | What it needs to say |
|---|---|
| Owner-selected direction | Me as individuals, We as organisations and They as machine intelligence; the Marketsphere spans all three, with shared agent-first market discovery and organisational value creation in We; consumable service, XaaS and durable-product spectrum; Porter’s five primary activities as an operational map; distinct commercial record lifecycles. DAV/DAC legal-person status needs actual national registration evidence. Maker eligibility, direct provider commitments and usage pricing retain their own gates. |
| Commercial terms open | API costs and charges, sharing/advertising permissions, platform fee incidence, service contracts and campaign allocation and Super Nudges. |
| Local implementation | Fictional actuator twin, synthetic catalogue, context/fit comparison, conditional unsigned proposal and teaching calculators. They demonstrate structure, not operating commerce. |
| Operations not connected | Real inventory, provider billing, engineering fit approval, seller acceptance, maker verification, XaaS standard/ratings, ordering, fulfilment, referral attribution, retained-sale validation and payouts. |
We includes organisational governance, issuance, ownership and financing. SoResFi remains a financial model with separate instrument and participation terms. Its exchange functions map to LIQUID; its monetary protocol mechanics are explained in They. These allocations establish neither automatic tradability nor a live DEX. Earlier pitch presentations remain archived.
Looking for an earlier section? Continue to product twins, makers and fulfilment, service or marketing and referrals.
Discovery identifies a possible offer. The provider, exact terms, authority, agreement, delivery, acceptance, invoice, payment and remedy each retain their own evidence.
Open the same fictional order as Me · buyer, We · author and accountable workshop or They · machine. Each visit starts a new local example; perspective controls within it preserve the record.
We · value creation · LIQUID · exchange scope · SoResFi · instruments and obligations · Network · economic receipt requirements · Aureus · asset origination
A product twin does not transfer title. Local logs do not issue OFN receipts. An order or accepted result does not establish payment. The originator, issuer, venue operator, chain operator and custodian retain separately specified responsibilities.
Product design, with local illustrative examples. Live inventory, billing, orders, attribution and payouts are not connected.
Continue exploringSkyzai APIModels, providers and explicit usage costs.Source: Skyzai Markets product model and public explanation and decision map. GitHub repository access may be required. These pages describe the design; they do not adopt commercial terms.
Context: Skyzai Markets.
