Reality / Intent
Start from a physical problem, prototype, sample, signal, place or research question.
真实研发起点HSIMC · REALITY R&D · MCP-NATIVE PHYSICAL R&D
REALITY R&D.
让现实研发持续发生。
Turn fragmented local hardware, sensors, models, people and evidence into addressable work that can continue across locations and time. Reality R&D keeps protocol addressability separate from physical readiness, Authority and accepted outcomes.
把分散在不同地点的人、设备、传感器、模型与证据组织成可以持续接力的真实研发工作。协议可无状态，Reality、Authority 与 Evidence 仍需连续。
PUBLIC P0 · Addressable does not mean deployed. Simulated, replay, physical and human-study evidence remain distinct.
ONE PRODUCT FAMILY · MANY REALITIES
R&D begins before every person and device can be in the same room.
Product 001 · T736 MCP-Ready Reality NodeOne product contract spanning cloud reference, hybrid integration and physical T736 Reality.
MCP-Ready Capability SurfaceMake bounded sensing, computation and action addressable without confusing protocol reachability with physical Authority.
Addressable Runtime EstateReuse Runtime identities and Reality states instead of creating a separate R&D directory.
Role Templates → e-PersonDescribe the work first. A role may later bind to a human or agent work identity only when accepted and authorized.
REALITY → WORK → EVIDENCE → CONTRIBUTION
A GenAI-native path for distributed physical R&D.
MCP Addressability
Expose bounded sensor, compute or action capabilities through a common invocation surface.
协议可调用Runtime + Product
Resolve which cloud, hybrid or physical Runtime is actually available for this work.
在哪里工作Role + e-Person
Bind accepted work roles to persistent identities without collapsing identity into Authority.
谁承担工作Evidence + Acceptance
Preserve source kind, operation identity, readback, test result and Reality Delta.
怎样证明Contribution
Connect research, supplier support, local execution and supervision to economic contribution later.
怎样形成价值PRODUCT 001
T736 is the first reference node—not the limit of the product family.
T736 MCP-Ready Reality NodeTarget Hardware Profile + Cloud Reference + Physical Adapter + Capability Bindings + Acceptance + Evidence.
WPI + UWB as first casesWPI Smart Glasses is the first academic case. UWB Sensor Bridge is the first ecosystem capability case. Child routes are not yet deployed in P0.
LIVE PRODUCT / WORK STATE · P0-002
The public product family now exposes what is live, defined and still absent.
Product 001 · T736 Reference BenchPUBLIC SURFACE LIVE · deterministic SIMULATED runs are available in-browser. No physical T736 performance claim.
Case 001 · WPI Smart GlassesCASE DEFINED · child route not yet deployed. Academic scope and human-study governance remain separate.
Case 002 · UWB Sensor EcosystemCAPABILITY CASE DEFINED · physical sensor bridge is not connected in this P0.
Physical T736 RealityCURRENTLY NOT CLAIMED ONLINE · historical capability evidence remains separate from current-state readiness.
Role TemplatesPUBLIC · no e-Person, mailbox, private workspace or Authority is provisioned by these templates.
Shared Work ContinuityAVAILABLE AS HSIMC INFRASTRUCTURE · product work may later bind to accepted roles and evidence without creating a parallel continuity system.
ROLE FORMATION
Many roles can exist before many e-Persons are created.
Reality R&D publishes role templates first. A role becomes an e-Person binding only when a human, agent or organization accepts the work and the relevant Authority is explicitly resolved.
Product EngineerSensor IntegrationResearch ContributorEvidence ReviewerHuman SupervisorSupplier SupportCase CoordinatorAcceptance Owner
This P0 surface does not create users, provision mailboxes, bind capabilities, reserve compute, authorize physical action or claim that a referenced Runtime is currently online.