Skip to content

KN-86 First-Party Programs

Canonical roster per ADR-0042. These are the thirteen programs that ship in the KN-86 system image, on DeckRunner’s Content tier (ADR-0040), authored in KEC Lisp and owned by the screen router.

They are a distinct category from the two other kinds of software on the device:

  • Programs (these thirteen) — first-party tools the operator uses; always present, regardless of cart.
  • Mission capability baselines (ADR-0030) — the four System-tier mission generators (TERMINAL / GRID / AUDIT / SONAR); see ../runtime/baselines/.
  • Carts (ADR-0019) — removable capability modules; see ../cartridges/.

Programs have no Capability Registry presence and are never superseded by a cart. Mission Lisp launches a program via (launch-app :program-id …) (NoshAPI primitive — ADR-0005 amendment, tracked in ADR-0042).

How carts enrich programs — the cross-program contract (a program is a generic lens; a cart supplies the simulated world it looks at; recon programs emit typed DOSSIER keys via a sanctioned write) is specified in enrichment-contract.md.

How programs thread together — the worked multi-program mission (one live :world + one DOSSIER shared across program handoffs; the three cross-program seams composed) is walked in worked-mission-walkthrough.md (GWP-630).

The per-tier gates and implementation readout for each program’s document chain, per the documentation standard. Gate vocabulary: absent · draft · approved. Impl is judged against the deepest approved tier, with an evidence link. Cells mirror each doc’s header block; a PR that changes a header updates its row here in the same PR.

#TitleFileT1T2T3Impl
1Mission Boardmission-control.mdshipped — board_screen.c, test_mission_board.c, board.gif
2Deck Hubdeck-hub.mdabsentapproveddraftpartial — first-boot OOBE aux.lsp, test_deck_aux.c; guided pass / loadout / SUPPLY unbuilt
3REPLrepl.mdapprovedshipped — repl_screen.c, test_repl_screen.c, repl-quake.gif
4nEmacsnemacs.mdapprovedshipped — nemacs.c, test_nemacs_runtime.c, nemacs-lib.gif
5CONDUITconduit.mddraftapprovedapprovedpartial — conduit.lsp, test_conduit.c, conduit.gif
6Kinoshita Kommanderkommander.mddraftapprovedapprovedpartial — kommander.lsp, test_kommander.c, kommander.gif
7AmberCalcambercalc.mddraftapprovedapprovedpartial — ambercalc.lsp, test_ambercalc.c, ambercalc.gif
8RIPSAWripsaw.mddraftapprovedapprovedpartial — ripsaw.lsp, test_ripsaw.c, ripsaw.gif
9Keyringkeyring.mddraftapprovedapprovedpartial — keyring.lsp, test_keyring.c, keyring.gif
10kn9 (Kinoshita K9)kn9.mddraftapprovedapprovedpartial — kn9.lsp, test_kn9.c, kn9.gif
11DOSSIERdossier.md · data modeldraftdraftdraftpartial — rolodex viewer dossier.lsp + dossier.c, test_dossier.c, dossier.gif
12bzbxbzbx.mddraftapprovedapprovedpartial — bzbx.lsp, test_bzbx.c, bzbx.gif
13knSALKknsalk.mddraftdraftdraftnone — chartered; no program source (screen_router.c reserves the id)

Mission Board’s design is Tier-4 (Mission Control, ADR-0028); its spec stays in runtime/. REPL and nEmacs are shipped utilities whose detailed design is Tier-4 (the ADRs + the editor-tools reference); they carry no program-tier T1/T3 chain. A cell marks a tier that lives at T4 by design, not a stub owed.

Single-tier companions (design detail beside the chains, each declaring one tier): the DOSSIER record schema dossier-data-model.md (T3 draft), the cross-program enrichment-contract.md (T3 draft), and the worked-mission-walkthrough.md integration path (T3 approved, shipped). The SUPPLY view’s contract deck-hub-supply.md folded into Deck Hub’s Tier 3 (GWP-710) and is now a pointer stub.

The implementer-facing editor reference (loop semantics, keymap internals, T9 ranker) lives at a different tier, in ../api-reference/editor-tools/; the REPL and nEmacs program docs above link out to it.

Program source lives in runtime/programs/ in the monorepo, one subdirectory per program.