Activate an identity. Port it into a Runtime.
The signal is an entry event. The Runtime is the address.
TapPort is not an NFC, QR or radio technology product. It is an identity activation and Runtime handoff layer: an event or signal can activate a candidate identity, resolve the bounded Reality reference, and port it into the next Runtime context. Activation is not authentication. Route is not Authority.
The entry can be near, far, visible, invisible or human-triggered.
“Tap” names the activation moment, not one radio technology. The signal may come from a finger, code, tag, device, network or sensor. What matters is that the event can be resolved into a bounded identity / Runtime reference without confusing detection with permission.
finger gesture · QR · barcode · text / marker
NFC · HF RFID · contact / proximity events
UHF RFID · Bluetooth / BLE · UWB
LoRa / LoRaWAN · SIM / eSIM / cellular identity events
camera · light state · optical code · spectral observation
odor / chemical · temperature · acoustic · motion / presence sensors
API callback · device event · machine state transition
lawfully observed gesture, presence or other bounded activation cues
A signal becomes an entry only after resolution.
TapPort deliberately separates activation, identity proof, Runtime routing and Authority.
Detection ≠ identity proof
A Bluetooth advertisement, RFID read, QR scan, camera detection or SIM event can activate a resolution path; it does not prove who owns or controls the Reality.
Activation ≠ authentication
“Something was activated” is a state transition. Authentication is a separate evidence / Authority process.
Tap ≠ consent
The human or object being detected does not automatically consent to downstream processing or execution.
Route ≠ Authority
A Port can hand off to the correct Runtime route. Whether the next action is lawful and executable remains a Minimum Authorized Path problem.