HSIMC · UN Six-Language White Paper · P6 / W0-017

Appendix D - Physical Interface and Material Profiles

D.1 Profile principle

A Profile describes a possible capability under declared conditions. A physical instance must still be observed and bound before the profile becomes evidence about that particular device or material.

D.2 Material Profile - minimum fields

Identity

Source, supplier/product when known, batch/lot, previous use and owner.

Physical condition

Dimensions, mass, thickness, surface, defects, contamination and moisture.

Composition

Declared composition, coating, binder, conductive material and unknowns.

Process history

Cutting, heat, lamination, printing, cleaning and chemical treatment.

Intended function

Fixture, card layer, packaging, antenna substrate, non-structural sample or another declared function.

Tests and limits

Dimension, resistance, adhesion, abrasion, RF response, durability and other relevant tests; explicitly record unverified load, fire, hygiene, electrical, environmental or regulatory conditions.

Evidence

Photos, measurements, test report, operator, timestamp and version.

D.3 Functional-surface Profile

For printed, embroidered, foil or conductive surfaces, record geometry, line/thread/material type, process settings, substrate, bonding/curing, measured resistance or other functional property, connection method, inspection image and acceptance limit.

D.4 Hardware/adapter Profile

For cameras, NFC readers, UHF RFID readers, UWB modules, machine interfaces and motion controllers, record exact model/BOM/revision, connector and pin assignment, electrical standard and voltage levels, driver/OS/runtime dependencies, communication protocol and timing, power budget and peak behavior, calibration/coordinate frame where relevant, failure/timeout/recovery behavior, tested concurrency/resource conflicts and evidence stage.

D.5 T736 reference design boundary

The current documentary baseline describes a HelperT736C core module approximately 60 x 40 x 3.0 mm and a substantially larger reference carrier. The credit-card-sized footprint remains a design target, not a proven integrated product. A proposed minimum common carrier retains power, recovery/USB0, UART0 service access, one selected network route, powered USB Host and intentionally allocated serial expansion. Exact connectors, power rails, USB supply, interface multiplexing, thermal design and device-tree configuration remain configuration-specific engineering work.

D.6 Interface names are not electrical guarantees

UART logic level is not RS-232 and is not RS-485. A connector that physically resembles miniPCIe does not prove PCIe signaling. A camera connector does not prove driver, format, timing or calibration compatibility. The Profile must record the actual electrical and software contract.