The Work May Continue. Authority Must Be Revalidated.
Ten-Billion-Phone Activation / 全球百亿手机激活愿景 invites independent people, organizations and communities to give existing devices and objects new productive roles. But a phone, NFC tag, pair of glasses, model or company is not the work itself. What must persist is the human purpose, a bounded working identity, truthful evidence, separately granted authority and acceptance by the person served.
No One Left Behind in the GenAI Physical Era means a person may enter through a qualified phone, NFC, QR, a short URL, speech or an assisted shared Reality. Each route should lead to the same accountable Work process when a real service is available. The global invitation is not an inventory of ten billion eligible handsets, a claim of universal connectivity or permission to operate another person's equipment.
CHAPTER 10 / WORK IDENTITY AND REALITY
10. A Persistent Working Identity Across Changing Devices
An accountable working identity outlives phones and models; its permissions do not.
PROPOSITIONAn e-Person is a persistent, addressable working identity for carrying bounded tasks across changing models, devices, locations and service providers. It is not another human being, a legal status, or automatic ownership over physical assets. Its purpose is to keep delegation, supervision, evidence and human acceptance connected when a phone is replaced or an AI session ends. Phones and NFC can be entrances; neither should become the single owner of an ongoing Work.
10.1 e-Person as working identity—not a phone, SIM, model session or replacement human
A handset has hardware identifiers; a SIM supports a connectivity relationship; an NFC tag may store an NDEF URL; a model session carries temporary interaction context. None of these alone identifies the continuing worker. An e-Person instead needs a stable, independently assigned identity, an accountable issuing or supervising party, defined roles, an auditable work history and a retirement or suspension path. Its identifier should not be embedded in an NFC UID or inferred from an Android device ID.
When a Sony phone writes or scans an NFC service URL, that is an entry event, not an e-Person activation or an authorization to act. Tag writing, independent readback, a user's scan, trusted origin, human authentication and a later Work grant are distinct gates. Similarly, an external camera or smart-glasses display might provide observations, but no preview or saved file becomes accepted Work without provenance, consent and separate verification.
The worker's persistent identity cannot replace a human. The requester, phone owner, supervising professional, local operator and service organization can be different parties with different rights. Their permission must be independently established for each relevant step.
10.2 Addressable Task Roles, assignments and scoped Human Supervision
An e-Person gains purpose through a bounded Work Assignment, not a blanket authority. The assignment identifies Work ID and intended Reality Delta; the requester; the e-Person's role; responsible Human Supervisor; target Reality; qualified capabilities; allowed actions and data; expiration, quota and revocation; evidence recipients; and who can accept or reject the outcome. “Explain this product accessibly” is not the same permission as “control this phone” or “operate every device in this building.”
The Sony MCP Phone experiment makes the boundary concrete. The Android pilot deliberately limited exposure to selected read-only device profile and battery capabilities, excluding NFC, camera, contacts and other tools. Later Revocation UX tests improved a visible Stop/Revoke control, but the final sequence of active grant, owner finger tap and independently rejected old token remained a separate acceptance test. That is scoped engineering progress, not permission for an AI to administer the whole handset [H1].
Supervision must be reachable and understandable, including for participants who need speech, larger controls or human assistance. A grant may remain AUTHORITY_PENDING, be refused, or expire without penalty. Physical actions may additionally require qualified operators and independent safety interlocks; a checkbox alone is not a safety certificate.
10.3 Continuity across models, locations, devices and participating organizations
Continuity means a verifiable chain of Work records, not an always-on model conversation. An e-Person's identity can reference a Work with its own stable ID, originating Intent, scope, accepted parent revision, actions and refusals, evidence, human decisions and later continuations. The same chain may move from one phone to a Mac or Ubuntu Local Edge, or from one supervised place to another. A tool call, an AI-generated explanation and a human-accepted outcome are different events.
Every handoff should identify source and receiving identities, document versions, data custody, time, location and the right to continue. Permitted offline evidence may be synchronized later; conflicting or duplicated events must be reconciled without rewriting history. A new model cannot silently replace a previous observation; a disconnected node cannot declare its own Work accepted. Where readback or permissions are incomplete, continuity remains PENDING rather than fabricated.
Cross-company continuity is not transferred corporate control. One provider may supply an observation, another a fixture and another accessible support. Each needs separate agreement to receive permitted Work data and perform a subsequent operation. Pannex, InnoSpire, Kingsware and community contributors keep their own customers, brands, knowledge and operating rights [H0].
10.4 Replacing a device without losing work history—or silently transferring its authority
Replacing a phone requires a controlled handoff rather than cloning credentials. First preserve only authorized Work state and evidence with verifiable provenance; then expire or suspend the old endpoint and its temporary grants. Next inspect the receiving device, operator and Reality, independently test the required capabilities and obtain fresh human authorization. Only after the receiving party accepts responsibility can the remaining Work resume.
Sony provides a useful counterexample to automatic migration. An Android APK successfully built and installed does not prove that a tag was written and independently read; an MCP battery result does not qualify camera or actuator access; and an external USB-glasses application launch does not establish successful live preview or saved JPEG. These tests have distinct acceptance records. A replacement phone or Hub must meet the same gates again instead of inheriting its predecessor's claimed readiness [H1–H3].
Revocation must stop new requests immediately and define safe completion for an operation already in progress. Deleting a token cannot retrieve a photograph already disclosed or mechanically stop a moving motor. Data retention, deletion and consent withdrawal remain governed by the rightful individual and organization. Continue the Work, never the unexamined privilege.
10.5 For Me: delegation and accountability, not unlimited ownership
“For Me” is a human-facing relationship: help me accomplish this specific outcome under conditions I can see, understand and change. It does not mean HSIMC owns the user's phone or decides every next task. An eligible person may enter through NFC, QR, a short HTTPS URL, speech or a supervised public station. Public product explanation should be possible without granting device-control privileges; meaningful verification needs trusted records; acting needs a separately scoped Work authorization.
Consider a proposed accessible product-support Work. A user scans an accessory tag, then requests help understanding or inspecting a low-risk item. An e-Person role computes the steps, asks only for necessary permissions and discovers a qualified phone, camera, shared Hub or local human service if actually available. Evidence is dated and returned for review; the user or nominated supervisor may accept, reject or request correction. This is not a claim that the Sony NFC, glasses photo capture and Work acceptance have already succeeded together.
The same delegation should support someone without mobile Internet through a qualified shared place or trusted human assistant. An NFC tag and MCP cannot create network coverage or guaranteed income. Commercial contributors may receive agreed recognition or payment, while a person's access to essential assistance must not depend on producing revenue. Global participation grows through independently accepted local results, not merely through new devices or subscriptions.
WORK / HUMAN ACCEPTANCE TESTQuestion: Can one Work survive a change of phone, model, Reality or provider while old grants are demonstrably invalid, new authority is explicit and the evidence remains readable by the rightful person? A repeatable reference test needs (1) stable e-Person and Work IDs with intact evidence links, (2) inspection of the receiving Reality, (3) a fresh limited grant, (4) rejection of the previous device's expired grant, (5) a genuine observation or justified refusal, and (6) human acceptance or correction. A scan, model answer or successful tool invocation alone is insufficient. This identity and delegation model leads to Chapter 11 — From Intent to a Computable Work Graph and Chapter 12 — Coordinating New Capability Formation. The actual Sony NFC, USB-glasses and MCP experiments retain their detailed evidence and outstanding tests in Chapters 16–17, not as presumed global readiness here.
CHAPTER 11 / WORK IDENTITY AND REALITY
11. From Intent to a Computable Work Graph
Make a desired change in Reality understandable, addressable and independently testable
PROPOSITIONAn Intent becomes useful when it identifies a desired Reality Delta, the acceptance authority and the known constraints—not when a model emits a generic to-do list. A Work Graph can compute prerequisites, eligible capabilities, separate human decisions, safe refusals and evidence without manufacturing unavailable rights or devices.
11.1 Expressing the intended Reality Delta and the conditions for acceptance
An accessible service request begins with a person specifying what needs to change in the real world. The request might be: 'I want to understand and verify the safety instructions for this cable before using it' or 'I need help recognising a low-risk repairable part'. It must distinguish requested understanding, diagnosis and physical action. The resulting Work records the requester, purpose, place or channel, desired Reality Delta, completion criterion, permitted data, deadline and who can accept the result.
An NFC tag on a product may supply a qualified HTTPS entrance but cannot represent the person's Intent or approval by itself. A user without NFC or Internet may state the same Intent through QR, accessible speech or a human-supported shared station. The original input and any interpretation should remain separately inspectable: an AI-generated paraphrase is a proposal requiring the person's confirmation, not a substitute for their expressed wishes.
11.2 Resolving available capabilities before generating or sourcing new ones
Before generating a design or purchasing equipment, the Work Graph queries only the capabilities that a rightful owner has made discoverable for this purpose. It may identify an existing phone camera, local audio output, a qualified NFC writer, an accessible operator, a nearby repair bench or a documented product instruction. Capability records expose scope, Reality location, cost, conditions, expiry, evidence of qualification and revocation, not blanket device access.
For the Sony reference path, a battery-read MCP result is evidence for a narrow read-only tool—not proof that the external USB-glasses camera can capture an accepted photograph or that a different phone supports the same NFC functions. The graph marks each prerequisite independently as REFERENCE_ONLY, AVAILABLE_FOR_INSPECTION, QUALIFIED_FOR_THIS_WORK or REJECTED. A list of installed Apps or network addresses is a candidate directory, not the outcome.
11.3 Turning missing conditions into bounded child work
An unmet condition generates a **bounded child Work** linked to the originating request and a named decision maker. For an accessible product-support task, branches may include verifying the manufacturer-controlled URL, confirming a genuine NFC NDEF readback, providing a plain-language version, obtaining rights to use an image, checking available audio output, or arranging an assisted session. Each child specifies input, deliverable, responsible provider, deadline, cost ceiling, proof, rejection reason and dependency.
An AI may draft instructions or recommend a suitable adapter, but it cannot issue a legal license, approve electrical safety, claim a repair slot or sign consent on a human's behalf. Those branches remain gated until a qualified person or institution responds. Unsatisfied demand is not hidden: it can become a reusable request to an independent supplier, a university laboratory or a community partner, without asserting that anyone has accepted an order.
Non-executable e-Person Work Graph template ↗
11.4 Parallel preparation, physical dependencies and explicit human decision points
Some child Works can run in parallel: translating safe public guidance, checking the expected NFC tag format, preparing an accessible interface and locating a qualified local helper. Others form hard dependencies: no tag-based service activation before destination integrity is reviewed; no photograph before camera permission and data rights are granted; no relay action without local interlocks and an accountable operator. The graph records both the concurrency and the point at which a human must decide.
A controlled local Authority Gate evaluates who is asking, which capability is being invoked, the actual Reality, whether the grant remains valid and what physical effect could follow. The cloud model may plan, summarize and compare branches; its recommendation is not an execution permit. Approval, denial, revocation and a supervisor's intervention are first-class Work events. A useful negative outcome is a safe refusal with a reason the person can understand.
11.5 Preserving the work when a tool fails, a node disappears or a model changes
Durable Work identity is separate from transient tools and model sessions. Every transition references accepted parent records, source evidence, schema or contract revision, operator decision and time. When an NFC reader fails, a Sony phone is removed, an MCP tool times out or an LLM provider changes, the graph preserves what is known and its unresolved next steps. Retried requests need deduplication so they do not create duplicate physical actions, charges or contradictory acceptance records.
A receiving node must check its own capabilities and fresh authorization instead of copying temporary credentials from the previous device. A previously accepted observation remains an historical fact, while an incomplete camera or tag test stays PENDING. The requester or named supervisor can choose to continue, seek a new provider, revise the goal or stop. Truthful continuity is more valuable than uninterrupted automation if an autonomous continuation would be unsafe or unapproved.
WORK / HUMAN ACCEPTANCE TESTChapter 11 is accepted if a second operator can reconstruct the originating human Intent, verify the intended Reality Delta, inspect dependencies and independent child Works, and reproduce a safe accepted outcome or explicit refusal after a deliberate tool or node failure.
CHAPTER 12 / WORK IDENTITY AND REALITY
12. Coordinating New Capability Formation
Form the smallest missing physical or human capability under independent rights and accountable evidence
PROPOSITIONWhen the Work Graph finds that the required capability does not yet exist or cannot lawfully be called, HSIMC's proposed role is to help specify, prepare and coordinate a qualified solution. Capability formation may mean reuse, software adaptation, accessible human assistance, a local fixture, verified manufacturing or an explicit refusal; it does not require a centralized inventory or a compulsory business platform.
12.1 e-Person-supported discovery, specification, preparation and execution coordination
An e-Person may help turn missing conditions into a precise specification: intended outcome, target person and accessibility mode, device and interface requirements, approved data, electrical and mechanical limits, site, timescale, estimate, supervisor and acceptance test. It can ask for missing facts, compare alternatives and generate a controlled proposal. The relevant humans still decide whether to commission, share, build, buy, repair, test or discontinue.
Consider an NFC-enabled accessory that a person cannot easily use. The shortest solution may be a readable instruction page and a human telephone contact rather than a new AI device. Another case may require a verified HTTPS tag, a QR fallback, voice output or an affordable shared Hub. Each option needs current evidence of usability. The specification should not quietly transform an information request into camera, payment or physical-control permissions.
12.2 Bringing local contributors, manufacturers and professional supervisors into the same Work
A Work can involve a product maker, a local technician, an accessible-interaction designer, a trusted community venue, a qualified safety reviewer and a receiving participant without merging their organizations. The Work Graph links separately authorized contributions and assigns who provides equipment, owns the output, verifies accessible use, pays or receives agreed compensation, handles data and signs acceptance. Companies retain their brands, customer relationships and contracts; personal trust is not delegated corporate authority.
Pannex offers a meaningful historical route for actual products and supply coordination, InnoSpire provides candidate inclusive-interaction experience, and other verified technical or local contributors may help with adapters, manufacturing and site execution. These are possible bounded contributions, not blanket four-party commitments. FIFA-associated product concepts require a distinct rights-holder route and cannot be inferred from an ordinary NFC pilot. Human participants should receive fair terms and must not be treated as free testing resources.
12.3 Forming a new tool or resource configuration rather than matching only existing listings
New capability may come from **composition**, not invention of a novel chip. A qualified old phone can offer one low-risk sensor or interface; a cable supplies safe power or data; NFC/QR provides optional entry; a local workstation or MCP-compatible adapter exposes only an approved Tool; a fixture stabilizes the object; and a human worker checks the observed result. The formed configuration receives its own Capability Contract, version, dependency list, Reality binding, expiry and revocation path.
Compatibility is not presumed. A USB-C port does not guarantee video output or host power, a generic NFC tag cannot establish authenticity, and Matter or a vendor App does not transfer control to a cloud model. A test proves only its observed hardware, software, operator and time window. The configuration must reject unsafe wiring, unsupported OS permissions, missing consent and unverifiable manufacturer claims rather than assign itself an optimistic READY label.
12.4 Evidence → acceptance → reusable capability → the next productive opportunity
A formed capability is not reusable merely because an installation script exits successfully. Its first Work requires independent evidence of configuration, permission, actual physical or informational output, errors, accessibility and human acceptance. A qualified reviewer should separate DEVICE_PRESENT, INTERFACE_REACHABLE, WORK_AUTHORIZED, ACTION_OBSERVED and OUTCOME_ACCEPTED. Any failed step has a reusable rejection reason and a corrected test plan.
After acceptance, the system may publish a **non-sensitive reusable specification**: compatible interface, operating limits, safe setup, evidence requirements, support needs, cost range and supported language. This helps another provider reproduce the outcome while leaving private credentials, personal data and local contracts with their rightful owners. A reproducibility claim requires another phone, operator or location—not just another request to the same LLM.
12.5 Keep one Work continuous across a user, workshop, supplier and receiving site
The same Work may travel from a person who needs help, to a supervising Hub, to a small workshop, to a supplier and finally to a receiving site. Each handoff carries the permitted purpose and evidence, not an inherited unlimited grant. The receiving party explicitly accepts its role, checks safety and local conditions, and can refuse or request revision. The e-Person identity holds continuity; each actor keeps its own authority, while named humans remain accountable for physical work and acceptance.
Two candidate routes illustrate the breadth. An Accessible Product Passport turns a neutral NFC/QR-linked product into understandable guidance and an optional support Work. Human-Guided Circular Work examines a low-risk reusable part, applies qualified human inspection, and records actual reuse, repair or disposal rather than invented environmental benefit. Both may be valuable without a new platform, a high-end phone or a large order. The global success condition is a safe, accessible, independently accepted result that can be repeated elsewhere under fresh authorization.
WORK / HUMAN ACCEPTANCE TESTChapter 12 succeeds when a needed new capability is specified from a real Work, an independent provider can make or supply it under explicit terms, another operator can verify it and the rightful person accepts an outcome. A visible STOP for missing safety or authority is a valid result.