Different demonstrations. One execution model.

Hold the common activity in view

A person's intention becomes useful computation, and that computation can continue as information, participants or available tools change. The common kernel connects what was requested, what actually ran, which result was consumed and who may decide about the next action.

The examples include original model calls, physical QPU measurements, controlled semantic roles, local services, stored evidence and mock business effects. Their roles and dates stay attached to each case. The map below compares eight relations; it does not combine different runs into one execution trace or prove that no other design can express them.

A compact index of the evidence

• Real QPU, checked results — Two Wedding hardware tasks supplied candidates for checked consumption; this is no claim of quantum advantage.
• Meaning changed actual Work — Wedding, Football and Sentinel have recorded semantic consumers. Wedding distinguishes live-origin episodes from captured re-execution. Football semantics · Sentinel investigation.
• An outside author, separate acceptance — Football's HOW/WHAT author returned candidate code; examination, corrections and owner admission remained separate.
• Another owner's result, checked locally — External DRS changed receiving computation from 96 to 102 without transferring the owner's decision.
• Independent Roots, no SuperRoot — Airline coordinated client, airline and bank; each retained its own decision and transaction effects were mock.
• A refusal and useful continuation — Supplier and Incident Atlas show lawful work alongside a refused path, with unfinished outcomes still visible. Supplier continuation.
• Useful memory, current grounds for use — Experience avoids particular repeated work; Workspace retains useful photo work. Neither carries old permission forward. Workspace continuation.
• Different episodes, one organisation of work — Intent, actual consumption, time, memory and independent decisions connect the cases; they are not one combined run.

1. Intention defines useful work

An intention includes a desired outcome and conditions on how to obtain it. Work has something concrete to satisfy before there is an effect to approve.

Wedding translates seating wishes into objectives and typed amendments under protected conditions. Football runtime makes an impossible request workable by allowing one 30-minute change; the resulting three-slot offer costs EUR 63 within a EUR 70 ceiling. An offer is useful output even before BOOK.

2. Model meaning becomes computation input

The model contributes meaning through a bounded returned structure. Runtime validates that structure and materialises supported Work; the model response is neither a finished computation nor an action grant.

In Wedding W3, Gemini amendments change compiler inputs and the computed plan. In Sentinel LS2R2, semantic contributions select concrete treatment of uncertain observations, including native reserve-series Work. A separate Atlas optional worker is controlled, so it is not counted as another cloud contribution.

3. A parent consumes the child's actual result

A child is useful when its typed returned value reaches the parent's declared input. Names and summaries alone do not establish that relation.

Growth: retained children follows the inspected current composition and U4 checkpoint: the parent consumes one retained result with a newly computed child in canonical order. Growth: missing pure capability follows a different U3 continuation in which the acquired capability's actual output reaches render. These are two bounded composition routes, not evidence that every demonstration includes arbitrary recursive children or that every child searches memory autonomously.

4. Changed conditions preserve useful neighbours

A changed input can invalidate one branch while leaving another useful. Continuation identifies both the affected computation and retained material.

Workspace loses a real audio process, recomputes media Work and retains the photograph result and preview. Wedding SR3 asks to validate the existing arrangement without another solve. One route reacts to a resource loss; the other requests a narrower operation. Both explain what work actually continues.

5. History stays; current use is checked again

Memory preserves origin, time, disagreement and earlier results. It supplies evidence for a current question, with current scope and permissions.

Experience N4-04 reuses an unchanged informational result while retaining a stored read and two current Root calls. External DRS qualifies released evidence against current source status; revocation blocks present consumption without erasing history. Testflix provides another practical form: a paid period survives as history while renewal requires its own consent.

6. Different computations meet at checked consumption

Ordinary code, models, numerical solvers and QPU hardware do different jobs. Each result needs a check appropriate to the role and a named downstream use.

Wedding W4 ran two tasks on Rigetti Cepheus-1-108Q through Amazon Braket. Selected raw measurements were decoded, checked against original conditions and consumed by native Work before separate save review. Workspace instead uses local media, preview and interaction services. Similar consumption relations do not turn its controlled principal profile into a live LLM run or make QPU use a proof of quantum advantage.

7. Owners decide locally

Ownership is separate from computation depth. A Root is a local decision role under its owner's policy, not an obligatory human click or a superior node in a hierarchy of Work.

Airline coordinates customer, airline and bank, each with its own decision and dependencies. Football keeps VenueRoot and ActivePlanetRoot distinct: the requester's consumption of a released offer does not create the venue's BOOK permission. More child Work does not create a ladder of Roots or a global business owner.

8. Creating a capability and using authority are separate

Candidate source can be created, examined and admitted. Its existence or admission does not authorise every future action it could perform.

Football authorship separates the outside AI code author from the examiner and owner admission. Growth's pure-capability retrieval independently readmits remembered source before installation and continuation. A runtime semantic model, an external code author, an examiner, a Host and a Root have different jobs.

The connections matter to the person

Selective continuation saves useful progress. Qualified reuse can avoid a particular repeated computation. Independent ownership lets participants coordinate without surrendering their decisions. A reusable capability can support more than one application. These relations explain why the project concerns the organisation of work, beyond a collection of safeguards around model output.

Geometry offers seven views of this activity with their original numbering and scopes. Incident Atlas tests refused proposals beside lawful continuations. Vision develops the larger human horizon—work moving with a person and tools extending what they can do—without presenting that future as one already executed integration.

Sources and scope

This page is a website explanation, updated 2026-10-02. Its explanation does not create a new execution result or change the status of its sources.