Skip to content
KN-86 Deckline

kn9 (Kinoshita K9) — encrypted operator comms

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

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

Identity

Section titled “Identity”

The operator’s encrypted comms and relay — handler messages, dead drops, and intel from linked decks. A threaded message / mail client in the Mutt lineage; the diegetic back-channel.

Scope (intended)

Section titled “Scope (intended)”
  • Threaded message reading (folders/threads, navigate, read, mark).
  • Receive handler briefs, dead-drop payloads, and intel.
  • Relay between linked decks (the LINK cooperation surface).

Interfaces

Section titled “Interfaces”
  • Launched via (launch-app :kn9 …) (NoshAPI Tier 1, ADR-0005). Draws on the cartridge/content rows per the canonical grid. Authored in KEC Lisp; source under runtime/programs/kn9/.
  • Messages arrive from mission scripts (handler narrative beats) and from linked decks via the LINK channel.

Open questions

Section titled “Open questions”
  • Message source model: mission-scripted only, or genuine deck-to-deck relay over LINK? Both?
  • Persistence — does a thread history live in UDS, on device SD, or per-cart?
  • Compose/reply: does the operator author messages (and if so, via nEmacs / Nokia multi-tap), or is kn9 read-mostly in v1?
  • Relationship to the bare-deck LINK tab (../runtime/bare-deck-content-brief.md).

References

Section titled “References”