Skip to content

DEVELOPER INTERFACE / PROTOCOL 1.1

Build the adapter. Not another reality database.

Public discovery and portable configuration are operational software. They are not grants, biological data transports or authenticated WorldCore sessions.

Discover

Detect actual browser/device support. A declared capability is not proof of a working device.

Calibrate + consent

Explicit familiarisation, separate input/output permission, no automatic imported consent.

Compile + stop

Validate scope, time, confidence and sequence. Translate semantic events; enforce stop on blur, disconnect or watchdog.

Portable kit example

{
  "schemaVersion": "1.1",
  "protocol": "vow-biobridge",
  "profile": "browser-first",
  "safety": {
    "neuralOutput": false,
    "physicalThermalScentTaste": false,
    "maximumIntensity": 0.2,
    "maximumDurationMs": 120
  }
}

Strict fields only, 4 KiB maximum, versioned limits. Identity, arbitrary URLs, cookies, device IDs, session state and consent fields are rejected. Each origin requires a fresh connection and explicit user gesture.

Integration contract

BoundaryInterfaceAuthority
DiscoveryGET /api/biobridge/manifestPublic read-only; not readiness for a world session
CompatibilityGET /api/biobridge/compatibilityServer probes fixed trusted peer; no biological telemetry
Persistent presenceVowMatrix /api/v3/presence/*Verified OIDC actor + signed PHP + owner/consent gates
Browser controlsVowMatrix /api/v3/biobridge/browser-device and /intentPhase 5 flag, manual control checks, stale/replay rejection; never mock-neural actuation
Future device SDKProvider adapter contractNot connected; no raw EEG upload or stimulation routes

No automatic cross-origin postMessage, WebHID/WebBluetooth scanning, account linking or secret sharing. Hardware pilot admission requires provider evidence, explicit permissions, revocation/disconnect tests and an operator review before rollout.