Skip to content
KN-86 Deckline

CONDUIT — multi-protocol network client

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

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

Identity

Section titled “Identity”

The deck’s network client — SSH / Telnet / FTP / raw TCP. The primary intrusion interface for contracts that require live terminal access to a target host.

Scope (intended)

Section titled “Scope (intended)”
  • Connect to a target endpoint over one of the supported protocols.
  • Interactive remote session (command/response), file pull/push over FTP.
  • The session surface a mission drops the operator into for hands-on access.

Interfaces

Section titled “Interfaces”
  • Launched via (launch-app :conduit …) (NoshAPI Tier 1, ADR-0005). Draws on the cartridge/content rows per the canonical grid. Authored in KEC Lisp; source under runtime/programs/conduit/.
  • A mission/cart hands CONDUIT a target via :payload (endpoint, protocol, credentials/handle) — ICE BREAKER’s domain enriches a CONDUIT session but does not gate access (ADR-0042 constraint).

Open questions

Section titled “Open questions”
  • Real sockets vs. simulated targets: on hardware, does CONDUIT speak to real network endpoints, or to mission-provided in-world target models? Resolved: always in-world / simulated (determinism + offline) — see enrichment-contract.md §2. The target host model arrives via :payload + a :world handle.
  • Relationship to bzbx (bzbx.md) — diagnostic/probing applets vs. interactive sessions: where is the line?
  • Credential flow — does CONDUIT pull keys from Keyring (keyring.md)?

References

Section titled “References”