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.
| # | Program | Spec | Status |
|---|---|---|---|
| 1 | Mission Board | ../runtime/mission-control.md | Implemented |
| 2 | Deck Hub | deck-hub.md | Spec pending |
| 3 | REPL | repl.md | Implemented |
| 4 | nEmacs | nemacs.md | Implemented |
| 5 | CONDUIT | conduit.md | Spec pending |
| 6 | Kinoshita Kommander | kommander.md | Spec pending |
| 7 | AmberCalc | ambercalc.md | Spec pending |
| 8 | RIPSAW | ripsaw.md | Spec pending |
| 9 | Keyring | keyring.md | Spec pending |
| 10 | kn9 (Kinoshita K9) | kn9.md | Spec pending |
| 11 | DOSSIER | dossier.md · data model | Data model drafted |
| 12 | bzbx | bzbx.md | Spec pending |
| 13 | knSALK | knsalk.md | Design drafted |
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.