code wiki / drv

topic: drv

10 modules sharing the drv name family (derived from the tree's prefix discipline).

The 'drv' topic family in the Nishi sovereign ecosystem focuses on driver-related functionalities, integrating hardware mapping, control flow, and protocol synthesis. Modules like _drv_bind_gate manage autonomous driver bring-up without mocks, while _drv_f1_gate handles consent-gated telemetry. _drv_proto_gate ensures protocol compliance from specification, supporting the ecosystem's modular, binary-per-organ design.

auto-narrated by the local model from this topic's module headers; links verified against the wiki index.

narrated overview -- maintained by the narration lane, module links verified against this wiki.

moduledescriptionlinesfuncs
_drv_bind_gate.nxthe gate for AUTONOMOUS DRIVER BRING-UP (X-DRV-W2). NO mocks.18210
_drv_f1_gate.nxgate for CONSENT-GATED DEVICE TELEMETRY (X-DRV-F1). NO mocks.17612
_drv_f2_gate.nxgate for the FEDERATED DRIVER REGISTRY (X-DRV-F2). NO mocks.21115
_drv_f3_gate.nxgate for LOCAL-ONLY DRIVER SELF-TUNE (X-DRV-F3). NO mocks.10410
_drv_proto_gate.nxthe gate for DRIVER-PROTOCOL-FROM-SPEC (X-DRV-W1). NO mocks.34315
_drv_v1414.nxbinds devices by vendor from HWMAP; control flow + pattern synthesized from the spec, compiled by nx_cc. license_tier: ORIGINAL261
_drv_v1af4.nxbinds devices by vendor from HWMAP; control flow + pattern synthesized from the spec, compiled by nx_cc. license_tier: ORIGINAL261
_drv_vdead.nxbinds devices by vendor from HWMAP; control flow + pattern synthesized from the spec, compiled by nx_cc. license_tier: ORIGINAL261
nx_drv_bind.nxAUTONOMOUS DRIVER BRING-UP (X-DRV-W2), the driver registry binder.27911
nx_drv_proto_emit.nxDRIVER-PROTOCOL-FROM-SPEC (X-DRV-W1), the GENERIC driver emitter.47028