Skip to main content
Link’d DMR
Download Beta

Code68 · CJ-1 all-features beta

What is included—and what stays gated

Version 0.2.65 includes all seven reviewed CJ-1 tracks plus the existing V1/V2 Android operations, web dispatcher, and V2 console. Automatic path selection and Nearby coordination remain safely unavailable whenever their production adapters are not configured. This is public-beta software, not an emergency-communications service.

Included in Code68 beta

All seven reviewed CJ-1 tracks are present in the signed beta. Availability still follows the explicit hardware, adapter, authorization, and safety gates shown here.

  • Dispatcher Lite expansion

    Role-gated incident assignment, release actions, assignment candidates, and a compact accountability view use the existing server-authorized organization boundary. Fleet planning and reports remain on the web.

  • Manual RF and Cellular handoff

    Both paths are shown clearly with deliberate manual selection and a keyed-call interlock. The Automatic engine is included but stays unavailable unless a reviewed production adapter is configured.

  • Direct Nearby coordination

    Bounded canned status, check-ins, assignments, expiry, deduplication, authorization re-checks, and receipts are included. Nearby stays unavailable without a reviewed production transport adapter; no multi-hop or verified range is claimed.

  • Better physical controls

    Debounced, user-visible action routing and supported CJ-1 mappings are included. A secondary action appears only for an explicitly validated hardware profile; unknown key events remain unavailable.

  • Bluetooth PTT and audio

    Approved accessory profiles expose visible audio-route and keying state, with transmit released fail-closed when the active accessory disconnects.

  • Signed configuration handoff

    Audience-bound, expiring, replay-safe plans require local review and apply with durable receipts, backup, verification, and rollback. There is no silent remote radio or firmware programming.

  • Expanded field diagnostics

    Sanitized support data includes coarse thermal state, reconnect history, transport history, and module state while excluding audio, transcripts, precise location, credentials, tokens, and private keys.

Availability gates

Included code does not imply an unsupported control is available. Each surface remains fail-closed until its runtime evidence is present.

  • Role and tenant boundaries

    Dispatcher actions must remain server-authorized, organization-scoped, auditable, and unavailable to ordinary field users.

  • Exact hardware evidence

    Physical buttons, Bluetooth profiles, RF state, thermal behavior, and firmware layouts must be reproduced on supported hardware.

  • PTT and audio safety

    Keying, audio routing, disconnects, and transport changes must fail closed without stuck transmit or misleading success states.

  • Production adapter evidence

    Automatic path selection and Nearby remain unavailable unless the reviewed production adapter for that surface is configured and healthy.

  • Interrupted-operation recovery

    Configuration, update, and selection flows must survive interruption and prove backup, verification, and rollback before release.

  • Privacy review

    Diagnostics and nearby coordination must exclude location, credentials, keys, audio, and unrestricted incident content by construction.

Research only

Exploration only, with no delivery date or compatibility promise.

  • Automatic production handoff

    Field validation and a reviewed production adapter are still required before the included Automatic engine can become available; it may never switch while keyed.

  • Multi-hop offline coordination

    Research beyond the first direct-device metadata exchange, including relay limits and safe reconnection behavior.

  • Additional adapters and modes

    Documented, permissioned radio and gateway interfaces, including NXDN96 feasibility, without a support or delivery promise.