A shared integration point for models, people, manufacturing and local facilities. Start with one useful contribution; turn it into a verifiable, repeatable result.
T736 is our first physical integration point—not a restriction on future platforms.
Historical evidence is retained. Current physical T736 state is unverified. SKU codes identify delivery candidates—not available products. The T736 MCP endpoint and automatic e-Person binding are not enabled here.
01 / OUTCOME → CAPABILITY → DELIVERY
Choose an outcome—not just a port.
Each candidate has an intended result, a minimum bundle and acceptance conditions. Select a contribution without pretending the whole bundle is already ready.
T736-VIS-01
DELIVERY CANDIDATE
Visual Evidence Cell
A traceable, acceptable photograph of an agreed object at a defined station.
First physical delivery candidate
Minimum bundle · Acceptance target
Minimum bundle
Matched T736 base + specified UVC camera + mount/light/object zone + bounded capture + checks and receipt + recovery.
Acceptance target
Identity, format, coverage, clarity, exposure, integrity, retrieval, authority, restart and recovery.
Not included
Not recognition accuracy, dimensional measurement, 30 fps, every camera or higher resolution.
T736-AUD-01
DELIVERY CANDIDATE
Audio Evidence Node
An authorized sound record with specified duration, format and quality.
Freeze the audio baseline next
Minimum bundle · Acceptance target
Minimum bundle
T736 + specified USB microphone + mounting/distance conditions + bounded capture + receipt and retention/recovery.
Acceptance target
Format, duration, noise/clipping/silence limits, stable selection, unplug/reboot and retrieval.
Not included
Not speech recognition, speaker identification, translation or validated on-board playback.
T736-IO-01
DELIVERY CANDIDATE
Bounded Signal Output
One authorized command produces one time-limited, observable site signal.
First bounded output pathway
Minimum bundle · Acceptance target
Minimum bundle
T736 + selected buzzer or safe low-voltage LED + defined electrical/default states + bounded action and receipt.
Acceptance target
Duration/state limits, failure/restart defaults, duplicate handling and observed effects.
Not included
No mains switching, mechanical motion or general relay control in the first scope.
T736-SER-01
DELIVERY CANDIDATE
Sensor Bridge Node
One specified peripheral produces usable data with identity, time, units and validity.
No capabilities match. Clear the search or choose All 20.
Status key. S0 Declared → S1 Observed → S2 Bound → S3 Verified → S4 Frozen → S5 Scenario-ready. A historical S4 does not assert current readiness.
First physical pathway: identify the current node → compare the frozen UVC baseline → verify image capture → complete the Visual Evidence Cell.
03 / FOUR CONTRIBUTION PATHWAYS
Different contributions. One real outcome.
Model teams, manufacturers, researchers and ecosystem builders can work on the same named capability. Public descriptions make the next interface and the missing work visible.
Models & AI
Bring a model, input/output profile, runtime constraints and a quality test.
Industry & manufacturing
Bring a sensor, fixture, power/interface module, sample or site service, with usable specifications.
Research & academia
Bring a bounded question, method, test set and reproducible evidence.
Capital & ecosystem
Bring resources, deployment partners or a milestone-based support proposal. No investment product or return is offered here.
e-PERSON → ROLE → CAPABILITY → EVIDENCE
Keep the work identity. Connect the local capability.
The existing HSIMC registration entry accepts requests for an X@hsimc.tech work address. The target is to link accepted e-Person roles with bounded sensing, computation and actions—not to create another isolated account system.
Work identity
Accepted role
Local capability
Operation & evidence
Contribution & next work
Registration creates REQUESTED only. Address reservation, identity/workspace activation, work authority and T736 capability binding remain separate. Existing collaborators can use their established channels.
Create a small JSON brief to share through your existing collaboration channel. This form runs only in your browser; it does not submit, register or allocate a device.
05 / HUMAN-READABLE · MACHINE-READABLE
Public data
Read the same inventory as structured data. This is a catalogue, not a live MCP server.
Based on HSIMC Capability Inventory / SKU Plan C0-001 (7 October 2026), the historical controlled manual and the published reference surfaces. This page publishes descriptions, contribution pathways and candidate acceptance targets. Engineering code, builds, credentials and private operational records are not part of this public catalogue.