They · Products and machine intelligence

Know what it needs. Keep it useful.

A product belongs to a web of parts, suppliers, people and services. A proposed virtual twin could connect that knowledge throughout its working life; an authorised agent could help act on it.

Follow the story

Pico D1’s illustrated repair journey. Connected services remain to qualify. The physical product, its virtual twin and an acting agent are distinct.

The product perspective

Know a product throughout its working life.

The intended virtual twin would connect a product’s configuration and documentation with its parts, suppliers, use and service history. The physical product, its twin and an acting agent are distinct: a product can have a twin without being intelligent or having an agent.

The design could give robots, drones and compute equipment their own records. An agent may eventually help find information or coordinate work only within the permissions it has been given; these connected services still need qualification.

Explore product twins

They · The product · Fictional story

Know what it needs. Act within permission.

The physical PICO-D1-U01, its twin and an authorised agent are distinct. The parts record identifies Harbor Motion as the original source of the left-hind PICO-D1-LH-A01, revision R1.

This dog-robot story is separate from the wheeled-cleaner illustrations below.

Who and what in this fictional story

Customer: Mira
Maker: North Workshop
Robot: Pico D1 · PICO-D1-U01
Original actuator supplier: Harbor Motion
Left-hind actuator: PICO-D1-LH-A01 · R1
Suspected-fault case: CASE-LH-01

A technician inspects a component alongside a four-legged robot at a workbench. — Concept illustration. It does not establish the component’s fit, the affected side or a completed action.

Follow the complete journey

Detect and pause
A sensor anomaly opens CASE-LH-01. Pico D1 stops the affected activity and reports uncertainty; it does not diagnose the fault merely by opening the case.
Check the chain
The agent examines permitted unit history, compatible-part evidence and any current Harbor Motion offer. A similar-looking part, an old price or an unavailable listing proves neither fit nor stock.
Request authority
A person approves or a previously granted bounded mandate permits the exact expenditure and booking. Rejection or missing authority stops the consequential action.
Arrange service safely
A supplier accepts an eligible order and a service partner confirms capacity. The robot travels only if the owner permits it and route and operating safety are established; otherwise a person arranges recovery.
Verify and update
The provider checks the work and the customer or delegate accepts or disputes it. Only accepted, attributable evidence updates the installed part and service history.

Missing fit evidence, unavailable stock, denied spending or unsafe travel stops that branch. The illustration proves no diagnosis, order, travel or completed repair.

A separate illustration

A separate household-product journey.

The following chapters retain the wheeled cleaner and its wrist-actuator example, separate from Pico D1’s dog-robot story.

Know which product you mean.

Distinguish the model, chosen configuration and individual unit. Record the owner and operator, installed parts and applicable rights. A virtual twin describes the product; it is not the product or a permission to act.

Mira’s robot has a particular wrist revision and service history. A similar-looking part in a catalogue is not automatically a compatible replacement.

Explore product identity and evidence

The robot’s wrist actuator is compared with an engineering sketch and component parts.

Understand what it depends on.

Parts, suppliers, energy, software, connectivity and maintenance make useful operation possible. Keep versions, compatibility claims and replacement options connected to their sources.

The wrist actuator comes from a component supplier; its firmware and mechanical interface both matter. An agent preserves missing evidence rather than guessing a fit.

Follow the upstream supply chain

The upstream supplier checks an arm/wrist assembly in a bench fixture before packing.

Follow it into use.

Configuration, production or existing stock, delivery, installation and acceptance describe different stages. The installed configuration changes only when the relevant work has been checked and accepted.

The maker supplies Mira’s agreed robot and dock. Onboarding establishes its operating limits and support arrangements, without giving it unrestricted access to the household.

Inspect the records of fulfilment

The robot and dock are prepared together for delivery.

Respond to a need with evidence.

A sensor anomaly starts an investigation. The robot can stop the affected action, report uncertainty and ask for help. Its agent checks compatible parts, service availability and the scope of its authority before proposing action.

A suspected wrist fault leads to a replacement proposal. Incompatible parts, unavailable stock or rejected expenditure stop that proposal. Travel is allowed only if permitted and safe; a technician verifies repair before normal use resumes.

Try the separate AX-14 repair exercise

The robot’s wrist is supported during a repair with removed and replacement parts kept apart.

Prepare for what comes next.

Upgrade, transfer, reuse and retirement have their own responsibilities. Preserve relevant service history while limiting access to the previous owner’s personal information.

Mira considers an upgrade against its cost and benefit. The old unit may be repaired, transferred or recovered under applicable terms. An upgrade is a choice, not an assumed entitlement.

Explore upgrade and exit terms

Connect capabilities without losing control.

Markets brings providers and needs together. The seven products contribute specialised capabilities; OFN describes economic receipts. SPECTRE explains the proposed underlying protocols.

The robot’s agent can inspect an offer through structured interfaces while Mira uses understandable screens. Both encounter the same commitments. A passive product can have a twin without having an acting agent.

Explore machine participation and integration

App evidence and implementation scope

This illustrated journey is a design. The retained machine exercises test local boundaries; they do not connect a robot, issue credentials or execute real purchases.

Inspect capabilities and qualification

One connected experience. Different perspectives.

Me follows the individual’s life and capabilities. We follows the organisation’s primary value chain. They follows the product’s upstream dependencies, downstream relationships and working life. The seven products and OFN support all three; Markets brings them together.

Pico’s dog-robot story connects these perspectives. The separate household-cleaner example and other fictional cases retain their own identities and records.

Me · The individual We · The organisation Meet in Skyzai Markets

Explore the details and working examples

Earlier they bookmarks

Detailed examples and explanations now have their own page. These links also work without JavaScript.

Know what it needs. Keep it useful.

Know a product throughout its working life.

Know what it needs. Act within permission.

Detect and pause

Check the chain

Request authority

Arrange service safely

Verify and update

A separate household-product journey.

Know which product you mean.

Understand what it depends on.

Follow it into use.

Respond to a need with evidence.

Prepare for what comes next.

Connect capabilities without losing control.

One connected experience. Different perspectives.

Skyzai

Outline

Site

Website app

Display

Skyzai, close at hand.