Skip to content
KN-86 Deckline

bzbx — network-diagnostic toolkit

First-party on-device program #12 (ADR-0042). Status: Stub — design pending.

Charter stub. bzbx is canonical per ADR-0042; this doc is a placeholder until the full design lands. See the program roster.

Identity

Section titled “Identity”

A single program bundling network-diagnostic applets — ping, traceroute, nslookup, telnet, wget, nc — plus a packet / signal capture viewer for inspecting raw data streams. The “read the wire” tool. (Spiritually a busybox for the deck’s net stack.)

Scope (intended)

Section titled “Scope (intended)”
  • A launcher of small diagnostic applets under one roof.
  • Probe / resolve / fetch / connect, and view captured traffic.
  • The reconnaissance complement to CONDUIT’s interactive sessions.

Interfaces

Section titled “Interfaces”
  • Launched via (launch-app :bzbx …) (NoshAPI Tier 1, ADR-0005). Draws on the cartridge/content rows per the canonical grid. Authored in KEC Lisp; source under runtime/programs/bzbx/.

Open questions

Section titled “Open questions”
  • Applet set for v1 — which of ping / traceroute / nslookup / telnet / wget / nc ship first?
  • Real network vs. mission-provided in-world responses (same determinism/offline question as CONDUIT). Resolved: always in-world / simulated — see enrichment-contract.md §2. bzbx reads the cart-supplied world model; discoveries emit DOSSIER keys via the sanctioned dossier-commit path.
  • Capture-viewer data format — what does “the wire” look like as a viewable stream?
  • Boundary with CONDUIT (conduit.md): bzbx = probe/inspect (recon), CONDUIT = interactive session (access). Keep that line sharp.

References

Section titled “References”