REALITY R&D · PRODUCT 001

T736 MCP-READY
REALITY NODE.
从云端参考到物理节点。

A reference product for making local sensing, compute and bounded physical action addressable to GenAI-era work without pretending that a cloud simulation and a physical T736 are the same Reality.

T736 产品不是一块开发板本身，而是一套可跨 Cloud Reference、Hybrid Integration 与 Physical Node 延续的 Capability Contract、Acceptance 与 Evidence。

Reality R&D Start a T736 Work · 定义工作

PUBLIC P0 · Product surface deployed. Current physical T736 node is not claimed online by this page.

ONE PRODUCT · THREE REALITY LAYERS

The upper work contract should survive the transition from simulation to physical Reality.

Cloud Reference / SimulatorProtocol, scenario, sensor-stream, model-package, output and evidence semantics. Performance equivalence to physical T736 is not assumed. Hybrid NodeCombine real local sensors or actions with cloud-side computation and replay while preserving source-kind boundaries. Physical T736 NodeReal Ubuntu/T736 hardware, drivers, sensors, local model runtime and I/O. Physical readiness requires its own current evidence. Acceptance + EvidenceKeep SIMULATED, REPLAY, PHYSICAL and HUMAN_STUDY evidence classes distinct and inspectable.

CAPABILITY SURFACE

Input, local compute, output and evidence belong to one bounded product contract.

Sensor Input

Camera, UWB, ToF, ultrasonic, IMU and future local capability adapters.

SIMULATED / REPLAY / PHYSICAL

Compute Profile

T736-class target compute, model-package interface and bounded local runtime.

Target profile ≠ calibrated cloud equivalence

MCP Surface

Expose bounded capabilities through a common machine-facing interface while preserving local truth and Authority.

Addressable capability

Output Reaction

Audio, UI response, relay/GPIO or other bounded actions can share the same work/evidence path.

Action still requires Authority

Readback

Fresh state, operation identity, source kind and execution evidence remain inspectable.

Protocol response ≠ physical effect

Acceptance

Cloud, hybrid and physical acceptance gates remain separate so drift and uncertainty stay visible.

Reality-specific canaries

T736 REFERENCE BENCH · SIMULATED P0-002

Run the contract before the physical node is ready.

This browser-side bench generates deterministic simulated sensor observations for research and integration. It demonstrates the data/evidence path only; it does not emulate physical T736 performance, electrical behavior or a live human study.

SOURCE · SIMULATED TARGET NPU CLASS · 3 TOPS PROFILE CLOUD EQUIVALENCE · NOT CALIBRATED PHYSICAL T736 · NOT CLAIMED ONLINE AUTHORITY · NONE

Scenario Output language

Simulated image / scene frame

SIMULATED FRAME Select a scenario and run a simulated observation.

Synchronized sensor state

ToF—NOT RUN

Ultrasonic—NOT RUN

IMU—NOT RUN

UWB—NOT RUN

Computed observation / output reaction

No observation yet.

UNCERTAINTY — AUDIO — RELAY — PHYSICAL EFFECT · NONE

Relay and audio are simulated output states in this P0. No device actuation occurs.

Evidence object

{
  "state": "NOT_RUN"
}

Stateless capability invocation preview

{
  "state": "PREVIEW_NOT_RUN"
}

Preview only. No public MCP endpoint is deployed by P0-002.

Bench state

Cloud Reference: browser-executed deterministic simulation.

Hybrid Node: defined, not connected.

Physical T736: not claimed online.

Evidence classes: SIMULATED / REPLAY / PHYSICAL / HUMAN_STUDY remain distinct.

Loading scenario data…

Operation	Scenario	Trigger	ToF	Ultrasonic	Uncertainty	Source

CLOUD REFERENCE

Develop the work contract before every physical dependency is available.

MCP-ready reference surfaceDefine discovery, invocation, operation, readback and evidence semantics without claiming physical-device readiness. Scenario + sensor simulationGenerate deterministic sensor streams and output reactions so research and supplier integration can start before final hardware assembly.

HYBRID NODE

Real local signals can enter before the final T736 product is frozen.

UWB / sensor bridgeA real sensor sample can be translated locally into the common capability contract while compute or replay remains elsewhere. Mixed Reality without mixed evidenceEach observation carries a source kind so simulated, replay and physical inputs never become indistinguishable.

PHYSICAL T736 NODE

Physical readiness is a separate evidence class.

Local MCP-ready node pathUbuntu/T736 can later implement the same semantic contract through real drivers, devices and local bounded execution. Current truthHistorical T736 capability evidence is preserved, but this P0 page does not assert that the physical node is currently online or unchanged.

FIRST REAL CASES

Cases grow under the product; they do not define the whole product.

Case 001 · WPI Smart GlassesAcademic collaboration case for sensor-aware assistive perception. Child route is not yet deployed in this P0. Case 002 · UWB Sensor EcosystemFirst supplier/ecosystem capability case for local sensor bridging. Child route is not yet deployed in this P0.

AVAILABLE ROLE TEMPLATES

Roles can be addressable before e-Persons are instantiated.

These are work-role templates only. No mailbox, private workspace, capability binding or Authority is created by viewing this page.

T736 Product EngineerSensor Integration ContributorResearch Case CoordinatorEvidence ReviewerSupplier SupportHuman SupervisorModel IntegrationAcceptance Owner

Cloud Reference ≠ Physical T736. Product page ≠ Runtime identity. Role template ≠ e-Person. Identity ≠ Authority.

Product 001 can be publicly addressable before every implementation is deployed. Readiness, availability, authorization and accepted physical outcomes require their own fresh evidence.

T736 MCP-READYREALITY NODE.从云端参考到物理节点。